TrustedUser
2,147
edits
Difference between revisions of "HOWTO-Release"
Jump to navigation
Jump to search
→News & Notification: add one more todo item
(→Updating the wiki: update list of pages to update on the wiki for new releases) |
(→News & Notification: add one more todo item) |
||
| (4 intermediate revisions by the same user not shown) | |||
| Line 37: | Line 37: | ||
=== Preparing the source === | === Preparing the source === | ||
* Make sure the translations.dat file is up to date. This file is automatically generated once per week (on Monday morning) and may need to be updated manually if changes to the translations occurred since the last Monday. Use ''make translations-dat'' to update the file (and then commit it if it was changed). | |||
* You have to update the versions in all relevant files. There is a script, <code>devtools/update-version.pl</code> meant to help you with this. It will generate/update the following files: | * You have to update the versions in all relevant files. There is a script, <code>devtools/update-version.pl</code> meant to help you with this. It will generate/update the following files: | ||
** base/internal_version.h | ** base/internal_version.h | ||
| Line 47: | Line 48: | ||
** COPYRIGHT | ** COPYRIGHT | ||
* Review the following port specific files for version updates: | * Review the following port specific files for version updates: | ||
** backends/platform/ | ** backends/platform/ps2/README.PS2 | ||
** backends/platform/psp/README.PSP | ** backends/platform/psp/README.PSP | ||
** backends/platform/symbian/README | ** backends/platform/symbian/README | ||
| Line 112: | Line 111: | ||
*** your build-specific README (optional) | *** your build-specific README (optional) | ||
*** ... | *** ... | ||
* Porters need to upload binaries at some service and then | * Porters need to upload binaries at some service and then send the link to the team member managing the release (this should be detailed in the email sent to porters with the links to the tarballs). | ||
* 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/config.inc.php</code> to update the global version. | ||
| Line 118: | Line 117: | ||
** Update <code>data/downloads.xml</code>. | ** Update <code>data/downloads.xml</code>. | ||
** Add a news item. | ** Add a news item. | ||
** Copy over the release files to | ** Sparkle automatic updates | ||
*** Create a ReleaseNotes file on FRS with the changes from this release (from NEWS file). | |||
*** Sign the macOS and Win32 binaries with our private key for Sparkle | |||
*** Update the scummvm_appcast.xml file in scummvm/dist/macosx/. | |||
*** Copy the app cast file on the website as appcasts/macosx/release.xml | |||
** Copy over the release files to FRS | |||
*** Set the OS for the newly uploaded binaries (click on the (i) next to each binary). | *** Set the OS for the newly uploaded binaries (click on the (i) next to each binary). | ||
**** -win32.exe as Windows binary | **** -win32.exe as Windows binary | ||
| Line 158: | Line 162: | ||
** ... more ? | ** ... more ? | ||
* Put the updated web site online | * Put the updated web site online | ||
* Update IRC channel topic | |||
=== Updating the wiki === | === Updating the wiki === | ||