TrustedUser
2,147
edits
Difference between revisions of "HOWTO-Release"
Jump to navigation
Jump to search
m
Text replacement - "</source>" to "</syntaxhighlight>"
(→Binaries: Add instructions for Sparkle) |
m (Text replacement - "</source>" to "</syntaxhighlight>") |
||
| (4 intermediate revisions by 2 users not shown) | |||
| Line 37: | Line 37: | ||
=== Preparing the source === | === Preparing the source === | ||
* Browse 'git log' since the previous release and add all significant changes to the NEWS file | |||
* 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). | * 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: | ||
| Line 111: | Line 112: | ||
*** 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 145: | Line 146: | ||
Then you need to create and upload the tarballs. | Then you need to create and upload the tarballs. | ||
< | <syntaxhighlight lang="bash"> | ||
devtools/dist-scummvm.sh scummvm 1.9.0 | devtools/dist-scummvm.sh scummvm 1.9.0 | ||
devtools/dist-scummvm.sh scummvm-tools 1.9.0 | devtools/dist-scummvm.sh scummvm-tools 1.9.0 | ||
</ | </syntaxhighlight> | ||
Then upload the resulting scummvm-1.9.0.tar.gz, scummvm-1.9.0.tar.bz2, scummvm-1.9.0.tar.xz and scummvm-1.9.0.tar.zip to the FRS. | Then upload the resulting scummvm-1.9.0.tar.gz, scummvm-1.9.0.tar.bz2, scummvm-1.9.0.tar.xz and scummvm-1.9.0.tar.zip to the FRS. | ||
| Line 162: | Line 163: | ||
** ... more ? | ** ... more ? | ||
* Put the updated web site online | * Put the updated web site online | ||
* Update IRC channel topic | |||
=== Updating the wiki === | === Updating the wiki === | ||