Difference between revisions of "Nova/ReleaseChecklist"
< Nova
John Garbutt (talk | contribs) (→Pre-release Checklist) |
(→Pre-release Checklist) |
||
| Line 7: | Line 7: | ||
* 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. | * 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. | ||
* Ideally add the RPC version alias just before opening the next release | * 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 | ||
=== Post-release Checklist === | === Post-release Checklist === | ||
Revision as of 09:08, 15 March 2016
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.
- 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
Post-release Checklist
- Add database migration placeholders to allow backportable DB migrations
- Drop old rpc compat code. See RpcMajorVersionUpdates
- Update version aliases for rpc outbound version control
