From: ludo@gnu.org (Ludovic Courtès)
To: Ricardo Wurmus <rekado@elephly.net>
Cc: guix-devel@gnu.org
Subject: Re: What should go in our NEWS file?
Date: Sun, 22 Apr 2018 22:05:18 +0200 [thread overview]
Message-ID: <87r2n7gg75.fsf@gnu.org> (raw)
In-Reply-To: <87h8o3thjy.fsf@elephly.net> (Ricardo Wurmus's message of "Sun, 22 Apr 2018 16:57:37 +0200")
Hello,
Ricardo Wurmus <rekado@elephly.net> skribis:
>> The Guix source tree contains a NEWS file in its root directory. What
>> is supposed to go into this NEWS file? When should we update it?
>
> It’s updated prior to making a release.
Committers following along should feel empowered to add noteworthy items
there, and not just right before the release. This has to be rather
concise because there are so many things going on, and rather about
“important” changes, in the categories that Ricardo mentions.
I’m saying this because updating NEWS right before the release can be
quite cumbersome, and it’s also easy to overlook important things, so
any contribution in that regard can be very helpful!
Ludo’.
next prev parent reply other threads:[~2018-04-22 20:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-22 8:03 What should go in our NEWS file? Chris Marusich
2018-04-22 14:57 ` Ricardo Wurmus
2018-04-22 20:05 ` Ludovic Courtès [this message]
2018-04-22 22:17 ` Ricardo Wurmus
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://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87r2n7gg75.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guix-devel@gnu.org \
--cc=rekado@elephly.net \
/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/guix.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).