view · edit · print · history

To Do List (in order) to prepare a binary release.

  • Add an appropriate tag to the monotone repository to capture the revision which has the candidate for a release:
Edit DISTRO_VERSION in conf/distro/openslug.conf
monotone commit
monotone tag <revision> <release name> (the revision should be the one generated by the commit).
  • Check out the tagged monotone revision into the SVN trunk.
You must have the full SVN repo tree:
svn checkout svn+ssh://svn.berlios.de/svnroot/repos/openslug openslug
cd openslug/trunk/openslug
rm -rf monotone
monotone --db=your.db --revision=<revision> co monotone
scripts/copyclone -c monotone openembedded
Does this look ok? Check it carefully...
scripts/copyclone monotone openembedded
diff -r --exclude=.svn --exclude==MT monotone openembedded
to make sure (the directories should be identical after copyclone).
svn commit
  • Make the release (snapshot) by creating a branch in the SVN tree.
svn copy svn+ssh://svn.berlios.de/svnroot/repos/openslug/trunk/openslug svn+ssh://svn.berlios.de/svnroot/repos/openslug/releases/OpenSlug-<release>
  • Create Source Tarball for release from SVN.
cd openslug/releases/OpenSlug-<release>
make openslug-source
mv openslug-source.tar.gz OpenSlug-<release>.tar.gz
  • Test SVN snapshot (make sure it builds.)
mkdir test
cd test
tar -xzf .../OpenSlug-<release>.tar.gz
  • File release the source tarball at berlios.de and sf.net.
Follow the instructions on the respective web sites.
  • Generate a clean binary from the released source from berlios.de.
  • Upload binary to be tested.
  • Test binary.
  • Package up binary with license, and documentation.
  • Point download link to binary package.
view · edit · print · history · Last edited by ByronT.
Based on work by jbowler, ka6sox, and ByronT.
Originally by ByronT.
Page last modified on August 08, 2005, at 02:15 PM