From: Mariusz Tkaczyk Date: Wed, 12 Feb 2025 10:29:05 +0000 (+0100) Subject: Move release steps to documentation/ X-Git-Url: http://git.neil.brown.name/?a=commitdiff_plain;h=4b3932487a8dc2e87530e595ccabe48c79446f30;p=mdadm.git Move release steps to documentation/ Make a room for release MAINTAINERS file. Signed-off-by: Mariusz Tkaczyk --- diff --git a/MAINTAINERS.md b/MAINTAINERS.md deleted file mode 100644 index e5b635f0..00000000 --- a/MAINTAINERS.md +++ /dev/null @@ -1,29 +0,0 @@ -# Maintainer tools - -Useful tools for mdadm maintenance: -- [checkpatch](https://docs.kernel.org/dev-tools/checkpatch.html) -- [kup](https://korg.docs.kernel.org/kup.html) -- [Auto-publishing](https://korg.docs.kernel.org/kup.html#auto-publishing-with-git-archive-signer) -- [b4](https://b4.docs.kernel.org/en/latest/) - -# Making a release - -Assuming that maintainer is certain that release is safe, following steps must be done: - -- Make and push release commit: - - Update versions strings, refer to previous releases for examples. - - Update CHANGELOG.md. - -- Create GPG signed tag and push it to both remotes. Use same format as was used previously, - prefixed by **mdadm-**, e.g. **mdadm-3.1.2**, **mdadm-4.1**. - -- Run kernel.org - [Auto-publishing](https://korg.docs.kernel.org/kup.html#auto-publishing-with-git-archive-signer): - - Adopt script to our release tag model. When ready, push signed note to kernel.org repository. If - it is done correctly, then *(sig)* is added to the package automatically generated by - kernel.org automation. There is no need to upload archive manually. - -- Add release entry on Github. - -- Write "ANNOUNCE" mail to linux-raid@kernel.org to notify community. diff --git a/documentation/HOW_TO_RELEASE.md b/documentation/HOW_TO_RELEASE.md new file mode 100644 index 00000000..e5b635f0 --- /dev/null +++ b/documentation/HOW_TO_RELEASE.md @@ -0,0 +1,29 @@ +# Maintainer tools + +Useful tools for mdadm maintenance: +- [checkpatch](https://docs.kernel.org/dev-tools/checkpatch.html) +- [kup](https://korg.docs.kernel.org/kup.html) +- [Auto-publishing](https://korg.docs.kernel.org/kup.html#auto-publishing-with-git-archive-signer) +- [b4](https://b4.docs.kernel.org/en/latest/) + +# Making a release + +Assuming that maintainer is certain that release is safe, following steps must be done: + +- Make and push release commit: + - Update versions strings, refer to previous releases for examples. + - Update CHANGELOG.md. + +- Create GPG signed tag and push it to both remotes. Use same format as was used previously, + prefixed by **mdadm-**, e.g. **mdadm-3.1.2**, **mdadm-4.1**. + +- Run kernel.org + [Auto-publishing](https://korg.docs.kernel.org/kup.html#auto-publishing-with-git-archive-signer): + + Adopt script to our release tag model. When ready, push signed note to kernel.org repository. If + it is done correctly, then *(sig)* is added to the package automatically generated by + kernel.org automation. There is no need to upload archive manually. + +- Add release entry on Github. + +- Write "ANNOUNCE" mail to linux-raid@kernel.org to notify community.