Document the release process

sylvestre · sylvestre · commit ae2b022982e1 · 2025-03-08T12:27:15.000+01:00
diff --git a/DEVELOPMENT.md b/DEVELOPMENT.md
@@ -337,3 +337,12 @@ Otherwise please follow [this guide](https://learn.microsoft.com/en-us/windows/d
 If you have used [Git for Windows](https://gitforwindows.org) to install `git` on you Windows system you might already have some GNU core utilities installed as part of "GNU Bash" included in Git for Windows package, but it is not a complete package. [This article](https://gist.github.com/evanwill/0207876c3243bbb6863e65ec5dc3f058) provides instruction on how to add more to it.
 
 Alternatively you can install [Cygwin](https://www.cygwin.com) and/or use [WSL2](https://learn.microsoft.com/en-us/windows/wsl/compare-versions#whats-new-in-wsl-2) to get access to all GNU core utilities on Windows.
+
+# Preparing a new release
+
+1. Modify `util/update-version.sh` (FROM & TO) and run it
+1. Submit a new PR with these changes and wait for it to be merged
+1. Tag the new release `git tag -a X.Y.Z` and `git push --tags`
+1. Once the CI is green, create a [new release](https://github.com/uutils/coreutils/releases/new).
+1. Write the release notes (it takes time) following previous examples
+1. Run `util/publish.sh` to publish the new release to crates.io
