Difference between revisions of "HOWTO-Release"

Jump to navigation Jump to search
→‎Tagging a version: Explained how to set default version in docportal
(→‎Branching for major release: clarified how to lock Weblate)
(→‎Tagging a version: Explained how to set default version in docportal)
 
(3 intermediate revisions by 2 users not shown)
Line 65: 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 134: 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 186: Line 189:
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/config.inc.php</code> to update the global version.
* 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 217: 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 ===

Navigation menu