4 * after a release, we move in cvs mode and use a .1 nano version number
6 * close to the next release, we make prereleases by upping the nano version
10 * add release notes to cvs
12 * update web site release notes
14 * make distcheck should pass
16 * test suite should pass
18 * autotools have latest config.{guess,sub}
19 This is needed in order to support newer platforms.
20 On Debian install the autotools-dev package to get these.
22 * depending on how the API has changed update the libtool versioning
23 in configure.ac. Look at the libtool info page about versioning for
26 * update package version
29 http://gstreamer.net/dev/cvs.php
33 * update web site news items for release
35 * upload to sourceforge
39 gstreamer-{devel, announce}
42 lwn (if it's a big release)
47 * autoconf feature to allow building outside source dir
51 Package version policy
52 ----------------------
54 Use major.minor.micro versioning
58 Update micro until code and API are fairly stable, then update minor.
63 Update major when code and api hit new level of stability or major features.
64 Update minor on API changes.
65 Update micro on API-compatible changes.