unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: zimoun <zimon.toutoune@gmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: Guix Devel <guix-devel@gnu.org>
Subject: Re: Guix minor version update?
Date: Fri, 24 Jan 2020 18:08:09 +0100	[thread overview]
Message-ID: <CAJ3okZ1j5Fr8rOeysoqj4-2ALtm1yzXxRa7riiWgTp2VszJREQ@mail.gmail.com> (raw)
In-Reply-To: <871rrqqgqk.fsf@gnu.org>

Hi Ludo,

On Thu, 23 Jan 2020 at 17:28, Ludovic Courtès <ludo@gnu.org> wrote:

> I think we really need someone to pay attention to the schedule.  It’s
> too hard for me and I guess for many of us to, at the same time, hack on
> new things, and sit down to prepare a release, which is often somewhat
> exciting.

Let engage a quick discussion at the Guix Days about that...

> I also think we should rotate release responsibilities.  We’ve improved
> the process and its documentation in the past, but I’m sure we can still
> do better.

...and that.


Because now Guix is becoming a piece of software \o/ and so more bugs
are opened than closed (no stats! :-)) then new features are touching
very different topics, we could imagine that 2-3 people take in charge
the release responsibilities because it would ease triage between what
is blocking and what is not.
Well, as usual, the difficult part is to bootstrap from scratch. ;-)
And the skills that are required are a bit abstract -- at least to me
-- so how to reach volunteers? :-)


Well, let talk at the Guix Days what could be done. :-)


Cheers,
simon

  parent reply	other threads:[~2020-01-24 17:08 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-21 13:32 Guix minor version update? zimoun
2020-01-21 15:37 ` Pierre Neidhardt
2020-01-21 17:43 ` Julien Lepiller
2020-01-22  1:35   ` Bengt Richter
2020-01-23 16:28   ` Ludovic Courtès
2020-01-24 16:31     ` Jonathan Frederickson
2020-01-24 17:08     ` zimoun [this message]
2020-01-23 15:42 ` Ludovic Courtès

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=CAJ3okZ1j5Fr8rOeysoqj4-2ALtm1yzXxRa7riiWgTp2VszJREQ@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).