From: Siddhesh Poyarekar <siddhesh@gotplt.org>
To: Florian Weimer <fw@deneb.enyo.de>
Cc: Carlos O'Donell <carlos@redhat.com>,
Max Gautier <mg@max.gautier.name>,
GLIBC Devel <libc-alpha@sourceware.org>
Subject: Re: Contribution Checklist - ChangeLog
Date: Thu, 20 Aug 2020 23:28:44 +0530 [thread overview]
Message-ID: <79ea0c20-0cf3-5c25-579d-67b0200959c0@gotplt.org> (raw)
In-Reply-To: <1138b3e2-51a7-440a-6c2c-55e817de4f44@gotplt.org>
On 20/08/20 14:12, Siddhesh Poyarekar wrote:
> My personal bias is towards not having to write ChangeLog entries at
> all. We could make it happen by backporting the ChangeLog script to
> older stable branches and then drop the ChangeLog requirement altogether.
>
> As an aside, I'm thinking of separating out the stable branch (and all
> of the old addons, ports, etc.) related stuff out into a separate page
> so that this checklist remains short and simple. Stable branches have
> historically only been touched by distribution maintainers and I doubt
> if that will change in the near future given that we don't cut releases
> off stable branches. I'll do this too tonight if nobody objects.
Aha, so this is where I updated the Checklist and then forgot to merge
the changes in:
https://sourceware.org/glibc/wiki/Contribution%20checklist%20v2
I'll hack on this to get y'all to review and this time around, remember
to merge the changes back :)
Siddhesh
next prev parent reply other threads:[~2020-08-20 17:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20200819154837.GA182209@ol-mgautier.localdomain>
[not found] ` <87k0xud3y7.fsf@mid.deneb.enyo.de>
[not found] ` <20200819162227.GA183107@ol-mgautier.localdomain>
[not found] ` <f0662ff8-0897-f833-f49e-09a2fabdfd7e@redhat.com>
[not found] ` <CAAHN_R1z4BqsvW7W578nbfjfb-LdL4beP0bMeJiVFF3KNajkdg@mail.gmail.com>
[not found] ` <877dttbvim.fsf@mid.deneb.enyo.de>
2020-08-20 8:42 ` Siddhesh Poyarekar
2020-08-20 17:58 ` Siddhesh Poyarekar [this message]
2020-08-20 18:03 ` Carlos O'Donell
2020-08-20 18:11 ` Siddhesh Poyarekar
2020-08-22 17:05 ` Siddhesh Poyarekar
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=79ea0c20-0cf3-5c25-579d-67b0200959c0@gotplt.org \
--to=siddhesh@gotplt.org \
--cc=carlos@redhat.com \
--cc=fw@deneb.enyo.de \
--cc=libc-alpha@sourceware.org \
--cc=mg@max.gautier.name \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).