HOWTO do dev checkpoint releases » History » Version 3
Abhishek Lekshmanan, 02/15/2017 08:58 AM
| 1 | 1 | Abhishek Lekshmanan | h1. HOWTO do development checkpoint releases |
|---|---|---|---|
| 2 | |||
| 3 | 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. |
||
| 4 | |||
| 5 | # Ask the ceph project lead, Sage on when to cut a release |
||
| 6 | 3 | Abhishek Lekshmanan | # Run a basic rados (with a subset like 1/99) rbd and rgw teuthology suite, ask the respective leads if there are any errors |
| 7 | 1 | Abhishek Lekshmanan | # 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 |
| 8 | # Release notes can be prepared based on this branch |
||
| 9 | # After successful build and a basic sanity test, the git tag is pushed to ceph-releases and ceph repo |
||
| 10 | 2 | Abhishek Lekshmanan | # 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 |
| 11 | 1 | Abhishek Lekshmanan | # 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. |