From: zimoun <zimon.toutoune@gmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: Reflections on the release process
Date: Fri, 24 Apr 2020 18:06:31 +0200 [thread overview]
Message-ID: <CAJ3okZ1V2DwQdcnfWGvuzJqYj6cYjX+QLZvMQ4NZGu8iQN6rWQ@mail.gmail.com> (raw)
In-Reply-To: <87y2qns2os.fsf@gnu.org>
On Wed, 22 Apr 2020 at 22:09, Ludovic Courtès <ludo@gnu.org> wrote:
> Yes, but how do we do that? I don’t think Debbugs supports a
> “release-critical” tag, does it? Or perhaps we could take advantage of
> Mumi to add special tags or something?
The GNU instance of Debbugs does not support it, I agree.
However, the Debian instance supports more tags than the GNU one, e.g.,
patch, wontfix, moreinfo, unreproducible, help, security, upstream,
pending, confirmed, ipv6, lfs, d-i, l10n, newcomer, a11y, ftbfs,
fixed-upstream, fixed, fixed-in-experimental, potato, woody, sarge,
etch, lenny, squeeze, wheezy, jessie, stretch, buster, bullseye,
bookworm, sid, experimental, sarge-ignore, etch-ignore, lenny-ignore,
squeeze-ignore, wheezy-ignore, jessie-ignore, stretch-ignore,
buster-ignore, bullseye-ignore, bookworm-ignore
https://www.debian.org/Bugs/
I have not dove into the Debbugs configuration so I do not know if it
is easy or not to extend the list of tags. However, because it is
managed by GNU sysadmin, it should be a long road. ;-)
And I do not know what is the "effect" of the 'block' command. Because
a "release vx.y" bug could be open. And the release critical issues
could be marked as "block release-vx.y". This bug "release vx.y" could
help to synchronise/coordinate and/or track progress and should help
for managing the schedule and deadlines.
I do not know. I am thinking loud.
> I think there’s no question we want more than one release per year. For
> that to happen, we should make sure the process is well documented, as
> smooth as possible, largely automated, and not tied to a single person
> (ahem…).
Agree.
Cheers,
simon
next prev parent reply other threads:[~2020-04-24 16:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-15 20:16 Reflections on the release process Ludovic Courtès
2020-04-17 12:46 ` zimoun
2020-04-22 20:09 ` Ludovic Courtès
2020-04-24 16:06 ` zimoun [this message]
2020-04-24 16:45 ` Gábor Boskovits
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=CAJ3okZ1V2DwQdcnfWGvuzJqYj6cYjX+QLZvMQ4NZGu8iQN6rWQ@mail.gmail.com \
--to=zimon.toutoune@gmail.com \
--cc=guix-devel@gnu.org \
--cc=ludo@gnu.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://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).