HOWTO announce a release » History » Version 1
Abhishek Lekshmanan, 10/04/2016 02:43 PM
| 1 | 1 | Abhishek Lekshmanan | h1. HOWTO formally announce a release |
|---|---|---|---|
| 2 | |||
| 3 | * Alfredo announces to QA Lead, Project Lead & Release manager once the final packages are cut |
||
| 4 | * Release manager to create the release notes on the master branch |
||
| 5 | * Make corrections to components as much as possible in the release notes for easier tracking. |
||
| 6 | * Generate a changelog which could be done via |
||
| 7 | <pre> |
||
| 8 | git log tags/<prev.release>..tags/<current.release> |
||
| 9 | </pre> |
||
| 10 | And submit the pr to master; on docs/changelog/<release-version>.txt |
||
| 11 | * 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 |
||
| 12 | * Announce the email preferably with the plain text version of release notes, to, ceph-announce, ceph-users, ceph-maintainers, ceph-devel lists |