docs: document the new release process

Release tarballs are only available on github from now on.

diff --git a/docs/RELEASE.md b/docs/RELEASE.md
index 2e1a73fbc8585d576f9bfad80dbff8ac635c4871..ba2cd00d41979dbf06246537dcaec115f737c63a 100644 (file)
--- a/docs/RELEASE.md
+++ b/docs/RELEASE.md
@@ -40,31 +40,7 @@ This documents contains the necessary steps to conduct a successful release.
 
    Add the section from `NEWS.md` to the git tag message.
 
-6. Push git to kernel.org
-
-   With:
-   ```console
-   $ git remote add kernelorg ssh://gitolite@ra.kernel.org/pub/scm/boot/dracut/dracut.git
-   ```
-
-   Push to kernel.org git:
-   ```console
-   $ git push --atomic kernelorg master "$VERSION"
-   ```
-
-
-7. Sign and upload tarballs to kernel.org
-
-   ```console
-   $ make upload
-   ```
-
-   This requires `kup` and a kernel.org account.
-   Wait until the tarballs are synced to http://www.kernel.org/pub/linux/utils/boot/dracut/ .
-
-8. Create a new release on github (https://github.com/dracutdevs/dracut/releases/new)
+6. Create a new release on github (https://github.com/dracutdevs/dracut/releases/new)
    - Add the section from `NEWS.md` to the release.
-   - Attach the tarballs and signature file from http://www.kernel.org/pub/linux/utils/boot/dracut/ to the github release.
 
-9. Close the github milestone and open a new one (https://github.com/dracutdevs/dracut/milestones)
-10. Ensure that announcement was sent and reached the linux-initramfs mailinglist (https://www.spinics.net/lists/linux-initramfs/)
+7. Close the github milestone and open a new one (https://github.com/dracutdevs/dracut/milestones)