Difference between revisions of "Release process"
From FusionForge Wiki
(Clarify relationship with debian maintainers and reorder; fix typos; note TODO on method to create a proper tarball) |
|||
| Line 3: | Line 3: | ||
* Update <tt>src/CHANGES</tt> with user-friendly description of what happened since the last release, e.g. [https://fusionforge.org/plugins/scmgit/cgi-bin/gitweb.cgi?p=fusionforge/fusionforge.git;a=blob;f=src/CHANGES;hb=refs/heads/Branch_5_3]. Usually one would make a call to contributors so they update it, if not already. | * Update <tt>src/CHANGES</tt> with user-friendly description of what happened since the last release, e.g. [https://fusionforge.org/plugins/scmgit/cgi-bin/gitweb.cgi?p=fusionforge/fusionforge.git;a=blob;f=src/CHANGES;hb=refs/heads/Branch_5_3]. Usually one would make a call to contributors so they update it, if not already. | ||
* Update <tt>src/www/index_std.php</tt> as well. | * Update <tt>src/www/index_std.php</tt> as well. | ||
| + | * Involve distro packagers (e.g. using Release Candidates) so they have a chance to give feedback if changes are necessary. For Debian, this is us :) - cf. project [https://fusionforge.org/projects/deb-packaging/ debian packaging]. No other distro right now :/ | ||
| + | * Make sure the current release point passes the [[Test Suite]]. | ||
| + | * Decide the release at the next weekly meeting. | ||
* Update <tt>src/translations/fusionforge.pot</tt> (see [[Translations]]). | * Update <tt>src/translations/fusionforge.pot</tt> (see [[Translations]]). | ||
| − | |||
* Tag the precise release point on the release branch. | * Tag the precise release point on the release branch. | ||
| − | + | * Create the archive (everything in ~/src/ directory) [TODO: clean-up methods? e.g. using git-archive?] | |
| − | |||
| − | * Create the archive (everything | ||
* Add the archive at https://fusionforge.org/frs/?group_id=6. | * Add the archive at https://fusionforge.org/frs/?group_id=6. | ||
* Make an official announcement on the fusionforge.org front page. | * Make an official announcement on the fusionforge.org front page. | ||
| Line 14: | Line 14: | ||
* Notify TranslationProject coordinator of the new tarball (see [[Translations]]). | * Notify TranslationProject coordinator of the new tarball (see [[Translations]]). | ||
* Update all field values in the tracker (add new "Found in version" and "Target release" fields...). | * Update all field values in the tracker (add new "Found in version" and "Target release" fields...). | ||
| − | * | + | * Push a new Debian version to unstable (and optionally to stable-backports). |
Revision as of 11:11, 30 May 2014
Here's the current semi-formal way we make a release:
- Announce intention to make a release on mailto:fusionforge-general@lists.fusionforge.org.
- Update src/CHANGES with user-friendly description of what happened since the last release, e.g. [1]. Usually one would make a call to contributors so they update it, if not already.
- Update src/www/index_std.php as well.
- Involve distro packagers (e.g. using Release Candidates) so they have a chance to give feedback if changes are necessary. For Debian, this is us :) - cf. project debian packaging. No other distro right now :/
- Make sure the current release point passes the Test Suite.
- Decide the release at the next weekly meeting.
- Update src/translations/fusionforge.pot (see Translations).
- Tag the precise release point on the release branch.
- Create the archive (everything in ~/src/ directory) [TODO: clean-up methods? e.g. using git-archive?]
- Add the archive at https://fusionforge.org/frs/?group_id=6.
- Make an official announcement on the fusionforge.org front page.
- If possible update fusionforge.org to the new version (showing we drink our own champagne).
- Notify TranslationProject coordinator of the new tarball (see Translations).
- Update all field values in the tracker (add new "Found in version" and "Target release" fields...).
- Push a new Debian version to unstable (and optionally to stable-backports).
