333
edits
Difference between revisions of "HOWTO-Release"
Jump to navigation
Jump to search
m
→Preparations
(Rearranged sections) |
Rootfather (talk | contribs) m (→Preparations) |
||
| Line 13: | Line 13: | ||
=== Preparations === | === Preparations === | ||
* Make the release plan, normally 1-2 weeks before branching, 3-4 weeks for bug fixing, 2 weeks after tagging before the release | * Make the release plan, normally 1-2 weeks before branching, 3-4 weeks for bug fixing, 2 weeks after tagging before the release. | ||
** e-mail -devel with the proposed schedule, ask if someone would like to finish some functionality | ** For reference, ScummVM 2.3.0 was built according to the following schedule: | ||
<pre>August 14 (Sat): Release testing announced, feature freeze in master | |||
August 28 (Sat): Release branch created, master unfrozen | |||
September 17 (Fri): Release tagged, porters asked to submit their builds | |||
September 27th (Mon): Release</pre> | |||
* e-mail -devel with the proposed schedule, ask if someone would like to finish some functionality | |||
* Look through all the open issues on the bugtracker and identify release blockers and nice-to-have-fixed bugs | |||
* Update the lists of files below, adding new engine data files and such | * Update the lists of files below, adding new engine data files and such | ||
* If some games must be fixed before the release, identify those and create a list at [[Release Testing]] | * If some games must be fixed before the release, identify those and create a list at [[Release Testing]] | ||