1,554
edits
Difference between revisions of "HOWTO-Release"
Jump to navigation
Jump to search
→During the release cycle: -- added section
(→Preparations: added the existing steps) |
(→During the release cycle: -- added section) |
||
| Line 11: | Line 11: | ||
** Look through all the open issues on the bugtracker and identify release blockers and nice-to-have-fixed bugs | ** 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]] | |||
* Announce the testing period on the main website and copy to the forums and FB | |||
=== During the release cycle === | |||
* E-mail the scummvm-devel list at least weekly with the list of release blockers and nice-to-have-fixed bugs | |||
* Track daily testing progress and update Wiki if applicable. Normally, we collect playtests on the forums | |||
* Watch for any potential blockers and pat developers who own the identified blockers | |||
* Squash as many bugs as possible | |||
=== Branching for major release === | === Branching for major release === | ||