coreutils/README-release, branch v8.7Mirror of https://https.git.savannah.gnu.org/git/coreutils.git/
https://git.shady.money/coreutils/atom?h=v8.72010-10-03T18:48:53Zmaint: add a release prerequisite: check the NixOS/Hydra autobuilder2010-10-03T18:48:53ZJim Meyeringmeyering@redhat.com2010-10-03T18:48:53Zurn:sha1:2006aeba9d44ecc49fefcba65d93451dc537cd01
* README-release: Add a note to check the autobuilder.
doc: factor hard-coded project-specific bits from README-release, ...2010-05-03T20:21:31ZJim Meyeringmeyering@redhat.com2010-05-03T20:00:30Zurn:sha1:9e42ecceff823a9f966b798bda5b33463d199277
using the new --mail-headers option to gnulib's announce-gen, and
the updated maint.mk rules to connect the pieces.
* README-release: Remove hard-coded To:, Cc: etc. parts, now
that they're emitted automatically into the announcement template.
* cfg.mk (announcement_Cc_): Override the default.
* gnulib: Update to latest, to get newer announce-gen and maint.mk.
doc: update release procedure2010-05-03T18:37:13ZJim Meyeringmeyering@redhat.com2010-05-03T18:37:13Zurn:sha1:ca41dcff1dc4f434b4b53fc9067dd709b8867ef2
* README-release: Rearrange slightly: post the announcement to
Savannah first, so you can include a link to that post in the email.
doc: adjust a header in announcement email template2010-04-08T06:45:23ZJim Meyeringmeyering@redhat.com2010-04-08T06:45:23Zurn:sha1:9e66806e2869504567761d632c806005d51265ca
* README-release: Use Mail-Followup-To: rather than Reply-To:.
The former works more reliably, at least with Gnus.
doc: synchronize parts of README-release from grep's version2010-03-31T06:58:40ZJim Meyeringmeyering@redhat.com2010-03-31T06:58:40Zurn:sha1:6416762b73f5d34bfc3b85f65d82f455da48ad74
* README-release (FIXME): Add Reply-To, use coreutils@gnu.org
for announcements. Update savannah-verbatim-announcement procedure.
doc: rewrite part of README-release2010-02-07T08:10:53ZJim Meyeringmeyering@redhat.com2010-02-07T08:10:53Zurn:sha1:cea6d15720ea595e313a79df55bcb6f3dea1dcc9
* README-release (Pre-release testing): Reorganize.
maint: add missing "post-release push" step to release procedure2010-01-14T13:39:11ZJim Meyeringmeyering@redhat.com2010-01-14T13:39:11Zurn:sha1:eccf54368f51b9492f1e744b66aeb56cea8706e9
* README-release: Push the automated release and post-release
NEWS-updating commits.
Pádraig Brady reported that I'd pushed the tag without also
pushing the followup commit.
build: "make stable" emitted an invalid gnupload command2009-11-18T20:04:52ZJim Meyeringmeyering@redhat.com2009-11-18T20:04:52Zurn:sha1:f18eef32848e2a0d1cc4159799ddc6d652f9ba75
* cfg.mk (gnu_ftp_host-stable): Rename from gnu_ftp_host-major.
* README-release: Change another s/major/stable/.
admin: automate one more part of the release process2009-10-31T10:08:03ZJim Meyeringmeyering@redhat.com2009-10-31T10:08:03Zurn:sha1:6eb457eaba841cc331d566a3f3dd83fc4cc5d058
This script automates the process of updating NEWS, performs
the resulting final commit (thus with a consistent log message),
and applies a signed tag (v$VERSION) to the result.
* build-aux/do-release-commit-and-tag: New script.
* README-release: Document it.
admin: fix typo in release procedure2009-10-31T07:49:46ZJim Meyeringmeyering@redhat.com2009-10-31T07:49:46Zurn:sha1:a276ba2dd43a35fed6f81fa976bece1d3eb48f64
* README-release: s/gzip/coreutils/