You've studied the [[Git/hacks]] and built a ton of features, fixes, and updates to your codebase in a sprint worthy of Usain Bolt
You've studied the [[Git/hacks]] and built a ton of features, fixes, and updates to your codebase in a sprint worthy of Usain Bolt [[File:Hussein Bolt.png|thumb]]. Now it's time to create some release notes - which in the tradition of open source is stored in the RELEASE_NOTES file of your project.
[[File:Hussein Bolt.png|thumb]]
. Now it's time to create some release notes - which in the tradition of open source is stored in the RELEASE_NOTES file of your project.
Since your team follows the best practices of writing good commit comments and also creating appropriate branches and pull requests, then it's a simple matter of letting '''[[git]]''' tell you what's in the release. Of course you can amend or add to it as needed.
First, study [[git/log]] for how to use the log command.
Since your team follows the best practices of writing good commit comments and also creating appropriate branches and pull requests, then it's a simple matter of letting ```git``` tell you what's in the release. Of course you can amend or add to it as needed.
Show the whole commit history, but skip any merge commits so that the Release Notes are not cluttered with workflow items.
Date: Tue Jan 7 17:33:33 2025 +0000
Upgrade to REL1_43
Fixes Issue #136
set meza_repository_url to use freephile/meza
set mediawiki_version for core
set mediawiki_default_branch (for extensions)
set php_ius_version to php81
</pre>
I've written up fancier routines for this, but every time they're lost to the client where I've implemented them so this article is a stub to record and improve on the existing practices. See for instance: https://www.mediawiki.org/wiki/Release_notes/data
See Also: https://www.mediawiki.org/wiki/Release_notes/data
[[Category:Best Practices]]
[[Category:Best Practices]]
Revision as of 00:20, 19 August 2025
You've studied the Git/hacks and built a ton of features, fixes, and updates to your codebase in a sprint worthy of Usain Bolt
. Now it's time to create some release notes - which in the tradition of open source is stored in the RELEASE_NOTES file of your project.
Since your team follows the best practices of writing good commit comments and also creating appropriate branches and pull requests, then it's a simple matter of letting git tell you what's in the release. Of course you can amend or add to it as needed.
First, study git/log for how to use the log command.
