Revision as of 02:01, 30 November 2013 by KindOne (Include updating the version number on Wikipedia.)
Should the changelog become part of the release tarballs? Just the latest changelog or a concatenation of all changelogs?
- Check todo lists and bug trackers.
- Check whether our-of-source builds still work.
- Release an "-alpha1" and notice that nobody tests it.
- Do a "-beta1" which still no one tests.
- For "-rc1", we finally do some version number changes
- Update version number in *version.h* and *configure.ac* (use VERSION-rc1 here)
git addall modified files, so that make-tarball.sh picks them up.
- Fix make-tarball.sh to add -rc1 to VERSION_EXTRA (TODO: do it automatically)
- Release tarball. (
Release, release, release
- Revert the changes from above
- Prepare changelog.txt based on ChangeLog/git, let everyone check it
- git pull!!!!
- Update version number in *version.h* and *configure.ac*
- Commit ("Increase the version number to foo")
- Create tarball (make-tarball.sh VERSION)
- Tag the new version in git (Use the changelog as commit msg, first line is "ZNC 1.foo")
git tag -s znc-1.foo HEAD
- Bump version number to foo+1. (Commit msg: "Increase the version number to foo+1")
- Update the wiki
- Upload the release files to people.znc.in/.
- The files themselves go directly into archive/
- The main dir only gets symlinks
- Ping Kuja to update znc.in/releases
- Update version number on Wikipedia.