Difference between revisions of "HOWTO-Release"

Jump to navigation Jump to search
827 bytes added ,  18:19, 20 September 2022
m
Clarify major vs. minor release
(→‎Preparing the source: Add instructions for weblate)
m (Clarify major vs. minor release)
(2 intermediate revisions by the same user not shown)
Line 5: Line 5:
All examples are based on the 2.6 and 2.6.0 version. Don't forget to adapt with the adequate version number.
All examples are based on the 2.6 and 2.6.0 version. Don't forget to adapt with the adequate version number.


=== Definitions ===
* Major release: A major release marks the leap from e.g. ScummVM 2.6.x to 2.7.x
* Minor release: A minor release marks the exact version we release, e.g. ScummVM 2.6.0 or 2.6.1.


=== Preparations ===
=== Preparations ===
Line 153: Line 157:


* Edit <code>include/config.inc.php</code> to update the global version.
* Edit <code>include/config.inc.php</code> to update the global version.
* Create a new XML file for the new version in <code>data/compatibility/</code>.
* Update <code>data/downloads.xml</code>.
* 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 165: Line 167:
* 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>scummvm_downloads</code> tab, for any releases that have been uploaded to FRS, change the <code>version</code> column to match the latest version
** 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!'''


=== Tagging a version ===
=== Tagging a version ===
329

edits

Navigation menu