From: Stefan Kangas <stefankangas@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 42917@debbugs.gnu.org, alex.branham@gmail.com,
Nicolas Petton <nico@petton.fr>
Subject: bug#42917: 27.1; temporary note included in 27 NEWS
Date: Wed, 19 Aug 2020 18:58:57 +0000 [thread overview]
Message-ID: <CADwFkmkag-FZ7cprvBi6f1WTNQ_XG2WcrxuVqH+s1Fxf4mAzxw@mail.gmail.com> (raw)
In-Reply-To: <83o8n6cw93.fsf@gnu.org>
reopen 42917
thanks
(I'm copying in Nico into the discussion.)
Eli Zaretskii <eliz@gnu.org> writes:
> Thanks, but that was a mistake: this part is only removed when
> preparing the release tarball. It cannot be removed in the
> repository, because it must be there for people who make changes in
> NEWS to see. And people do make changes in NEWS, even though this is
> a release branch.
Oh, I double-checked the emacs-26 branch and saw that it was removed
there (but I guess that was right after 26.3). I'll revert that change.
I'm not sure what to do about this then. Should we perhaps add
anything else to admin/release-process to remind about this, for example:
modified admin/release-process
@@ -79,8 +79,10 @@ so e.g. admin/ is fine.) This is important for
legal compliance.
** Remove temporary +++/--- lines in NEWS.
But first make sure there are no unmarked entries, and update the
documentation (or decide no updates are necessary) for those that aren't.
+** Remove "Temporary note" at the top of NEWS.
+
** Try to reorder NEWS: most important things first, related items together.
** For a major release, add a "New in Emacs XX" section to faq.texi.
Best regards,
Stefan Kangas
next prev parent reply other threads:[~2020-08-19 18:58 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-18 18:05 bug#42917: 27.1; temporary note included in 27 NEWS Alex Branham
2020-08-18 18:26 ` Eli Zaretskii
2020-08-19 18:01 ` Stefan Kangas
2020-08-19 18:43 ` Eli Zaretskii
2020-08-19 18:58 ` Stefan Kangas [this message]
2020-08-19 19:22 ` Eli Zaretskii
2020-08-20 9:58 ` Stefan Kangas
2020-08-20 13:26 ` Eli Zaretskii
2020-08-20 14:19 ` Stefan Kangas
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CADwFkmkag-FZ7cprvBi6f1WTNQ_XG2WcrxuVqH+s1Fxf4mAzxw@mail.gmail.com \
--to=stefankangas@gmail.com \
--cc=42917@debbugs.gnu.org \
--cc=alex.branham@gmail.com \
--cc=eliz@gnu.org \
--cc=nico@petton.fr \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).