How to Make a Release: Difference between revisions
From OPeNDAP Documentation
⧼opendap2-jumptonavigation⧽
| Line 3: | Line 3: | ||
== Set Tasks for a Release == | == Set Tasks for a Release == | ||
;Verify CI and fix as needed | ;Verify CI and fix as needed | ||
;Security Review libdap & bes | ;Security Review libdap & bes | ||
;Security review OLFS | ;Security review OLFS | ||
| Line 9: | Line 9: | ||
;Source release BES | ;Source release BES | ||
;Build OLFS release bundles | ;Build OLFS release bundles | ||
;Build RPMs for release. | ;Build RPMs for release | ||
;Software packages on website | |||
;Update Hyrax release pages on website | |||
;Install new sever on test.opendap.org | |||
Revision as of 22:30, 28 October 2015
Overview
To plan a sprint there are two basic sets of tasks: cleaning up the left over bugs that have accumulated during the past sprints and then working on a set of predictable tasks. This page lists those predictable tasks and some notes about the various releases. In the burndown chart built by Jira, there is a Time Spent column that tells how long each of the various tasks really took. While it's impossible to predict how long some of the stuff will take, previous performance is the best tool we've got, as they say...
Set Tasks for a Release
- Verify CI and fix as needed
- Security Review libdap & bes
- Security review OLFS
- Source release libdap
- Source release BES
- Build OLFS release bundles
- Build RPMs for release
- Software packages on website
- Update Hyrax release pages on website
- Install new sever on test.opendap.org
