Release Checklist

From PERPWiki

Jump to: navigation, search

Steps to be done as part of doing a release

Contents

Update lang files

The lang files are probably outdated. Update the lang files by loading an eTemplate from each application, and clicking "Write Langfile". This should be done sufficiently in advance for translators to update the translations.

Update example and starter SQL

... as soon as I find that script...

Update docs

The user documentation is always updated as fast as possible, but the API docs and ER diagrams should be updated. API docs use Doxygen, just re-generate the docs and upload to server. The ER diagrams can be updated by going to devel.projecterp.org/perp_<app>/setup/

Branch trunk

svn copy https://perp.svn.sourceforge.net/svnroot/perp/trunk/ https://perp.svn.sourceforge.net/svnroot/perp/releases/[release_number] -m "Creating release [release_number] from trunk (rev [rev #])"

Change to branch

$ svn switch https://svn.sourceforge.net/svnroot/perp/releases/[release_number] Or check out the branch to work with it: svn co https://perp.svn.sourceforge.net/svnroot/perp/releases/[release_number]/ ./[release_number]

Update ChangeLog

The program svn2cl is a handly little thing to convert an SVN change log into a traditional change log file.

svn2cl --authors=/home/nathan/perp_authors --group-by-day --break-before-msg --include-path --strip-prefix=trunk -r <release revision>:<last release revision>

Update README

Add any changes or notes specific to this release, and remove anything from prior releases.

Create Package

Creating the actual tarball is a multi-step process.

  1. Copy the release directory outside the SVN working copy. cp -r ../<release> ~/<release>
  2. Change to that directory cd ~/<release>
  3. Delete .svn hidden directories find . -name .svn -print0 | xargs -0 rm -rf
  4. Tar the contents tar -cf pERP-[release_number].tar *
  5. Gzip the tar gzip pERP-[release_number].tar

Post File

Releases are hosted on sourceforge.net, so the files need to be posted there. After posting, the file should be downloaded and verified, preferably by creating a new installation from it.

Redo

Immediately after posting the file, some embarrassing bug will be discovered that really should be fixed.

Retrieved from "http://www.projecterp.org/mediawiki/index.php/Release_Checklist"
Personal tools