Platform Releng (David)

My schedule for rest of the year: working "part time" to enjoy some vacation ... will be around roughly half days Tuesdays, Wednesdays, and Thursdays. Please open releng bugs or send email if anything needs my attention. I will "be around", but plan to be on IM less, etc. But do feel free to let me know of anything needed for M4 (Our M4 +0 day is 12/14).

Equinox p2 (Ian Bull)

October 17, 2012

Discussion/Reminders

Or, if rebuild desired, just chance picking up new things not specifically planned for rebuild?

Nearly all components now use "master" as input to I- and N- builds.

Conclusion was no, we don't need a formal "quiet period" (it'd be too confusing with all the different time zones, etc.); the current weekly rhythm description suffices; basically comes down to being component lead's responsibility to make sure only safe fixes are going into master. If/when there are risky changes, team may want to return to master/integration model, or wait a while after I build, so less chance of a risky change going into a re-build before it had been through a nightly build. Another option mentioned was if rebuild was required, all repositories could be "commented out" except for the repositories that intend to be in the rebuild ... but, that sounds complicated and error prone itself (but ... could be done on occasion).

WebKitGTK plans to discontinue GTK 2.x support in their next release (likely Spring 2013)

EclipseCon Europe prep (Arun)

Markus committer election completed

Platform Releng (David)

Mac 64 bit machine (VM and Eclipse) is now used instead of 32 bit. (bug 354774) It is now quickest run of unit tests (though, admittedly we do run a few fewer tests there). Some labeling will remain wrong until bug 390986 is fixed. But it is 64 bit, using a Java 6 VM.

- I plan to remove the "old" Mac 32 bit Hudson jobs unless someone thinks we might need them for some special case?

Windows. Sigh. After our performance "tests of the tests" we have had trouble getting ordinary JUnit's running again in a reasonable period of time due to "virtualization tweaking" that's needed. Join in or watch the fun at bug 389857. I think progress is being made, but seems clear it will never "be the same" as running plain windows.

JDT Core (Srikanth)

Good progress on JSR308 & JSR335.

JDT Debug (Mike)

fixed bugs in 'Open from Clipboard' action

migrated website to git

bug fixing / triage

continued work on converting JDT debug actions

JDT UI (Markus)

cleaning up website for transfer to Git

planning to remove org.junit 3.8.2 from the SDK builds; JUnit 3 tests can also be run with JUnit 4 now

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. ]