all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: zimoun <zimon.toutoune@gmail.com>
To: Marius Bakke <marius@gnu.org>
Cc: "Jakub Kądziołka" <kuba@kadziolka.net>,
	"Guix Devel" <guix-devel@gnu.org>
Subject: Re: branch staging updated: gnu: ghc-7: Clean up package definition.
Date: Wed, 3 Jun 2020 00:02:09 +0200	[thread overview]
Message-ID: <CAJ3okZ3_688WYrcRn8SPwjb+cw4iLXbQNjvNMEZfyFOtj_YJ2g@mail.gmail.com> (raw)
In-Reply-To: <87tuztuson.fsf@gnu.org>

Dear,

On Tue, 2 Jun 2020 at 22:19, Marius Bakke <marius@gnu.org> wrote:

> Also, we'd have to bother the Savannah admins every time we 'freeze' a
> branch.

However, we could ask to extend the list of tags used by Debbugs.  For
example, by adding the tag 'release-critical' or any other
well-chosen.


> Another option could be to create a tracking bug with a special tag that
> can be displayed by issues.guix.gnu.org.  It could also show any merge
> blockers such as <https://issues.guix.gnu.org/issue/41598> to make it
> easier to contribute.

Yes.  And similar thing could be done for release.  Special subject
string that Mumi could parse to report accordingly on
issues.guix.gnu.org and blocking tags to synchronize.  I already
thought loud like that [1]. :-)

[1] https://lists.gnu.org/archive/html/guix-devel/2020-04/msg00380.html


All the best,
simon


      parent reply	other threads:[~2020-06-02 22:02 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20200601154315.6307.59562@vcs0.savannah.gnu.org>
2020-06-02 19:22 ` branch staging updated: gnu: ghc-7: Clean up package definition Marius Bakke
2020-06-02 19:45   ` Jakub Kądziołka
2020-06-02 20:19     ` Marius Bakke
2020-06-02 21:13       ` Jakub Kądziołka
2020-06-02 22:10         ` zimoun
2020-06-02 22:02       ` zimoun [this message]

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=CAJ3okZ3_688WYrcRn8SPwjb+cw4iLXbQNjvNMEZfyFOtj_YJ2g@mail.gmail.com \
    --to=zimon.toutoune@gmail.com \
    --cc=guix-devel@gnu.org \
    --cc=kuba@kadziolka.net \
    --cc=marius@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 external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.