Development/Releasing

From Sit

Jump to: navigation, search
SiT! Manual SiT! Manual Developers Guide → Development/Releasing Chapter 6

Some notes on the steps needed to publish a release

  • Get the revision number of the last release, one way to find this is to see the 'tags' in subversion

http://sitracker.svn.sourceforge.net/viewvc/sitracker/tags/

Getting a changelog, where 4533 is the last release revision number 

svn2cl --revision HEAD:4533 --group-by-day --include-rev --authors "doc/AUTHORS" -o "/tmp/changelog"
  • Update Translation page
  • Update Upgrading and doc/UPGRADING
  • Set a target for Mantis issues that were resolved since the last release date but have no target set
  • Update doc/Changelog
  • Update doc/README
  • Set 'Fixed in Current SVN' issues in Mantis to Fixed in this version
  • Update wiki ReleaseNotes
  • Update releasenotes.php
  • Change version number in lib/base.inc.php
  • Tag the release 
svn cp https://sitracker.svn.sourceforge.net/svnroot/sitracker/trunk \
https://sitracker.svn.sourceforge.net/svnroot/sitracker/tags/release-X.YY -m "Tagging the X.YY release of SiT"
  • Branch the release in case further fixes need to go in here 
svn cp https://sitracker.svn.sourceforge.net/svnroot/sitracker/trunk \
https://sitracker.svn.sourceforge.net/svnroot/sitracker/branches/X.YY -m "Branching the X.YY release of SiT"
  • Update the version number in trunk ready for the next release after this one
  • Build the release packages 
release-tools/tools/create-release.sh tags/release-X.YY
  • Check that the phpcheck file created by the release script is empty, i.e. contains no errors
  • Check the sit_X.YY.tar.gz file created by the release script extracts ok and looks correct
  • Add a new release on Sourceforge (make a folder via the web interface first) 
scp sit_X.yy.tar.gz username,sitracker@frs.sourceforge.net:/home/frs/project/s/si/sitracker/stable/X.yy
  • Update the wiki release notes with the download link
  • Edit the release notes redirect to point to this versions release notes
  • Add release notice to sourceforge project news
  • Blog the release under the category 'News'
  • Mark this version released and set release date in Mantis
  • Announce the release in the IRC channel topic
  • Announce the release in the forum
  • Close all the bugs in Mantis that are marked fixed in this release


VM

  • Follow the guide on Development/VM to create a new VM.
  • Upload the Source code of the OS (Preferable Ubuntu) if it's a new release to http://sitracker.org/VM including an MD5 hash file of the iso
  • 7zip the VM and name it VMware_SiT_X.YY.7z where X is the major version and YY is the lesser version (example VMware_SiT_3.51.7z).
  • Generate a MD5 hash file of the compressed VM and name it the same name as the compressed file with extension .md5
  • Upload both files to http://sourceforge.net/projects/sitracker/files/stable/X.YY
  • Modify Download section VM to modify the links
  • Add the new version to the vmware appliance page
  • Announce on freshmeat
Retrieved from "http://sitracker.org/wiki/Development/Releasing"
Personal tools
project