Release Procedure

1. To release a new version of OESS, create a new branch named <version>-release where version is something like 2.0.6; Ask around if you're not sure which version number to use.
2. Next, update the following files to use the new version number.

   Makefile
   oess.spec
   app/Makefile
   app/oess-core.spec
   frontend/Makefile
   frontend/oess-frontend.spec
   perl-lib/OESS/MANIFEST
   perl-lib/OESS/lib/OESS/Database.pm
   perl-lib/OESS/perl-OESS.spec
   perl-lib/OESS/share/nddi.sql
   

3. Add database upgrade script share/upgrade/oess-0.0.0-0.0.1 to perl-lib/OESS/MANIFEST.
4. Create a database upgrade script named perl-lib/OESS/share/upgrade/oess-<pre-version>-<version>. Use an existing upgrade script to more quickly complete this process.
5. Regenerate web api documentation by running the following command from the base project directory, and commit all generated files.

   make documentation
   

6. Create a pull request, verify all tests pass, and then receive merge approval from the project manager.
7. Lastly begin working through manual integration tests. See the testing section of this wiki for a link to the manual testing spreadsheet.
8. Assuming all integration tests pass, sign Jenkins built RPMs and add to GlobalNOC public and private RPM repositories.