From: Andrey Albershteyn <aalbersh@redhat.com>
To: linux-xfs@vger.kernel.org
Cc: "Darrick J. Wong" <djwong@kernel.org>,
Andrey Albershteyn <aalbersh@kernel.org>
Subject: [PATCH v5 00/10] Update release.sh
Date: Wed, 26 Feb 2025 15:50:25 +0100 [thread overview]
Message-ID: <20250226-update-release-v5-0-481914e40c36@kernel.org> (raw)
To: linux-xfs@vger.kernel.org
The release.sh seems to be last updated in 2015. Every one seems to have
their own script to release. This patchset updates release.sh to do the
basic stuff as updating version files, committing them, creating tag,
creating release tarball, uploading tarball (optional), generate
for-next announce.
Just a few minor fixes from v4, see below.
--
Andrey
---
Changes in v5:
- Use --separator instead of --delimiter for git-contributors.py in
release.sh: generate ANNOUNCE email
- Check return code of gpg --verify-signature in
release.sh: add signing and fix outdated commands
- Add argument to $(basename) in help() in
release.sh: add --kup to upload release tarball to kernel.org
- Link to v4: https://lore.kernel.org/r/20250213-update-release-v4-0-c06883a8bbd6@kernel.org
Changes in v4:
- Add a few from recently generated files to gitignore
- Drop Cc: trailers in libxfs-apply
- Better handling of trailers with multiple emails/hash marks/not quoted
names
- Link to v3: https://lore.kernel.org/r/20250211-update-release-v3-0-7b80ae52c61f@kernel.org
Changes in v3:
- Add -f to generate for-next ANNOUNCE email
- Update for-next when new released is pushed
- Link to v2: https://lore.kernel.org/r/20250122-update-release-v2-0-d01529db3aa5@kernel.org
Changes in v2:
- Added git-contributors.py from Darrick
- A bit better/shorter commands for maintainer to run
- Link to v1: https://lore.kernel.org/r/20250110-update-release-v1-0-61e40b8ffbac@kernel.org
---
Andrey Albershteyn (10):
release.sh: add signing and fix outdated commands
release.sh: add --kup to upload release tarball to kernel.org
release.sh: update version files make commit optional
Add git-contributors script to notify about merges
git-contributors: better handling of hash mark/multiple emails
git-contributors: make revspec required and shebang fix
release.sh: generate ANNOUNCE email
release.sh: add -f to generate for-next update email
libxfs-apply: drop Cc: to stable release list
gitignore: ignore a few newly generated files
.gitignore | 2 +
release.sh | 189 +++++++++++++++++++++++++++++++++++++++++++---
tools/git-contributors.py | 168 +++++++++++++++++++++++++++++++++++++++++
tools/libxfs-apply | 1 +
4 files changed, 348 insertions(+), 12 deletions(-)
---
base-commit: 4fd999332e19993fb7fd381f5fcd40ff943d98ac
change-id: 20241111-update-release-13ef17c008a5
Best regards,
--
Andrey Albershteyn <aalbersh@kernel.org>
next reply other threads:[~2025-02-26 14:50 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-26 14:50 Andrey Albershteyn [this message]
2025-02-26 14:50 ` [PATCH v5 01/10] release.sh: add signing and fix outdated commands Andrey Albershteyn
2025-02-26 14:50 ` [PATCH v5 02/10] release.sh: add --kup to upload release tarball to kernel.org Andrey Albershteyn
2025-02-26 14:50 ` [PATCH v5 03/10] release.sh: update version files make commit optional Andrey Albershteyn
2025-02-26 14:50 ` [PATCH v5 04/10] Add git-contributors script to notify about merges Andrey Albershteyn
2025-02-26 14:50 ` [PATCH v5 05/10] git-contributors: better handling of hash mark/multiple emails Andrey Albershteyn
2025-02-26 14:50 ` [PATCH v5 06/10] git-contributors: make revspec required and shebang fix Andrey Albershteyn
2025-02-26 14:50 ` [PATCH v5 07/10] release.sh: generate ANNOUNCE email Andrey Albershteyn
2025-02-26 14:50 ` [PATCH v5 08/10] release.sh: add -f to generate for-next update email Andrey Albershteyn
2025-02-26 14:50 ` [PATCH v5 09/10] libxfs-apply: drop Cc: to stable release list Andrey Albershteyn
2025-02-26 14:50 ` [PATCH v5 10/10] gitignore: ignore a few newly generated files Andrey Albershteyn
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20250226-update-release-v5-0-481914e40c36@kernel.org \
--to=aalbersh@redhat.com \
--cc=aalbersh@kernel.org \
--cc=djwong@kernel.org \
--cc=linux-xfs@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox