1
0
Fork 0
mutter-performance-source/doc/RELEASING
Neil Roberts 0a83e03afb doc/RELEASING: Fix the check for diffs from origin/master
The recommended command to check for differences from master to the
remote master was using git log with a range from the local master to
the remote master but this wouldn't work if the local master is ahead
of the remote master because the range is backwards. This patch
changes it to recommend git diff --stat instead because then the
command would work even if the two branches have diverged.
2011-06-29 16:16:25 +01:00

64 lines
1.5 KiB
Text

RELEASING
=========
When making a new release;
- Verify that you don't have uncommitted and unpublished
changes, i.e. both this:
$ git status
and this:
$ git diff --stat master origin/master
should be empty. Commit and push before the next step.
- Clean your work directory:
$ git clean -xdf
This ensures that you don't have stale files lying around.
- Run:
$ ./autogen.sh --enable-gtk-doc --enable-docs
$ make all
$ make check
And verify that the code builds from a clean Git snapshot.
- Update the release documentation:
- NEWS: new feature details, bugs fixed, acknowledgements
- README: dependencies, any behavioural changes relevant to
developers;
then commit the changes.
- Bump clutter_micro_version to the next even number; if this is a stable
release, bump up clutter_interface_version by one as well. Then commit
the changes.
- Run:
$ make release-publish
which will:
- do sanity checks on the build
- distcheck the release
- tag the repository with the version number
- upload the tarball to the remote server (needs SSH account)
- Bump clutter_micro_version to the next odd number; if this is a stable
release, bump up clutter_interface_version by one as well. Then commit
the changes.
- Push the branch and then the tag, e.g.:
$ git push origin master
$ git push origin 1.2.4
- Announce release to the waiting world on the blog and mailing lists. Use
the template printed by `make release-publish`.