9.1. Release Process

  1. Update the version number in include/header.php, doc/version.xml, doc/administration/bmfo_administration_guide.xml, doc/user/en/bmfo_user_guide.xml, build.xml, bmfo.nsi, bmfo-client.nsi, servlet/WEB-INF/web.xml, etc/index.html and doc/development/doxygen/doxygen.cfg.

  2. Verify that all SQL DDL scripts are running without errors (redirect output to file).

  3. Check that the webtest is passed.

  4. Review Apache's error.log after running the web test.

  5. Check that the UML diagrams in doc/development are up to date.

  6. Update all translations (See Section 4). Don't forget the Java ResourceBundles.

  7. Add the necessary information to the Updating section of the administration guide.

  8. Check that the documentation build is passed.

  9. Update the NEWS file and the "What's New" section in the BMFO user guide.

  10. In the Subversion repository, copy all files to the appropriate folder under /tags. Include the version information, e.g. /tags/bmfo/BMFO_1_0_8. This can be done with the TortoiseSVN repository browser.

  11. Delete temporary files.

  12. Create a zipfile using build.xml. Create the installers.

  13. Update the documentation on the CD.

  14. Check the links on the CD.

  15. Update etc/index.html. Create a BMFO CD and test.

  16. Release the zipfile and installer on sourceforge.

  17. Upload the updated documentation to Sourceforge.

  18. Create a news item on sourceforge.

  19. Update http://bmfo.sourceforge.net - this is done automatically with RSS for the main page. Update the docs on the website.

  20. Update the freshmeat entry (http://freshmeat.net).

  21. Send a release notice to .

  22. Announce the new release on http://www.omsproject.com.jo