• OpenHPI
• OpenHPI
• ReleaseSteps

This is a best stab at the structure that should lead up to a release. Feel free to change as appropriate.

R - 10 days

1. Use OpenHPI/Tools to help with the release tracker and announcement

2. Update tracker page http://openhpi.sourceforge.net/tracker/, see where we are at

3. Announce impending freeze on the mailing list with link to the updated tracker

R - 3 days (Freeze Day)

1. Update tracker page http://openhpi.sourceforge.net/tracker/, see where we are at (again)

2. Update README for release (check version and comments to ensure they are still applicable
3. Ensure Versions are Correct:
   • tarball version - configure.ac
   • lib version - configure.ac

4. OPTIONAL: Creating new branch only : Set branch of format <Major(M)>.<Minor(mm)>.x

   • svn cp https://openhpi.svn.sourceforge.net/svnroot/openhpi/openhpi/trunk \

     • https://openhpi.svn.sourceforge.net/svnroot/openhpi/openhpi/branches/M.mm.x

5. Roll RC tarball (make distcheck) for testing. In particular, test "make install" with tarball to be sure that files are installed in right places.

R - 3 days -> R - 1 days

1. March through OpenHPI/ReleaseCriteria

   • If releasing the SNMP Subagent, follow the OpenHPI_SNMP_subAgent/ReleaseCriteria

2. Fix bugs in branch (remerge with HEAD if appropriate)
   • Checkout the branch
   • From within co branch:

     • svn merge -r<rev num low>:<rev num high> --dry-run https://openhpi.svn.sourceforge.net/svnroot/openhpi/openhpi/trunk (dry-run is for testing)

     • svn merge -r<rev num low>:<rev num high> https://openhpi.svn.sourceforge.net/svnroot/openhpi/openhpi/trunk (do it for real)

   • After the merge, check in the changes to the working copy of the branch.
3. Rinse, Repeat

R day

1. Ensure OpenHPI/ReleaseCriteria is met

2. Set release tag of format <Major(M)>.<Minor(mm)>.<FIX version (f)>

   • svn cp https://openhpi.svn.sourceforge.net/svnroot/openhpi/openhpi/branches/M.mm.x \

     • https://openhpi.svn.sourceforge.net/svnroot/openhpi/openhpi/tags/M.mm.f

3. Increment trunk version number

   • tarball version - configure.ac
   • lib version - configure.ac

4. make dist, and upload to SourceForge

   • Sourceforge.net -> Admin tab -> File Releases

5. Announcements:
   1. Announce on sourceforge
      • openhpi-devel mailing list.
      • openhpi-announce mailing list.
      • Sourceforge openhpi news
   2. Update OpenHPI.org Web Site with release announce

      • Generate changelog using OpenHPI/Tools:

        * sf2xml_scrape.py <release>

        scrape sourceforge for closed features and bugs

        * xml2changelog.py <release>

        generate changelog, text format

        * xml2changelog.py -w <release>

        generate changelog, wiki format for openhpi.org

      • Create wiki changelog page for the release.

      • Then, create news blurb in the LatestNews wiki page.

      • Also, update the Downloads page accordingly.
   3. Add Freshmeat.net record:
      • Login and "add release" for OpenHPI.
      • Go through the steps, fill in the blanks to create the announcement.
   4. Update irc.freenode.net#openhpi topic