HOWTO announce a release » History » Version 5
Abhishek Lekshmanan, 06/23/2017 12:55 PM
| 1 | 2 | Loïc Dachary | h3. HOWTO formally announce a release |
|---|---|---|---|
| 2 | 1 | Abhishek Lekshmanan | |
| 3 | * Alfredo announces to QA Lead, Project Lead & Release manager once the final packages are cut |
||
| 4 | 5 | Abhishek Lekshmanan | |
| 5 | 1 | Abhishek Lekshmanan | * Release manager to create the release notes on the master branch |
| 6 | 5 | Abhishek Lekshmanan | |
| 7 | 1 | Abhishek Lekshmanan | * Make corrections to components as much as possible in the release notes for easier tracking. |
| 8 | 5 | Abhishek Lekshmanan | |
| 9 | 4 | Abhishek Lekshmanan | * Generate a changelog (this is only for backport releases) which could be done via |
| 10 | 1 | Abhishek Lekshmanan | <pre> |
| 11 | git log tags/<prev.release>..tags/<current.release> |
||
| 12 | </pre> |
||
| 13 | And submit the pr to master; on docs/changelog/<release-version>.txt |
||
| 14 | 5 | Abhishek Lekshmanan | |
| 15 | * Once docs.ceph.com updates with the above files, and the right urls are checked, do a blog post on ceph.com with the correct links, this can be copy-pasted from the html rendered release notes, also the blog post can be saved as a draft in advance so that the publish button can be clicked once the packages are out. |
||
| 16 | |||
| 17 | |||
| 18 | * Announce the email preferably with the plain text version of release notes, use discretion if the changelog is large.. in that case just a link to the blog might suffice with the major release announcements only in the email. The mail needs to be sent to ceph-announce, ceph-users, ceph-maintainers, ceph-devel lists |
||
| 19 | |||
| 20 | 3 | Abhishek Lekshmanan | * Inform Patrick (@scuttlemonkey) about the release so that @ceph tweets the release |