From mboxrd@z Thu Jan  1 00:00:00 1970
From: zimoun <zimon.toutoune@gmail.com>
Subject: Re: Guix minor version update?
Date: Fri, 24 Jan 2020 18:08:09 +0100
Message-ID: <CAJ3okZ1j5Fr8rOeysoqj4-2ALtm1yzXxRa7riiWgTp2VszJREQ@mail.gmail.com>
References: <CAJ3okZ1dz6dQZ04wDbxCKLbuhWfQ9wmN8DbjydwVZ_g5cB3qiQ@mail.gmail.com>
 <E20C9EBA-C21A-4655-8C8B-CDA6BDAA1BFD@lepiller.eu> <871rrqqgqk.fsf@gnu.org>
Mime-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Return-path: <guix-devel-bounces+gcggd-guix-devel=m.gmane-mx.org@gnu.org>
Received: from eggs.gnu.org ([2001:470:142:3::10]:49364)
 by lists.gnu.org with esmtp (Exim 4.90_1)
 (envelope-from <zimon.toutoune@gmail.com>) id 1iv2RU-0002sx-8a
 for guix-devel@gnu.org; Fri, 24 Jan 2020 12:08:25 -0500
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
 (envelope-from <zimon.toutoune@gmail.com>) id 1iv2RT-0003Z7-CF
 for guix-devel@gnu.org; Fri, 24 Jan 2020 12:08:24 -0500
In-Reply-To: <871rrqqgqk.fsf@gnu.org>
List-Id: "Development of GNU Guix and the GNU System distribution."
 <guix-devel.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/guix-devel>,
 <mailto:guix-devel-request@gnu.org?subject=unsubscribe>
List-Archive: <https://lists.gnu.org/archive/html/guix-devel>
List-Post: <mailto:guix-devel@gnu.org>
List-Help: <mailto:guix-devel-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/guix-devel>,
 <mailto:guix-devel-request@gnu.org?subject=subscribe>
Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane-mx.org@gnu.org
Sender: "Guix-devel"
 <guix-devel-bounces+gcggd-guix-devel=m.gmane-mx.org@gnu.org>
To: =?UTF-8?Q?Ludovic_Court=C3=A8s?= <ludo@gnu.org>
Cc: Guix Devel <guix-devel@gnu.org>

Hi Ludo,

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

> I think we really need someone to pay attention to the schedule.  It=E2=
=80=99s
> 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=E2=80=99ve im=
proved
> the process and its documentation in the past, but I=E2=80=99m sure we ca=
n 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