Development Focus -----------------
The Release Candidate (RC) deadline is next Thursday, September 26th. Work should be focused on fixing any release-critical bugs.
General Information -------------------
All deliverables released under a cycle-with-rc model should have a first release candidate by the end of the week, from which a stable/train branch will be cut. This branch will track the Train release.
Once stable/train has been created, master will will be ready to switch to Ussuri development. While master will no longer be feature-frozen, please prioritize any work necessary for completing Train plans. Release-critical bugfixes will need to be merged in the master branch first, then backported to the stable/train branch before a new release candidate can be proposed.
Actions ---------
Early in the week, the release team will be proposing RC1 patches for all cycle-with-rc projects, using the latest commit from master. If your team is ready to go for cutting RC1, please let us know by leaving a +1 on these patches.
If there are still a few more patches needed before RC1, you can -1 the patch and update it later in the week with the new commit hash you would like to use. Remember, stable/train branches will be created with this, so you will want to make sure you have what you need included to avoid needing to backport changes from master (which will technically then be Ussuri) to this stable branch for any additional RCs before the final release.
The release team will also be proposing releases for any deliverable following a cycle-with-intermediary model that has not produced any Train release so far.
Upcoming Deadlines & Dates --------------------------
RC1 deadline: September 26 (R-3 week) Final RC deadline: October 10 (R-1 week) Final Train release: October 16 Forum+PTG at Shanghai summit: November 4