1,510
edits
Difference between revisions of "HOWTO-Release"
Jump to navigation
Jump to search
→Tagging a version: Explained how to set default version in docportal
Rootfather (talk | contribs) |
(→Tagging a version: Explained how to set default version in docportal) |
||
| (10 intermediate revisions by 3 users not shown) | |||
| Line 6: | Line 6: | ||
All examples are based on the 2.7 and 2.7.0 version. Don't forget to adapt with the adequate version number. | All examples are based on the 2.7 and 2.7.0 version. Don't forget to adapt with the adequate version number. | ||
For "x.y.0" releases of ScummVM, we also release a new version of the ScummVM Tools set. | |||
=== Definitions === | === Definitions === | ||
| Line 35: | Line 37: | ||
=== Branching for major release === | === Branching for major release === | ||
* Before creating the branch make sure there is no pending changes on weblate | * Before creating the branch make sure there is no pending changes on weblate | ||
** Go to repository maintenance for the ScummVM/scummvm component on the translations website: https://translations.scummvm.org/projects/scummvm/scummvm/#repository | ** Go to [https://translations.scummvm.org/projects/scummvm/#repository repository maintenance] for the ScummVM/scummvm component on the translations website: https://translations.scummvm.org/projects/scummvm/scummvm/#repository | ||
*** Lock the component | *** Click on the Lock the component button | ||
*** Commit pending changes, and push. | *** Commit pending changes, and push. | ||
* Create a branch for the 2.7.x releases from master, named branch-2-7 | * Create a branch for the 2.7.x releases from master, named branch-2-7 | ||
| Line 46: | Line 48: | ||
** <code>git tag -a -m "Mark 2.7.0pre" desc/2.7.0pre</code> | ** <code>git tag -a -m "Mark 2.7.0pre" desc/2.7.0pre</code> | ||
** <code>git push origin tag desc/2.7.0pre branch-2-7:branch-2-7</code> | ** <code>git push origin tag desc/2.7.0pre branch-2-7:branch-2-7</code> | ||
* Update doc/docportal/other_platforms/ | * Update doc/docportal/other_platforms/ios_build.rst to clone the new branch | ||
** Change <code>git clone <nowiki>https://github.com/scummvm/scummvm.git</nowiki></code> to <code>git clone --depth 1 -b branch-2-7 <nowiki>https://github.com/scummvm/scummvm.git</nowiki></code> | ** Change <code>git clone <nowiki>https://github.com/scummvm/scummvm.git</nowiki></code> to <code>git clone --depth 1 -b branch-2-7 <nowiki>https://github.com/scummvm/scummvm.git</nowiki></code> | ||
** <code>git add doc/docportal/other_platforms/ | ** <code>git add doc/docportal/other_platforms/ios_build.rst</code> | ||
** <code>git commit -m 'DOC: Update iOS clone command for 2.6 branch'</code> | ** <code>git commit -m 'DOC: Update iOS clone command for 2.6 branch'</code> | ||
** <code>git push</code> | ** <code>git push</code> | ||
| Line 63: | Line 65: | ||
** Go to repository maintenance for the ScummVM/scummvm component on the translations website: https://translations.scummvm.org/projects/scummvm/scummvm/#repository | ** Go to repository maintenance for the ScummVM/scummvm component on the translations website: https://translations.scummvm.org/projects/scummvm/scummvm/#repository | ||
*** Unlock the component | *** Unlock the component | ||
** Go to the announcement settings for the ScummVM/scummvm component on the translations website: https://translations.scummvm.org/projects/scummvm/scummvm/#announcement | |||
*** Post an announcement along the line of ''ScummVM 2.8.0 will be released soon. You have until Thursday December 14 to update your translations.'' Set the color to Warning, set the expiry date to the translation freeze date, and make sure the ''Notify users'' option is toggled on. | |||
* Update buildbot | * Update buildbot | ||
** Edit at the end of [https://github.com/scummvm/dockerized-bb/blob/master/buildbot-config/builds.py builds.py] the line starting with <code>builds.append(ScummVMStableBuild("stable",</code>. | ** Edit at the end of [https://github.com/scummvm/dockerized-bb/blob/master/buildbot-config/builds.py builds.py] the line starting with <code>builds.append(ScummVMStableBuild("stable",</code>. | ||
| Line 73: | Line 77: | ||
** Update IRC and Discord channel description | ** Update IRC and Discord channel description | ||
** Write a mail to scummvm-devel | ** Write a mail to scummvm-devel | ||
=== Semi-automated Checks === | |||
* Run <pre>make release-checks</pre> for performing several routine checks covered below: | |||
** Icons and Shader packs | |||
** ADGF_TESTING | |||
** IDE Projects | |||
** Translations | |||
** Release Notes on FRS | |||
** Engine data for MM and Ultima | |||
=== Testing === | === Testing === | ||
| Line 122: | Line 136: | ||
** git commit -m "DISTS: Generated Code::Blocks and MSVC project files" | ** git commit -m "DISTS: Generated Code::Blocks and MSVC project files" | ||
** And last but not least don't forget to push the results to our github repo via "git push" | ** And last but not least don't forget to push the results to our github repo via "git push" | ||
* [[#Tagging_a_version|Tag version]] | |||
* Make source tarballs, put them in the FRS directory. | * Make source tarballs, put them in the FRS directory. | ||
** There is a script <code>devtools/dist-scummvm.sh</code>, which creates them automatically. | ** There is a script <code>devtools/dist-scummvm.sh</code>, which creates them automatically. | ||
| Line 166: | Line 181: | ||
*** your build-specific README (optional) | *** your build-specific README (optional) | ||
*** ... | *** ... | ||
* Porters need to upload binaries | * Porters need to upload binaries. To do this, we will use our own Nextcloud instance, so porters don't have to rely on third-party services. To do this: | ||
**Create a new shared folder with upload permissions in the Nextcloud (ask rootfather when in doubt) | |||
**Set a new password for this shared folder | |||
**Mention this password in the mail to the mailing list asking for the porters to submit their builds | |||
=== Updating the Website === | === Updating the Website === | ||
Update the website internally (i.e. update the version in the repository), but do not yet put these changes online. | Update the website internally (i.e. update the version in the repository), but do not yet put these changes online. | ||
* Edit <code>include/ | * Edit <code>include/Constants.phpq</code> to update the global version. | ||
* Add a news item. | * Add a news item. | ||
* Follow the instructions at [https://wiki.scummvm.org/index.php?title=HOWTO-Release#Signing_binaries HOWTO-Release#Signing binaries] in order to enable updates via (Win)Sparkle | * Follow the instructions at [https://wiki.scummvm.org/index.php?title=HOWTO-Release#Signing_binaries HOWTO-Release#Signing binaries] in order to enable updates via (Win)Sparkle | ||
| Line 182: | Line 200: | ||
* On [https://docs.google.com/spreadsheets/d/1QzwFleEKXOsE59cYMOcQB7C2f0Np48uAQOCG8kicX_s/edit#gid=854570757 the ScummVM Data spreadsheet] | * On [https://docs.google.com/spreadsheets/d/1QzwFleEKXOsE59cYMOcQB7C2f0Np48uAQOCG8kicX_s/edit#gid=854570757 the ScummVM Data spreadsheet] | ||
** On the <code>versions</code> tab, add the new release to the bottom of the list | ** On the <code>versions</code> tab, add the new release to the bottom of the list | ||
** On the <code>compatibility</code> tab, replace DEV with the release number for all newly added games | |||
** On the <code>scummvm_downloads</code> tab, for any releases that have been uploaded to FRS, change the <code>version</code> column to match the latest version. Verify that all ports that don't have the new version (yet) are set to "old", so they appear in the right section of our website. | ** On the <code>scummvm_downloads</code> tab, for any releases that have been uploaded to FRS, change the <code>version</code> column to match the latest version. Verify that all ports that don't have the new version (yet) are set to "old", so they appear in the right section of our website. | ||
**'''WARNING:''' The website update script keeps track of the different sheets in the spreadsheet file based on an internal ID. You '''must''' use the exact same sheet for every release. This means that you have to temporarily duplicate the downloads sheet and constantly update it while the porters submit their builds - you don't want to all builds at once right before the release. As soon as the release is about to get published, '''copy over all content of the temporary scummvm_downloads sheet to the productive one.''' '''You must not rename the old sheet under any circumstances, it will break the website!''' | **'''WARNING:''' The website update script keeps track of the different sheets in the spreadsheet file based on an internal ID. You '''must''' use the exact same sheet for every release. This means that you have to temporarily duplicate the downloads sheet and constantly update it while the porters submit their builds - you don't want to all builds at once right before the release. As soon as the release is about to get published, '''copy over all content of the temporary scummvm_downloads sheet to the productive one.''' '''You must not rename the old sheet under any circumstances, it will break the website!''' | ||
| Line 201: | Line 220: | ||
**# Click on '''ScummVM''' | **# Click on '''ScummVM''' | ||
**# Click on '''Versions''' | **# Click on '''Versions''' | ||
**# Find the relevant tag like 'v2.6.0' | **#* Find the relevant tag like 'v2.6.0' | ||
**# Press '''Activate''' | **#* Press '''Activate''' | ||
**# Click on '''⚙ Admin''' | |||
**#* Click on '''Advanced Settings''' | |||
**#* In '''Default version''' drop-down, select the new tag. | |||
=== Creating source tarballs === | === Creating source tarballs === | ||
| Line 245: | Line 267: | ||
* Write a news item for our website (also to be used as a template for news items on other sites). | * Write a news item for our website (also to be used as a template for news items on other sites). | ||
** Change version constants in <tt>include/Constants.php</tt> | ** Change version constants in <tt>include/Constants.php</tt> | ||
** Put Release Notes into two files in the release directory, one is plain text, named "ReleaseNotes", another one is HTML, use [https:// | ** Put Release Notes into two files in the release directory, one is plain text, named "ReleaseNotes", another one is HTML, use [https://markdowntohtml.com/ markdowntohtml.com] service but copy the HTML body tags from the previous release. | ||
**Make sure to update the Release information in the datasheet | **Make sure to update the Release information in the datasheet | ||
** Make sure Sparkle appcast is updated (see [[#Signing binaries]]) | ** Make sure Sparkle appcast is updated (see [[#Signing binaries]]) | ||