Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with
or
.
Download ZIP
Fetching contributors…

Cannot retrieve contributors at this time

50 lines (43 sloc) 1.974 kB
Checklist for (pre)-releases
----------------------------
See also: https://live.gnome.org/MaintainersCorner/Releasing
Note on version numbers:
* Releases are X.YY
* Bugfix releases are X.YY.Z where Z is a relatively small number (1, 2, 3...)
* Pre-releases (right before a major release) are X.YY.ZZ where ZZ = 91, 92, ...
Pre-requisites:
* 'make check' passes
* 'make distcheck' passes
* Do a test installation and make sure all files are properly dist-ed/install-ed
* No 'blocker' bugs against the upcoming release in bugzilla
Preparing:
Pre-releases:
* Bump nano number up in configure.ac (ex: 0.15.91 -> 0.15.92)
* Re-autogen
* Make sure pre-requisites are still valid
* Commit
* Generate the complete ChangeLog file:
* docs/makeChangelog.py > ChangeLog
Releases (major or bugfixes):
* Bump minor number up in configure.ac and remove the nano (ex: 0.15.92 -> 0.16)
* Re-autogen
* Make sure pre-requisites are still valid
* Update the following files:
* pitivi.org/versions.txt: add new release as current
* ChangeLog (see the instructions in the previous section)
* RELEASE. To get the list of contributors,
* 'git shortlog -s -n RELEASE-<previoustag>..'
* NEWS (Using the changes from RELEASE)
* AUTHORS (if there are new contributors)
* Commit
* git tag -a RELEASE-X_YY_Z # For major releases, Z = 0
* Use git push --tags to ensure the tags are published on the remote
Publishing (for both releases and pre-releases):
* 'make distcheck' again to get the tarball
* 'scp pitivi-X.YY.ZZ.tar.bz2 master.gnome.org:'
* On master.gnome.org, run 'ftpadmin install pitivi-X.YY.ZZ.tar.bz2'.
The tarball will appear on http://ftp.gnome.org/pub/gnome/sources/pitivi/X.YY/
* Send out an announcement mail to:
* pitivi-pitivi@lists.sourceforge.net
* gstreamer-devel@lists.freedesktop.org
* gnome-i18n@gnome.org (requesting translations update)
Jump to Line
Something went wrong with that request. Please try again.