-
Notifications
You must be signed in to change notification settings - Fork 25
Release Procedure
Jonathan Stout edited this page Oct 7, 2019
·
9 revisions
- To release a new version of OESS, create a new branch named
<version>-release
where version is something like2.0.6
; Ask around if you're not sure which version number to use. - Next, update the following files to use the new version number.
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
- 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. - Create a pull request, verify all tests pass, and then receive merge approval from the project manager.
- Lastly begin working through manual integration tests. Ask around if you can't find the integration test spreadsheet.
- Assuming all integration tests pass, sign Jenkins built RPMs and add to GlobalNOC public and private RPM repositories.