Equinox p2 (Ian Bull)

September 26, 2012

Discussion/Reminders

Status

Platform Workspace (Szymon)

Platform UI (Paul)

Platform Text (Dani)

vacation

Platform Debug (Mike / Pawel)

bug fixing / triage

Platform Ant (Mike)

bug fixing / triage

Platform SWT (Silenio)

Platform Releng (David)

prepared for Juno SR1 release on Friday

I'm prepared to give up trying to fix the 2 p2-related DNFs on Mac tests. I think "manual" proxies really don't work with p2!? Opened bug 390392. Also requested webmasters use transparent proxies which (I'm guessing) would make the tests work again. bug 390401. Should we disable them? DNFs add hours and hours to total test time.

JDT Core (Srikanth)

JDT Debug (Mike)

JDT UI (Markus)

Fixed various coloring problems for platforms with white-on-black tooltips (e.g. Variable value hover on Ubuntu with Ambiance theme). Common flaw: Code sets bg to SWT.COLOR_INFO_BACKGROUND but doesn't set fg to COLOR_INFO_FOREGROUND.

PDE (Curtis)

API Tools EE Descriptions categories now distributed in a single feature

JDT Debug (Mike)

JDT UI (Dani)

PDE (Curtis)

I (Curtis) may miss the meeting due to an unexpected appointment

No changes planned for SR1

Equinox (Tom Watson)

Equinox p2 (Ian Bull)

September 5, 2012

Reminders

RC3 this week with a test pass on Thursday and official sign-off. All non-doc fixes need PMC approval. For details see Juno 4.2 SR1 Endgame Plan. Please make sure that all bugs are verified and marked as such in bugzilla. Currently we still have many unverified bugs.

Discussion

Sign-off details [David]

I propose a slight tightening of "sign off" procedure, so there is a concrete deadline.
Typically, if "test day" is Thursday, we'd say project leads or delegates 1) must sign-off by 5 PM (Eastern) Thursday,
or, 2) by 5 PM, comment in sign-off bugzilla entry when they plan to be done (Such as "by noon Friday"). If no sign-off and no word from component, then Friday morning a note sent to PMC List asking for PMC member to "sign off", or not. If no word from PMC, by 5 PM Friday, we would assume a "go", hope for the best, and sort out errors in process or delegation later. See discussions in bug 388377 for the background and motivation for this proposal.

Suggestions? Counter proposals?

Status

Platform Workspace (Szymon)

Juno SR1 status: no further fixes planned

Platform UI (Paul)

Platform Text (Dani)

Juno SR1 status: no further fixes planned

bug fixing

Platform Debug (Mike / Pawel)

Juno SR1 status: no further fixes planned

bug fixing / triage

Vacation

Platform Ant (Mike)

Juno SR1 status: no further fixes planned

Vacation

Platform SWT (Silenio)

Juno SR1 status: no further fixes planned

reviewing more GTK 3 patches

bug fixing

Platform Releng (David)

prep for Juno SR1, minor work with tests, test framework
Orbit work

JDT Core (Srikanth)

* Progress on JSR335 - we are able to execute code with default methods now.
* Progress on JSR308 - Annotations on nested types, wildcards.
* Progress on hiring - Two candidates short listed - looks promising barring last
minute hitches.
* Nothing more in plan for SR1.

PDE (Curtis Windatt)

Equinox (Tom Watson)

Equinox p2 (Ian Bull)

August 15, 2012

Discussion

(Markus) Auto-tagging from master is problematic in the milestone week

No possibility for a controlled rebuild

Not all committers seem to follow (or know about) the Eclipse process (lockdown rules; changes on or after test day need to be reviewed)

Team leads should decide and stick to one of two working modes:

Either work with integration and master branches, and only push integration in a controlled fashion

Or work with master only, but make sure all committers follow the rules and do not commit ongoing work to master in milestone weeks after the last scheduled test build and until the milestone is released

Decision: Team leads who keep working with master only remind their committers to not push unreviewed work in milestone weeks

(John) What to do in the Git repository when bundles or features are removed?

Decision: Keep a .project file and add a readme.

Status

Platform UI (Paul)

Returning from vacations

Juno SR1 status: still have open bugs for 4.2.1, will need to bump some to 4.2.2

Decision was to move to Wednesday's 10, 12:00; always, instead of Thursday, and then schedule nothing special for RC weeks. This aligns with the 4.2.1 SR 1 Endgame Plan.

Question was asked about how to "change history" to correct authorship of a commit. Basic answer was that changing history risks messing up others who have that branch checked out, so best to add a new commit explaining the connection to a bug, the other commit hash, and ?fixing? authorship if possible ... but, not sure any of us on call knew all details of how that all works with auto IP log (especially, if desire was to remove an author? ... though, not sure that's legitimate ... maybe if someone just added whitespace formatting or something?). [Its not clear, to me, how "authorship" could ever be "wrong"? Interesting case. ]