HOWTO announce a release » History » Version 4
Abhishek Lekshmanan, 02/15/2017 08:59 AM
| 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 | * 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 | 4 | Abhishek Lekshmanan | * Generate a changelog (this is only for backport releases) which could be done via |
| 7 | 1 | Abhishek Lekshmanan | <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 |
||
| 13 | 3 | Abhishek Lekshmanan | * Inform Patrick (@scuttlemonkey) about the release so that @ceph tweets the release |