Difference between revisions of "Geeklog Release Procedures"
From GeeklogWiki
(Started documenting the release procedure (to do) and which sites and places to update) |
(More steps ...) |
||
| Line 1: | Line 1: | ||
This page outlines the necessary steps to perform before, during, and after the release of a new Geeklog version. | This page outlines the necessary steps to perform before, during, and after the release of a new Geeklog version. | ||
| − | = | + | = Pre-Announcements = |
| − | TBD | + | * Obviously, plans for a new release should have been discussed on [http://eight.pairlist.net/mailman/listinfo/geeklog-devel geeklog-devel]. For security releases, the discussion may happen on [http://www.geeklog.net/staticpages/index.php?page=GeeklogSecurity geeklog-security] only. |
| + | * Notify the [http://eight.pairlist.net/mailman/listinfo/geeklog-translations geeklog-translations] mailing list to give translators a chance and a timeframe to update their translations. | ||
| + | |||
| + | |||
| + | = The Tarball = | ||
| + | |||
| + | * make sure the local copy of the repository that is to be released is up to date | ||
| + | * use the <tt>mkdist.sh</tt> script from the [http://project.geeklog.net/cgi-bin/hgwebdir.cgi/tools/ tools repository] to create the tarball | ||
| + | * upload tarball to www.geeklog.net/nightly | ||
| + | * compare md5 checksum with that of the local copy | ||
| + | * unpack tarball on the server | ||
| + | * update site | ||
| + | ** TBD: document traps and pitfalls as well as additional changes to be done on geeklog.net | ||
= Information to Update = | = Information to Update = | ||
| − | * Publish an article on geeklog.net | + | == Geeklog Sites == |
| − | * 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 [http://project.geeklog.net/cgi-bin/hgwebdir.cgi/tools/ tools repository]. | + | |
| − | * Send out an email to the [http://eight.pairlist.net/mailman/listinfo/geeklog-announce geeklog-announce] mailing list. Provide a brief description of the release and link to the geeklog.net article for details. | + | * Publish an '''article''' on geeklog.net: |
| − | * Update the channel topic on #geeklog on irc.freenode.net | + | ** summarize the changes in this release |
| − | * Update the wiki frontpage (not for betas/release candidates) | + | ** include a link to the entry in the download area |
| + | ** Convention for the story ID: <tt>geeklog-x.y.z</tt>, e.g. geeklog-1.5.2, geeklog-1.4.0sr6 | ||
| + | ** Announcements of new versions go into the [http://www.geeklog.net/index.php?topic=announcements Announcements] topic. For security releases, either post the announcment in the [http://www.geeklog.net/index.php?topic=Security Security] topic, or post two articles (one in Announcements and the details of the security issues in Security). | ||
| + | * 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 [http://project.geeklog.net/cgi-bin/hgwebdir.cgi/tools/ tools repository]. | ||
| + | * Send out an '''email''' to the [http://eight.pairlist.net/mailman/listinfo/geeklog-announce 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) | ||
| + | * Update the '''bugtracker''' (not for betas/release candidates) to ensure the version is removed from the Roadmap and added in dropdowns available for bugreports: | ||
| + | ** Go to Manage -> Manage Projects -> Geeklog 1 -> Versions | ||
| + | ** Edit the version: Set the release date, check the "Released" checkbox | ||
| + | ** Additionally, post a '''news item''' on the [http://project.geeklog.net/tracking/main_page.php bugtracker frontpage] | ||
== External Sites == | == External Sites == | ||
| Line 23: | Line 47: | ||
* [https://sourceforge.net/projects/geeklog sourceforge.net] | * [https://sourceforge.net/projects/geeklog sourceforge.net] | ||
* [https://www.ohloh.net/p/geeklog ohloh.net] | * [https://www.ohloh.net/p/geeklog ohloh.net] | ||
| + | |||
| + | |||
| + | [[Category:Development]] | ||
Revision as of 10:28, 9 February 2009
This page outlines the necessary steps to perform before, during, and after the release of a new Geeklog version.
Contents
Pre-Announcements
- Obviously, plans for a new release should have been discussed on geeklog-devel. For security releases, the discussion may happen on geeklog-security only.
- Notify the geeklog-translations mailing list to give translators a chance and a timeframe to update their translations.
The Tarball
- make sure the local copy of the repository that is to be released is up to date
- use the mkdist.sh script from the tools repository to create the tarball
- upload tarball to www.geeklog.net/nightly
- compare md5 checksum with that of the local copy
- unpack tarball on the server
- update site
- TBD: document traps and pitfalls as well as additional changes to be done on geeklog.net
Information to Update
Geeklog Sites
- Publish an article on geeklog.net:
- summarize the changes in this release
- include a link to the entry in the download area
- Convention for the story ID: geeklog-x.y.z, e.g. geeklog-1.5.2, geeklog-1.4.0sr6
- Announcements of new versions go into the Announcements topic. For security releases, either post the announcment in the Security topic, or post two articles (one in Announcements and the details of the security issues in Security).
- 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)
- Update the bugtracker (not for betas/release candidates) to ensure the version is removed from the Roadmap and added in dropdowns available for bugreports:
- Go to Manage -> Manage Projects -> Geeklog 1 -> Versions
- Edit the version: Set the release date, check the "Released" checkbox
- Additionally, post a news item on the bugtracker frontpage
External Sites
These sites should only be notified about final and security releases (i.e. not for betas and release candidates):
