Creating a new Nebula Release

Creating a new Nebula 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.

Steps to Create a New Minor Release:

• Announce the Release on Mailing List
• Create Service Release in Project Administration
• Add GitHub Artifacts for Minor Release
• Create Release Bug
• Classify Bugs
• Update Build Configuration
• Update Version in Main Feature
• Promote Build Candidate
• Announce and Test Candidate
• Update Website
• Add Release to GitHub
• Close GitHub Milestone
• Update NAN
• Announce Success

New Service Release Checklist

A Service Release is intended 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. To create a new Nebula Service Release, follow the steps below. 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.

Steps to Create a New Service Release:

• Announce Service Release on Mailing List
• Create Service Release in Project Administration
• Add GitHub Artifacts for Service Release
• Create Release Bug
• Classify Bugs
• Update Version in Main Feature
• Cherry-Pick Changes on Working Branch
• Create Pull Request in GitHub
• Update Build Configuration
• Promote Build Candidate
• Announce and Test Candidate
• Update Website
• Add Release to GitHub
• Close GitHub Milestone
• Update NAN
• Announce Success