aboutsummaryrefslogtreecommitdiffhomepage
path: root/RELEASING
Commit message (Collapse)AuthorAge
* RELEASING: Remove obsolete step about updating micro version number.Gravatar Carl Worth2010-04-15
| | | | | | | We've now changed to using "git describe" to automatically report a version number that changes with every git commit. So we no longer need to manually update anything in the Makefile during the release process.
* Makefile: Make "make release" run the test suite.Gravatar Carl Worth2010-04-15
| | | | | This drops one manual step from our release process, (helping to ensure we don't forget anything during the release).
* RELEASING: Update instructions for new version technique.Gravatar Carl Worth2010-04-09
| | | | | We pass this in on the "make release" command-line rather than editing the Makefile.
* Makefile: Print template for release announcement.Gravatar Carl Worth2010-04-05
| | | | | At the end of "make release" or at any point later with "make release-message".
* Makefile: Make the "make release" target push the new tag.Gravatar Carl Worth2010-04-05
| | | | Otherwise I'm sure I'll always forget to push it.
* Makefile: Start implementing a "make release" target.Gravatar Carl Worth2010-04-05
| | | | | So far just doing checks that the version is sane and that no release of the same version already exists.
* RELEASING: Add this file describing the steps to make a release.Gravatar Carl Worth2010-04-05
These steps might be changing a bit as we work on making the initial 0.1 release.