Jump to: navigation, search

QA/releases

< QA

Projects with only Branches

For the most part Devstack and Grenade only have branches, which need to be cut when other projects get stable/* branches during a release.

Devstack

The branch process for Devstack is as follows:

  1. Wait for stable/branch to exist on the bulk of projects in devstack repo
  2. Ask Release Team to create a stable/foo branch
  3. Update .gitreview and stackrc in stable/foo to reference the new branch
  4. Update lib/tempest to hardcode max microversions and extensions

Grenade

The branch process for Grenade is as follows:

  1. Wait for stable/branch to exist on Devstack
  2. Ask Release Team to create a stable/foo branch
  3. Update .gitreview and grenaderc in stable/foo to reference the new branch
    1. Example: https://review.openstack.org/129645
  4. Update grenaderc in master to reference the new branch
    1. Example: https://review.openstack.org/128959
  5. Update devstack-gate logic to use the new branches
    1. Example: https://review.openstack.org/128974/

Project Releases

tempest

With the start of branchless tempest there are no long any tempest releases, but instead incremental tags for each OpenStack release milestones. The tag should be incremented to coincide with either a new OpenStack release, or the EOL of a supported stable branch. For example, the tempest-2 tag was added at the Juno release and was used to mark adding support for the Kilo release. The next tag tempest-3 will be used to either signify the start of L development or the EOL of icehouse, whichever occurs first. In addition, the tempest repository contains library interfaces based on https://specs.openstack.org/openstack/qa-specs/specs/tempest/implemented/reintegrate-tempest-lib.html So we are releasing new tags in the middle of releases also for new library interfaces. Please see https://github.com/openstack/tempest/releases/tag/12.1.0 as the sample.

The procedure for pushing a new tempest tag is:

  • Check the format of the existing tags
       $ git tag -n
  • Check a new reno before tagging. You can see a new reno on the first report
       $ reno report .

You can check it from http://docs.openstack.org/releasenotes/tempest/unreleased.html also

  • Once the version bump is in master you can tag the release and push it to gerrit with:
       $ git tag -s (version number like "12.1.0")
       $ git push gerrit (version number like "12.1.0")

this will add the signed tag to the git repo and generate a tarball and store it here: http://tarballs.openstack.org/tempest/

If you face the following problem, you need to run "$ git review -s" before pushing:

      $ git push gerrit 14.0.0
      fatal: 'gerrit' does not appear to be a git repository
      fatal: Could not read from remote repository.
      Please make sure you have the correct access rights
      and the repository exists.

tempest-lib

NOTE: tempest-lib itself has been deprecated now, so we never need to release a new tempet-lib anymore

Hacking

Versioning: http://docs.openstack.org/developer/hacking/readme.html#versioning

Hacking has a branch for every major.minor release. For example: 0.9.x and 0.8.x. The process for cutting a new major or minor release involves creating a new branch and pushing a tag (major.minor.0). At that point patches that fit the versioning requirements can be backported to the stable branch for maintenance releases.

The releasing way is the same as Tempest one.

eslint-config-openstack

This project follows the release model of Hacking (above), with a branch for every major.minor release (ex: 0.9.x and 0.8.x). Please refer to the above for process and procedure.

To perform a release, please first install npm on your system. Then, perform the following steps:

   # Check out the most recent master.
   git checkout master; git pull;
   # Ask NPM to update the package version, and tag the release.
   npm version (major|minor|patch)
   # Push the new tag to gerrit
   git push --tags
   # Request for a code review on the new version tag.
   git review
   # Ask NPM to publish the tag to npmjs.com
   # (This step will be deprecated by https://review.openstack.org/#/c/199725/)
   npm publish