HOWTO do dev checkpoint releases » History » Revision 3
Revision 2 (Abhishek Lekshmanan, 10/26/2016 08:39 AM) → Revision 3/9 (Abhishek Lekshmanan, 02/15/2017 08:58 AM)
h1. HOWTO do development checkpoint releases
Development checkpoint releases are essentially development snapshots released often until the first release candidate is announced. The process for development checkpoint releases are a bit more ad hoc compared to the formal processes involved for stable releases and for release candidates.
# Ask the ceph project lead, Sage on when to cut a release
# Run a basic rados (with a subset like 1/99) rbd and rgw teuthology suite, ask the respective leads if there are any errors
# On approval, the <release> branch (for eg, kraken) in the ceph-releases repo (this is an exact copy of the ceph repo, only frozen in time in order to avoid commits between the time a release occurs and the long times package builds take place) would be used by the new build service, chacra to build packages. Alfredo triggers the build
# Release notes can be prepared based on this branch
# After successful build and a basic sanity test, the git tag is pushed to ceph-releases and ceph repo
# Ensure the packages are published and signed, and the source tarball is uploaded as this is used for linking in the email to the list
# Once the builds are green and Alfredo gives the approval, announce a release as mentioned in [[HOWTO formally announce release]], the rich view from the release notes rst rendering can be used to publish the blog post.