From: Tomi Ollila <tomi.ollila@iki.fi>
To: David Bremner <david@tethera.net>,
Felipe Contreras <felipe.contreras@gmail.com>,
Felipe Contreras <felipe.contreras@gmail.com>,
notmuch@notmuchmail.org
Subject: RE: Final call for news for 0.18
Date: Fri, 02 May 2014 12:06:50 +0300 [thread overview]
Message-ID: <m2siosa6s5.fsf@guru.guru-group.fi> (raw)
In-Reply-To: <878uqkdhlx.fsf@maritornes.cs.unb.ca>
On Fri, May 02 2014, David Bremner <david@tethera.net> wrote:
> Felipe Contreras <felipe.contreras@gmail.com> writes:
>
>>
>>> Also NEWS for these changes are missing.
>>
>> Shouldn't the NEWS be written by the maintainers? In fact, aren't they
>> the ones that decide if something is worth mentioning in the NEWS or
>> not?
>>
>
> Hi Felipe;
>
> I guess for the Vim/ruby stuff you're best positioned to judge what is
> important. We run a kind of pyramid scheme: people generally submit
> short summaries of their own user visible changes; this is the first
> release that I've written a short summary of that.
That said (by David) I'm happy w/ your revised patch set, provided you
also add a NEWS patch, on top of 'release' branch.
For writing NEWS patch: NEWS patches should be written by the one authoring
the corresponding change. And everyone else judges whether the NEWS are
good enough, and the iteration goes on. Finally unless NEWS are
satisfactionary, the patches in question are reverted from the repository >;D
I.e. ease the work of maintainers by providing relevant NEWS by the time of
release :D
>
> d
Tomi
next prev parent reply other threads:[~2014-05-02 9:07 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-30 23:18 Final call for news for 0.18 David Bremner
2014-04-30 23:18 ` [PATCH] NEWS: add overview section " David Bremner
2014-04-30 23:37 ` Final call for news " Felipe Contreras
2014-05-01 19:43 ` Tomi Ollila
2014-05-01 22:43 ` Felipe Contreras
2014-05-02 2:44 ` David Bremner
2014-05-02 9:06 ` Tomi Ollila [this message]
2014-05-02 9:08 ` Tomi Ollila
2014-05-01 14:41 ` [PATCH 0/5] some more " Jani Nikula
2014-05-01 14:41 ` [PATCH 1/5] NEWS: notmuch insert respects maildir.synchronize_flags Jani Nikula
2014-05-01 14:41 ` [PATCH 2/5] NEWS: emacs: push mark before signature on reply Jani Nikula
2014-05-01 14:42 ` [PATCH 3/5] NEWS: cli exit status codes Jani Nikula
2014-05-01 14:42 ` [PATCH 4/5] NEWS: message piping working directory Jani Nikula
2014-05-01 14:42 ` [PATCH 5/5] NEWS: insert and new refuse invalid tags Jani Nikula
2014-05-01 22:36 ` David Bremner
2014-05-03 23:44 ` Final call for news for 0.18 David Bremner
2014-05-05 1:31 ` Felipe Contreras
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://notmuchmail.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m2siosa6s5.fsf@guru.guru-group.fi \
--to=tomi.ollila@iki.fi \
--cc=david@tethera.net \
--cc=felipe.contreras@gmail.com \
--cc=notmuch@notmuchmail.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.
Code repositories for project(s) associated with this public inbox
https://yhetil.org/notmuch.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).