WikiReleaseTeam/Release timeline/1.24

Release dates are given on in the Version lifecycle page. This timeline is a schedule for what needs to happen before that time. The release should happen no later than the last day of the month given in the lifecycle document. That date is given here as R (for “release”).

Date for 1.24	Relative schedule	Task
2014-10-08	(R-7 weeks)	Announce that the release branch will be created in one week. Ask people to make sure that anything needed to complete in-progress features is merged before then. Create X.XX version in bugzilla.
2014-10-15	(R-6 weeks)	Create the branch for core and all extensions in Gerrit.
2014-10-22	(R-5 weeks)	Apply the X.XX-rc.0 tag and release the initial release candidate.
2014-10-29	(R-4 weeks)	Collect any bug reports and summarize them on the mailing list.
2014-11-05	(R-3 weeks)	Apply the X.XX-rc.1 tag and release the second release candidate. Any new extensions that are proposed for addition to the tarball should be in it by this point. No extension changes are made after this point.
2014-11-12	(R-2 weeks)	Collect any new bug reports, merge fixes, back out new, incomplete features accidently included, apply X.XX-rc.2 tag and release third release candidate.
2014-11-19	(R-1 week)	Repeat previous step, use X.XX-rc.final to tag and release. No backports are accepted after this point.
2014-11-26	(R)	TAG the code with X.XX and Make the release.

During this whole process, review the RELEASE-NOTES and determine what to include in the release announcement.

See also[edit]