Difference between revisions of "Storlets/Release Branch Creation"

Latest revision as of 09:26, 23 August 2017

This is a temporary procedure till we are "Big Teneted"

1. In two different patches:
   1. pin the dependencies versions (Swift and Keystone) in tox.ini and in devstack localrc.sample
      1. In tox.ini place in the appropriate line:
         1. git+git://github.com/openstack/swift.git@2.7.0 <---- The version of the stable release
      2. In localrc.sample add e.g.:
         1. SWIFT_BRANCH=stable/ocata
         2. KEYSTONE_BRANCH=stable/ocata
   2. Update CHANGELOG with the tag for the release, and the Release notes.
2. Once the above patches are approved create and push the above-mentioned release tag, this will initiate the PyPI jobs. Make sure your .gitconfig is up-to-date with e.g. the gpg signingkey entry.
   1. git tag -m "stable/newton tag" -s 0.3.0
   2. git push gerrit 0.3.0
3. Create the branch
   1. git checkout -b stable/newton
   2. git push gerrit stable/newton
4. Update the openstack release repo (currently we are in an independent release cycle format)
   1. checkout https://github.com/openstack/releases.git
   2. Edit deliverables/_independent/storlets.yaml
      1. Add the release branch and version in the existing format.
      2. The hash should reflect the hash of the latest commit done before creating the branch point (the CHANGELOG commit)
      3. TODO: Do we need to update this in case of a backport??
5. On master undo the dependencies version pinning
6. If a backport is required checkout the branch and cherry-pick the backport commit:
   1. git checkout stable/newton
   2. git cherry-pick <commit>
   3. git review stable/newton