Nebula/Releases/New Release

This page describes how to create a new release.

Nebula uses the major.minor.service version semantics

New Minor Release Checklist

A minor release is a new release without an API break. The Minor Release versioning updates the second number e.g. 2.7.0 -> 2.8.0

• Announce the release on the mailing list
• Create a service release in the project administration
• Add GitHub Artifacts for a Minor Release
• Create a Release Bug
• Classify bugs
• Update the version in the main feature
• Cherry-pick the changes on a working branch
• Create a PR in Github (but do not merge)
• Update the Build configuration
• Promote a build candidate
• Announce and Test the Candidate
• Update the Website
• Add the Release to Github
• Close the Github Milestone
• Update the NAN
• Announce Success

New Service Release Checklist

A Service Release is to fix a bug in the minor release. Service releases have the third number of the release set. e.g. 2.7.0 -> 2.7.1 The following steps are needed to create a new Nebula Service Release. To avoid unneeded risks, you must cherry-pick your changes on top of the latest released tag.

Before you start, open a new workspace and import this project set via Import/Team/Team Project Set.

• Announce the service release on the mailing list
• Create a service release in the project administration
• Add GitHub artifacts for a Service Release
• Create a Release Bug
• Classify bugs
• Update the version in the main feature
• Cherry-pick the changes on a working branch
• Create a PR in Github (but do not merge)
• Update the Build configuration
• Promote a build candidate
• Announce and Test the Candidate
• Update the Website
• Add the Release to Github
• Close the Github Milestone
• Update the NAN
• Announce Success