Geeklog Release Procedures

From GeeklogWiki
Revision as of 21:29, 8 February 2009 by Dirk (talk | contribs) (Started documenting the release procedure (to do) and which sites and places to update)

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search

This page outlines the necessary steps to perform before, during, and after the release of a new Geeklog version.

Creating the Tarball

TBD


Information to Update

  • Publish an article on geeklog.net, linking to the tarball and summarizing the changes in this release. Convention for the story ID: geeklog-x.y.z, e.g. geeklog-1.5.2, geeklog-1.4.0sr6
  • Update the versionchecker.php script (not for betas/release candidates). Requires access to webserver. Once updated, the new version of the script should be added to the tools repository.
  • Send out an email to the geeklog-announce mailing list. Provide a brief description of the release and link to the geeklog.net article for details.
  • Update the channel topic on #geeklog on irc.freenode.net
  • Update the wiki frontpage (not for betas/release candidates)

External Sites

These sites should only be notified about final and security releases (i.e. not for betas and release candidates):

Retrieved from "http://wiki.geeklog.net/index.php?title=Geeklog_Release_Procedures&oldid=4831"