[platform-releng-dev] Reminder of all to do this week ... On Wednesday (

[David M Williams <david_williams@xxxxxxxxxx>]

This is a reminder of actions each component
lead needs to do this week -- on Wednesday, Eastern time -- some of which
need to be "coordinated" or our build will break. 

Today's I-build is in progress, and
following our standard practice, teams, in theory, could ask for a respin
... but, we'll say just for a short, limited time today (Tuesday) since
the changes we make on Wednesday will make a respin difficult or uncertain.


1. The change to coordinate most, is
to change your version of eclipse-platform-parent pom to "4.4.0-SNAPSHOT"
in master. I'll leave as "4.3.0-SNAPSHOT for tonight's N-build (8
PM Eastern) but after that, it will be "4.4.0-SNAPSHOT" (in master)
so everyone will need to "match", in master and/or integration
branches, or builds will break. Paul has kindly prepared patches for everyone
(see umbrella bug 410966 [1] ... but as with all patches, please take minute
to make sure it "makes sense" to you, and if questions, ask in
the bug). 

2. Every thing is on track for formal
release tomorrow, 6/26, so that's a good time to tag your code, that was
used in Kepler Release, with R4_3_0 (See bug 410747 [2] for complete details,
and please update that bug as you tag your repos, so we all know). 

3. After tagging your repo, that is
a good time to make an R4_3_maintenance branch of your code, so we can
start 4.3 M builds using that branch (See bug 411613 [3]).  
Since making "persistent branches"
is disabled for our repositories, there is a flag needs to be temporarily
disabled (or, is it enabled? :) to allow a persistent branch to be created,
and then you, as committer, can create your branch, preferably from your
R4_3_0 tag. To disable the repo flag, you will need a committer who has
shell access, and I am glad to help any team do this, who doesn't have
a committer with shell access.  (Or, even if you do, I'm glad to help
if you don't remember how :) 

Please ask if questions, 

[1] https://bugs.eclipse.org/bugs/show_bug.cgi?id=410966
[2] https://bugs.eclipse.org/bugs/show_bug.cgi?id=410747
[3] https://bugs.eclipse.org/bugs/show_bug.cgi?id=411613