Difference between revisions of "Storlets/Release Branch Creation"
< Storlets
| (One intermediate revision by the same user not shown) | |||
| Line 3: | Line 3: | ||
# In two different patches: | # In two different patches: | ||
## pin the dependencies versions (Swift and Keystone) in tox.ini and in devstack localrc.sample | ## pin the dependencies versions (Swift and Keystone) in tox.ini and in devstack localrc.sample | ||
| + | ### In tox.ini place in the appropriate line: | ||
| + | #### git+git://github.com/openstack/swift.git@2.7.0 <---- The version of the stable release | ||
| + | ### In localrc.sample add e.g.: | ||
| + | #### SWIFT_BRANCH=stable/ocata | ||
| + | #### KEYSTONE_BRANCH=stable/ocata | ||
## Update CHANGELOG with the tag for the release, and the Release notes. | ## Update CHANGELOG with the tag for the release, and the Release notes. | ||
# 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. | # 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. | ||
| Line 10: | Line 15: | ||
## git checkout -b stable/newton | ## git checkout -b stable/newton | ||
## git push gerrit stable/newton | ## git push gerrit stable/newton | ||
| + | # Update the openstack release repo (currently we are in an independent release cycle format) | ||
| + | ## checkout https://github.com/openstack/releases.git | ||
| + | ## Edit deliverables/_independent/storlets.yaml | ||
| + | ### Add the release branch and version in the existing format. | ||
| + | ### The hash should reflect the hash of the latest commit done before creating the branch point (the CHANGELOG commit) | ||
| + | ### TODO: Do we need to update this in case of a backport?? | ||
# On master undo the dependencies version pinning | # On master undo the dependencies version pinning | ||
# If a backport is required checkout the branch and cherry-pick the backport commit: | # If a backport is required checkout the branch and cherry-pick the backport commit: | ||
Latest revision as of 09:26, 23 August 2017
This is a temporary procedure till we are "Big Teneted"
- In two different patches:
- pin the dependencies versions (Swift and Keystone) in tox.ini and in devstack localrc.sample
- In tox.ini place in the appropriate line:
- git+git://github.com/openstack/swift.git@2.7.0 <---- The version of the stable release
- In localrc.sample add e.g.:
- SWIFT_BRANCH=stable/ocata
- KEYSTONE_BRANCH=stable/ocata
- In tox.ini place in the appropriate line:
- Update CHANGELOG with the tag for the release, and the Release notes.
- pin the dependencies versions (Swift and Keystone) in tox.ini and in devstack localrc.sample
- 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.
- git tag -m "stable/newton tag" -s 0.3.0
- git push gerrit 0.3.0
- Create the branch
- git checkout -b stable/newton
- git push gerrit stable/newton
- Update the openstack release repo (currently we are in an independent release cycle format)
- checkout https://github.com/openstack/releases.git
- Edit deliverables/_independent/storlets.yaml
- Add the release branch and version in the existing format.
- The hash should reflect the hash of the latest commit done before creating the branch point (the CHANGELOG commit)
- TODO: Do we need to update this in case of a backport??
- On master undo the dependencies version pinning
- If a backport is required checkout the branch and cherry-pick the backport commit:
- git checkout stable/newton
- git cherry-pick <commit>
- git review stable/newton
