evergreen-docs:release_notes_process
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
evergreen-docs:release_notes_process [2019/08/19 19:04] – [Point Release Notes] sandbergja | evergreen-docs:release_notes_process [2024/02/12 15:55] (current) – Release notes from commits stub stompro | ||
---|---|---|---|
Line 4: | Line 4: | ||
====Major Release Notes==== | ====Major Release Notes==== | ||
- | => See also the [[dev: | + | => See also the [[dev: |
===Preparing for the release=== | ===Preparing for the release=== | ||
Line 16: | Line 16: | ||
- After this script is run, make all copyediting, | - After this script is run, make all copyediting, | ||
+ | ==(Fixme: Proposed Enhancement)Extract Release Notes From Commits script== | ||
+ | - Use the docs/ | ||
+ | - Release notes for bug fixes that use the *Release-note: | ||
+ | - Contributors List (Author, Committers, Reviewers). | ||
+ | - Sponsors (grabbing the sponsored-by: | ||
+ | - See [[https:// | ||
+ | - Enhance these instructions once the script has been used. | ||
===Acknowledgements for Major Releases=== | ===Acknowledgements for Major Releases=== | ||
Line 30: | Line 37: | ||
* Acknowledge translators who added translations for one of the ' | * Acknowledge translators who added translations for one of the ' | ||
* Acknowledge documenters who have contributed documentations for new features in this release. As is the case with code contributors, | * Acknowledge documenters who have contributed documentations for new features in this release. As is the case with code contributors, | ||
- | * Acknowledge authors of any tests that were written for that release. Tests are most often written with the code for a new feature or a bug fix. However, when a test is written apart from any new feature or bug fix, those tests are typically merged to the master | + | * Acknowledge authors of any tests that were written for that release. Tests are most often written with the code for a new feature or a bug fix. However, when a test is written apart from any new feature or bug fix, those tests are typically merged to the main branch and not backported. Therefore, those authors should be acknowledged in the major release notes. |
* For **organizations whose employees contributed patches**, identify the library institutions, | * For **organizations whose employees contributed patches**, identify the library institutions, | ||
Line 42: | Line 49: | ||
- Repeat the process for each other relevant release. | - Repeat the process for each other relevant release. | ||
- Push the commits to the release notes to the following branches: | - Push the commits to the release notes to the following branches: | ||
- | * master | + | * main |
* the newer major release branch (e.g. rel_17_10) | * the newer major release branch (e.g. rel_17_10) | ||
* the older major release branch, but only include the changes to the earlier branch (e.g. don't put the 17.10 changes in the rel_17_9 branch). | * the older major release branch, but only include the changes to the earlier branch (e.g. don't put the 17.10 changes in the rel_17_9 branch). |
evergreen-docs/release_notes_process.1566255870.txt.gz · Last modified: 2022/02/10 13:34 (external edit)