We will need to tag the release but we can wait until we are officially done (week of June 25th).

June 6, 2012: - McQ, Dani, Martin, John, Andrew

Discussion of how to handle test failures for final build. Most of the remaining failures are infrastructure issues related to our move to Hudson for tests. We will document the failures through bugs, and include a note on the build results page for the final build explaining the failures

Discussion of whether we need a 3.9 release. Unanimous conclusion was that we do not see a need for it. Reducing to one stream will greatly reduce our development overhead and encourage consolidation around the single stream.

Discussion of how to handle the disappearance of org.eclipse.equinox.concurrent from our RC3 builds. This was never deliberately included in the platform, but was present due to a greedy optional dependency from ECF. By very close 3/2 decision PMC decided to leave it alone and document the disappearance in porting guide, readme file, release review material, and cross-project list.

McQ would like to see a plan item for next year "actively promote more committers from outside"

Martin: Asterisk - will need a dialin for Dani in Switzerland; AI Dani forward his dialin to Martin for the time being

April 11, 2012: - McQ, Dani, Martin, Andrew, John

Martin: LTS vs Quality/Fixes in Current Stream - Like John's reply making the link between the two

McQ/John: Builds - Moving forward

McQ: CBI Builds - Platform not going to take any ownership but will be a consumer like others - still shooting for Juno SR1

Andrew: 4.2 Builds in Fedora 17 - Testing now

McQ: IBM Ottawa Team moving to new building - expect delays during next couple days

April 4, 2012: - McQ, Dani, Martin, Andrew

Dani: VM Requirements - Help no longer works on Java 5, this surprised some people... but Project Plan talks about a Java 6 req now

Martin suggestion: on the "Required JVM" table in the Project Plan, add a 2nd column with closure of BREE including all pre-reqs (continue having 1st column the BREE of the bundle itself auto-generated)

McQ concern: Lots of duplicate bugs would take focus away from the team

Martin: Could encourage triage as part of the contest, and only count good/new bugs

John: Some low-hanging fruit bugs in Platform UI but not necessarily in 4.x ("helpwanted")

John: Re-introduce the "greatbug" keyword ?

A greatbug is relevant, new, good description that helps understanding/finding the issue; ideally with a patch.

Resolution: AI John send note to Mike

John: PDE API Moved

Some internal, provisional API was migrated to full API in this release

Someone from SAP (Dimitar Giormov) Asked adding back the provisional API such that they could support 2 versions of Eclipse with one codebase

McQ: Would have helped them 4 years ago .. but at the moment don't have enough people

McQ: Question how pervasive their use of the old API is ... how much Reflection would they need to put int

One resolution could be OK but only if they provide all the patches

This kind of duplication is error prone and adds a maintenance burden on the project

February 22, 2012: - Dani, McQ, John, Andrew

Repeat of PDE build discussion from last week. We decided to nominate John Arthorne as a committer so we at least have someone to accept community patches. We will revisit after Juno and perhaps do a larger restructuring

Communication with eGit: We have written some patches for eGit that have been growing stale. Dani will review the patches, and then send an email to eGit lead asking if there is a particular reason for not accepting them. If there is no problem with the patches we will track down an eGit committer to release them.

Andrew asked about process for approving CQs:

Any PMC member can feel free to approve CQs

New versions of existing third party libraries are a no-brainer, typically just +1 right away

For new third party libraries we may need a PMC discussion about why the library is needed, what feature it will live in, etc

For code contributions just make sure the legal process has been followed and then +1. We generally trust the judgement of the committer who will process the contribution.

February 15, 2012: - Dani, McQ, John

Some discussion of what to do with PDE Build, which lacks committers. PDE as a whole has barely enough committers to be a functioning project, so maybe we should be looking at a larger restructuring after

Juno rather than one piece at a time. We lacked quorum to make a decision so we will defer discussion to another week.