Use refs/for/Neon_maintenance for Gerrit
changes intended for Neon.1 and refs/for/master for Gerrit changes intended
And, remember, anyone that is new to
Neon.1 should join the build by the 7/27 checkpoint at the latest. If questions
or issues, please ask here, or open a cross-project bug if you need help.
And, for Oxygen, remember to prepare
your release records and "declare intent" here soon -- and then
contribute to the aggregation build soon after!
David M Williams/Raleigh/IBM@IBMUS To:
07/12/2016 06:04 PM Subject:
Dates for Neon Update releases and Oxygen Milestones; changes; and declaring
for Oxygen. Sent by:
They do come out at about the same time so there will be work to do that
overlaps one with the other. Please plan accordingly.
We will update the Google calendar soon.
= = = = = = = = = = = =
Some small differences from previous years:
- The Update releases will formally, simultaneously release mid-week instead
of on Friday's, which makes their "quiet week" more like a week
and a half. - There is no longer a "warm-up" RC two weeks in advance of RC2:
we expect all RC's to be strong release candidates. - There is no longer a two-week window for the initial three milestones.
The Planning Council felt that (and the warm-up RC) were left-over processes
when we were all much less experienced at this, and now most projects are
very skilled at it, so those buffers are no longer needed.
= = = = = = = = = = = =
A larger change for the Update Releases.
There will be a "milestone" of sorts for each Update Release.
We call it a "checkpoint" in this context since there is only
one of them. This checkpoint build is primarily for new projects just joining
the train for the first time, or for projects which have very significant
changes. Other projects may contribute to them if they would like but in
most cases, we recommend not to, so that we have a steady target for the
new projects to hit. These checkpoints are one month before the first RC,
which means the fist one is not far off -- 7/22 to 7/27. (No EPP packages
for checkpoint builds.) Our goal is to allow those new to the process to
learn and get through the mechanics of contributing to the aggregation
build at a time that is less stressful than the rapid fire RC period as
well as improve communication about who or what is new in the Update releases.
= = = = = = = = = = = = =
I will split streams on Wednesday. All those in Neon will assume to be
still in Neon.1 unless they formally withdraw. For Oxygen, I will mark all contributions as "disabled" until
projects declare their intent, and create a Release Record. At that point, you may re-enable your contribution, but you may need to
wait to commit it until all your prereq projects have joined (that is,
just leave in in Gerrit until it passes validation there).