To create new wiki account, please join us on #znc at Libera.Chat and ask admins to create a wiki account for you. You can say thanks to spambots for this inconvenience.

HowToRelease

From ZNC
Revision as of 13:57, 4 November 2013 by DarthGandalf (talk | contribs)
Jump to navigation Jump to search
The printable version is no longer supported and may have rendering errors. Please update your browser bookmarks and please use the default browser print function instead.

TODO

Should the changelog become part of the release tarballs? Just the latest changelog or a concatenation of all changelogs?

Preparation

  1. Check todo lists and bug trackers.
  2. Check whether our-of-source builds still work.
  3. Release an "-alpha1" and notice that nobody tests it.
  4. Do a "-beta1" which still no one tests.
  5. For "-rc1", we finally do some version number changes
    1. Update version number in *version.h* and *configure.ac* (use VERSION-rc1 here)
    2. git add all modified files, so that make-tarball.sh picks them up.
    3. Fix make-tarball.sh to add -rc1 to VERSION_EXTRA (TODO: do it automatically)
    4. Release tarball. (./make-tarball.sh VERSION-rc1).

Release, release, release

  1. Revert the changes from above
  2. Prepare changelog.txt based on ChangeLog/git, let everyone check it
  3. git pull!!!!
  4. Update version number in *version.h* and *configure.ac*
  5. Commit ("Increase the version number to foo")
  6. Create tarball (make-tarball.sh VERSION)
  7. Tag the new version in git (Use the changelog as commit msg, first line is "ZNC 1.foo")
    1. git tag -s znc-1.foo HEAD
  8. Bump version number to foo+1. (Commit msg: "Increase the version number to foo+1")
  9. Update the wiki
    1. Move ChangeLog/git and create that page again.
    2. Update Template:ZNC-Version.
  10. Upload the release files to people.znc.in/.
    1. The files themselves go directly into archive/
    2. The main dir only gets symlinks
  11. Ping Kuja to update znc.in/releases