From: zimoun <zimon.toutoune@gmail.com>
To: Leo Famulari <leo@famulari.name>
Cc: Guix Devel <guix-devel@gnu.org>
Subject: Re: Release 1.2.1: status
Date: Sun, 21 Mar 2021 00:00:20 +0100 [thread overview]
Message-ID: <86y2ehv3az.fsf@gmail.com> (raw)
In-Reply-To: <YFZUtOlQP0fhY6lE@jasmine.lan>
Hi Leo,
On Sat, 20 Mar 2021 at 16:01, Leo Famulari <leo@famulari.name> wrote:
> I suggest we use debbugs to keep track of tasks for the release.
>
> We can create a new bug called "1.2.1 release checklist".
>
> This bug can be made to depend on other bugs using the "block" feature
> of debbugs:
>
> https://debbugs.gnu.org/server-control.html
>
> Concretely, this means we send email to debbugs with messages like
> "block NNN with YYY", which means that NNN cannot be closed until YYY is
> closed.
>
> What do you think? Should I create a new bug ticket for this?
We discussed that and I agree. We also discussed some tagging and Maxim
did some tests, IIRC. Please go ahead and let try if it helps to
synchronize. :-)
Cheers,
simon
next prev parent reply other threads:[~2021-03-20 23:03 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-18 14:28 Release 1.2.1: status zimoun
2021-03-19 6:37 ` Chris Marusich
2021-03-19 8:27 ` Christopher Baines
2021-03-19 8:50 ` zimoun
2021-03-20 18:09 ` Leo Famulari
2021-03-20 22:56 ` zimoun
2021-03-20 23:21 ` Leo Famulari
2021-03-19 18:31 ` Andreas Enge
2021-03-19 21:59 ` Luis Felipe
2021-03-20 23:03 ` zimoun
2021-03-19 22:26 ` Luis Felipe
2021-03-21 0:16 ` zimoun
2021-03-21 14:05 ` bug#47293: guix lint -c archival icecat fails Luis Felipe via Bug reports for GNU Guix
2021-03-21 14:23 ` bug#47293: Failure of “guix lint -c archival icecat” zimoun
2021-03-21 19:39 ` Mark H Weaver
2021-03-25 23:25 ` bug#47293: guix lint -c archival icecat fails Ludovic Courtès
2021-03-21 14:13 ` Release 1.2.1: status Luis Felipe
2021-03-20 20:01 ` Leo Famulari
2021-03-20 23:00 ` zimoun [this message]
2021-03-21 17:54 ` Leo Famulari
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=86y2ehv3az.fsf@gmail.com \
--to=zimon.toutoune@gmail.com \
--cc=guix-devel@gnu.org \
--cc=leo@famulari.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.
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.