Jump to: navigation, search

Difference between revisions of "Nova/ReleaseChecklist"

(added to Nova category)
(Post-release Checklist)
 
(7 intermediate revisions by 4 users not shown)
Line 4: Line 4:
  
 
* Merge latest translations
 
* Merge latest translations
 +
* Bump rpc major versions.  See [[RpcMajorVersionUpdates]]
 +
* If products drop out of support, or have stopped being tested, we should ensure we warn users, so we have the option to remove them in the following release, if needed. In other words, make sure that the release notes are up to date, especially the upgrade notes.
 +
* Ideally add the RPC version alias just before opening the next release
 +
* Add a reno 'prelude' section describing the most important changes in the release
 +
* Make sure there are no *-rc-potential bugs in launchpad, or anything that was an rc-potential bug is properly deferred.
  
 
=== Post-release Checklist ===
 
=== Post-release Checklist ===
  
* Add database migration placeholders to allow backportable DB migrations
+
* Add database migration placeholders to allow backportable DB migrations. For example, Pike backports added in Queens: https://review.openstack.org/#/c/496932/
* Bump rpc major versions to drop old compat code.  See [[RpcMajorVersionUpdates]]
+
* Drop old rpc compat code.  See [[RpcMajorVersionUpdates]]
* Update version aliases for rpc outbound version control
+
* Update version aliases for rpc outbound version control. For example, the Newton RPC aliases were added in Ocata: https://review.openstack.org/#/c/386625/
  
 
[[Category:Nova]]
 
[[Category:Nova]]

Latest revision as of 03:08, 25 August 2017

This page is for tracking things that we should be doing in the code before or after each release.

Pre-release Checklist

  • Merge latest translations
  • Bump rpc major versions. See RpcMajorVersionUpdates
  • If products drop out of support, or have stopped being tested, we should ensure we warn users, so we have the option to remove them in the following release, if needed. In other words, make sure that the release notes are up to date, especially the upgrade notes.
  • Ideally add the RPC version alias just before opening the next release
  • Add a reno 'prelude' section describing the most important changes in the release
  • Make sure there are no *-rc-potential bugs in launchpad, or anything that was an rc-potential bug is properly deferred.

Post-release Checklist