HOWTO announce a release » History » Version 9
Nathan Cutler, 07/23/2019 11:11 AM
1 | 8 | Nathan Cutler | h3. HOWTO 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 | 9 | Nathan Cutler | * Release manager to create the release notes by submitting a patch to <code>doc/releases/<named_branch>.rst</code> as a PR targeting the *master* branch |
6 | 6 | Nathan Cutler | ** Release notes are generated using the script <code>src/script/ceph-release-notes</code> |
7 | ** Make manual corrections to components as much as possible in the release notes for easier tracking. |
||
8 | 5 | Abhishek Lekshmanan | |
9 | 7 | Abhishek Lekshmanan | * Once http://docs.ceph.com/docs/master/release-notes/ 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 (alternatively just ask jenkins to render docs via jenkins render docs and copy paste the related html |
10 | , 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. |
||
11 | 5 | Abhishek Lekshmanan | |
12 | * 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 |
||
13 | |||
14 | 3 | Abhishek Lekshmanan | * Inform Patrick (@scuttlemonkey) about the release so that @ceph tweets the release |