This is a best stab at the structure that should lead up to a release. Feel free to change as appropriate.
R - 14 days
Use OpenHPI/Tools to help with the release tracker and announcement
Update tracker page http://openhpi.sourceforge.net/tracker/, see where we are at
- Announce impending freeze on the mailing list with link to the updated tracker
R - 7 days (Freeze Day)
Update tracker page http://openhpi.sourceforge.net/tracker/, see where we are at (again)
- Update README for release (check version and comments to ensure they are still applicable
- Ensure Versions are Correct:
- tarball version - configure.ac
- lib version - configure.ac
- Windows build versions - Makefile.mingw32.def
C# baselib - baselibs/csharp/openhpi_baselib/AssemblyInfo.cs
- Java baselib - baselibs/java/openhpi_baselib/manifest.txt
Python baselib - baselibs/python/openhpi_baselib/OhpiVersion.py
OPTIONAL: Creating new branch only : Set branch of format <Major(M)>.<Minor(mm)>.x
- If a new branch was not created above, then update the current branch with the current contents of the trunk
- 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.
Increment trunk version number so that further development can proceed. At this point, any bugs will need to be fixed in both the trunk and branch.
- tarball version - configure.ac
- lib version - configure.ac
- Windows build versions - Makefile.mingw32.def
- Roll RC tarball (make distcheck) for testing. In particular, test "make install" with tarball to be sure that files are installed in right places. Do not hand out the tarball, in case it changes during the freeze week.
- Announce the freeze on openhpi-devel, asking people to test the top of the frozen branch.
R - 7 days -> R - 1 days
March through OpenHPI/ReleaseCriteria
If releasing the SNMP Subagent, follow the OpenHPI_SNMP_subAgent/ReleaseCriteria
- Fix bugs in branch (remerge with trunk 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.
- Rinse, Repeat
R day
Ensure OpenHPI/ReleaseCriteria is met
Set release tag of format <Major(M)>.<Minor(mm)>.<FIX version (f)>
make dist, and upload to SourceForge
Sourceforge.net -> Admin tab -> File Releases
- Announcements:
- 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.
- Note that the top-level "Status" page is pretty out of date...update this!
- Announce on sourceforge
- openhpi-devel mailing list.
- openhpi-announce mailing list.
- Sourceforge openhpi news
- Add Freshmeat.net record:
- Login and "add release" for OpenHPI.
- Go through the steps, fill in the blanks to create the announcement.
- Update irc.freenode.net#openhpi topic
- Update OpenHPI.org Web Site with release announce