From: Bengt Richter <bokr@bokr.com>
To: Leo Famulari <leo@famulari.name>
Cc: Guix Devel <guix-devel@gnu.org>,
Maxim Cournoyer <maxim.cournoyer@gmail.com>,
zimoun <zimon.toutoune@gmail.com>
Subject: Re: GNU Guix 1.4.0 in September? (was: Re: GNU Guix 1.3.0 released)
Date: Mon, 17 May 2021 19:35:25 +0200 [thread overview]
Message-ID: <20210517173525.GA9279@LionPure> (raw)
In-Reply-To: <YKKBGGvP8vvRzpiE@jasmine.lan>
Hi all,
On +2021-05-17 10:43:36 -0400, Leo Famulari wrote:
> On Mon, May 17, 2021 at 02:55:39PM +0200, zimoun wrote:
> > I remember a plot sent to guix-maintaainers about the number of grafts,
> > the core-updates merges and the release dates. I am not sure it is
> > really interesting and it is worth to resend it, or maybe dumping the
> > Cuirass database to investigate a bit more. Well, my point is the
> > core-updates merges and the release dates should be synchronized; say
> > target the core-updates for end of September, then the release for
> > November. To me, this synchronisation makes senses because it
> > constraints the ~6months core-updates cycle and in the same time, the 2
> > releases per year.
>
> I like this idea.
>
This sounds like planning activity.
Gnome has an app called planner ;-)
Would it make sense to discuss a way to put these rc- and other related goals
on a gantt chart?
Maybe even automate import from mailing list emails marked with e.g. [release-planning] in the subject
and one delimited markup region like
--8<---------------cut here---------------start------------->8---
planner-importable xml here
--8<---------------cut here---------------end--------------->8---
Discussion without triggering automated import would just leave
"[release-plannng]" out of the Subject: line, or have e.g. [release-discussion]
in the Subject: line.
Anyway, I thought a nice gantt chart .svg or .png or .pdf might be nice :)
Thoughts?
--
Regards,
Bengt Richter
next prev parent reply other threads:[~2021-05-17 17:36 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-12 6:40 GNU Guix 1.3.0 released Maxim Cournoyer
2021-05-12 7:58 ` Paul Jewell
2021-05-12 11:43 ` 宋文武
2021-05-12 12:35 ` Mathieu Othacehe
[not found] ` <Maxim Cournoyer's message of "Wed, 12 May 2021 02:40:39 -0400">
[not found] ` <OSZP286MB06642FFB3BB362E2E85BE9D4A3529@OSZP286MB0664.JPNP286.PROD.OUTLOOK.CO M>
2021-05-12 12:02 ` maxxcan--- via
2021-05-15 16:42 ` Ludovic Courtès
2021-05-16 13:18 ` GNU Guix 1.4.0 in September? (was: Re: GNU Guix 1.3.0 released) Maxim Cournoyer
2021-05-16 16:02 ` Vagrant Cascadian
2021-05-16 16:47 ` Julien Lepiller
2021-05-17 12:55 ` zimoun
2021-05-17 14:43 ` Leo Famulari
2021-05-17 15:01 ` GNU Guix 1.4.0 in September? Maxim Cournoyer
2021-05-17 17:35 ` Bengt Richter [this message]
2021-05-17 20:29 ` Maxim Cournoyer
2021-05-17 20:34 ` Maxim Cournoyer
2021-05-17 20:32 ` Ludovic Courtès
2021-06-16 7:49 ` Chris Marusich
2021-06-20 16:26 ` Debbugs user tags Ludovic Courtès
2021-06-23 2:48 ` Chris Marusich
2021-06-23 13:53 ` Ludovic Courtès
2021-06-24 4:59 ` Chris Marusich
2021-06-24 19:48 ` GNU Guix 1.4.0 in September? Maxim Cournoyer
2021-06-24 20:48 ` Debbugs Usertags - which user to use? (Was: Re: GNU Guix 1.4.0 in September?) Chris Marusich
2021-06-25 3:23 ` Debbugs Usertags - which user to use? Maxim Cournoyer
2021-07-06 4:22 ` Chris Marusich
2021-07-06 16:10 ` Maxim Cournoyer
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=20210517173525.GA9279@LionPure \
--to=bokr@bokr.com \
--cc=guix-devel@gnu.org \
--cc=leo@famulari.name \
--cc=maxim.cournoyer@gmail.com \
--cc=zimon.toutoune@gmail.com \
/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.