Skip to content
This repository has been archived by the owner on Aug 2, 2023. It is now read-only.

Kabanero Release Process Template

Jump to bottom
Gary Picher edited this page Oct 9, 2019 · 2 revisions

NOTE: This is a template. Kabanero feeder projects should copy this template and include it in their repo's wiki in a page entitled "Release Process", ensuring to delete this comment and properly fill out the template before publishing it.

A new release of this project is created every 4 weeks, at the end of each odd-numbered iteration in the Kabanero Iteration Schedule.

This project follows the Kabanero Release Best Practices, which should be consulted for detailed release information.

Creating A New Scheduled Release

  1. Determine the version of the new release. Typically, this is the same as the version of the last scheduled release but with the minor version number increased, e.g. if the last scheduled release was 0.2.0, the next one is 0.3.0. This version will be referred to as [version] in subsequent steps.

  2. Push a "[version]-rc.1" tag to the repository. This will initiate a Travis build of the source code at this commit.

  3. Run release candidate validation against the resulting build.

    DOCUMENT RELEASE CANDIDATE VALIDATION PROCESS HERE

  4. If the build fails validation, merge fixes into master and go back to Step 2, but increment the release candidate version.

  5. Once the build passes validation, push a "[version]" tag at the same commit of the release candidate that was verified.

  6. If Kabanero Foundation should be updated to this release, open an issue in [that repository] https://github.com/kabanero-io/kabanero-foundation, following the conventions in the Kabanero Release Best Practices.

Clone this wiki locally