Release notes template: Difference between revisions
From MoodleDocs
(Adding API changes section) |
David Mudrak (talk | contribs) m (→Tips: Improve the command to dump it in wiki friendly syntax) |
||
(7 intermediate revisions by 3 users not shown) | |||
Line 5: | Line 5: | ||
Release date: Not yet released | Release date: Not yet released | ||
Here is [ | Here is [https://tracker.moodle.org/secure/IssueNavigator!executeAdvanced.jspa?jqlQuery=project+%3D+mdl+AND+resolution+%3D+fixed+AND+fixVersion+in+%28%22X.X.X%22%29+ORDER+BY+priority+DESC&runQuery=true&clear=true the full list of fixed issues in X.X.X]. | ||
===Highlights=== | ===Highlights=== | ||
Line 27: | Line 27: | ||
* ... | * ... | ||
==See also== | |||
*[[Moodle X.X.X-1 release notes]] | *[[Moodle X.X.X-1 release notes]] | ||
Line 34: | Line 34: | ||
[[fr:Notes de mise à jour de Moodle X.X.X]] | [[fr:Notes de mise à jour de Moodle X.X.X]] | ||
[[es:Notas de Moodle X.X.X]] | |||
</code> | </code> | ||
[[es:Plantilla para las notas de versiones|Plantilla en Español]] | ===Tips=== | ||
The following git command can be used to find all upgrade.txt files that were modified since the last release, so that links to them can be provided in the release notes - typically in the For developers section. | |||
$ git log --oneline --pretty="format:" --name-only v3.5.0..v3.6.0-beta | grep upgrade.txt | sort | uniq | while read path; do echo "* [https://git.in.moodle.com/moodle/moodle/blob/v3.6.0-beta/$path $path]"; done | |||
[[:es:Plantilla para las notas de versiones|Plantilla en Español]] | |||
[[Category:Release notes]] | [[Category:Release notes]] | ||
[[Category:Processes|Release process]] | [[Category:Processes|Release process]] |
Revision as of 09:41, 20 November 2018
Copy and paste this wiki code into the new Release Notes page and replace all the missing bits.
Releases > Release notes template
Release date: Not yet released
Here is the full list of fixed issues in X.X.X.
Highlights
- ...
Functional changes
- ...
API changes
- ...
Security issues
A number of security related issues were resolved. Details of these issues will be released after a period of approximately one week to allow system administrators to safely update to the latest version.
Fixes and improvements
- ...
See also
Tips
The following git command can be used to find all upgrade.txt files that were modified since the last release, so that links to them can be provided in the release notes - typically in the For developers section.
$ git log --oneline --pretty="format:" --name-only v3.5.0..v3.6.0-beta | grep upgrade.txt | sort | uniq | while read path; do echo "* $path"; done