| Table of Contents |
|---|
...
Prerequisites
Git Branches
Release plan and actions assumes that all OpenNCP modules are being developed in git branch named "develop" and the "master" branch is being kept in sync with latest releases. It is recommended also to enable in your development environment the git flow extensions (http://danielkummer.github.io/git-flow-cheatsheet/)When performing a release of OpenNCP and publicising the artifacts
JIRA Workflow
Each issue in JIRA has the following tags related to release process
- OpenNCP affects Version
- OpenNCP fix Version
- Affects Version
- Fix Version
When an issue is opened is tagged with the "affects" related tags (OpenNCP affects Version and Affects Version).
Each OpenNCP version is a list of components that have their version numbers. This relation is being hold in the Version Management page. So the previous tags relate to these 2 types of versions (openncp version and component version)
Notification of developers
...
| Info |
|---|
Before starting with the actual release steps, the |
...
Each component has a corresponding JIRA project, which has a version corresponding to this release. This version must be marked as 'released' and any pending (non-resolved) issues must be moved to the next release version. All issues that have been resolved in this release must be update with the "Fix OpenNCP Version" to point to this release. Also they have to be tagged with "Fix Version" with the component version
Cleaning up
remove the local and the remote git branches:
...