From mboxrd@z Thu Jan  1 00:00:00 1970
From: =?UTF-8?Q?G=C3=A1bor_Boskovits?= <boskovits@gmail.com>
Subject: Re: New release soon?
Date: Sat, 17 Nov 2018 01:58:24 +0100
Message-ID: <CAE4v=pi_fDKo0uMDO9pos-oXW2b7XacWrWWf3M5Zau=ctFJ5nA@mail.gmail.com>
References: <588d8f0c-703e-7897-b9b8-39d29c453854@riseup.net>
	<8736s3vq6l.fsf@elephly.net> <875zwz5yq4.fsf@fastmail.com>
	<87o9aovqor.fsf@gnu.org> <87ftw0u3kw.fsf@elephly.net>
	<87wopcsoro.fsf@gnu.org> <20181116230358.1ef639a7@alma-ubu>
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.org@gnu.org>
Received: from eggs.gnu.org ([2001:4830:134:3::10]:45616)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <boskovits@gmail.com>) id 1gNowl-00018C-E0
	for guix-devel@gnu.org; Fri, 16 Nov 2018 19:58:52 -0500
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <boskovits@gmail.com>) id 1gNowk-00055d-Gr
	for guix-devel@gnu.org; Fri, 16 Nov 2018 19:58:51 -0500
In-Reply-To: <20181116230358.1ef639a7@alma-ubu>
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: <http://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.org@gnu.org
Sender: "Guix-devel" <guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org>
To: =?UTF-8?B?QmrDtnJuIEjDtmZsaW5n?= <bjoern.hoefling@bjoernhoefling.de>
Cc: Guix-devel <guix-devel@gnu.org>

Bj=C3=B6rn H=C3=B6fling <bjoern.hoefling@bjoernhoefling.de> ezt =C3=ADrta (=
id=C5=91pont:
2018. nov. 16., P, 23:06):
>
> On Fri, 16 Nov 2018 22:20:27 +0100
> ludo@gnu.org (Ludovic Court=C3=A8s) wrote:
>
> > Heya,
> >
> > Ricardo Wurmus <rekado@elephly.net> skribis:
> >
> > >> Initially I thought we may want to wait for core-updates to be
> > >> merged, but it looks like we have troubles focusing on that ;-),
> > >> so I don=E2=80=99t know.  Thoughts?
> > >
> > > I would prefer to have core-updates in the next release.  This has
> > > been delayed for much too long.  This would also avoid the bad look
> > > for a new release to have somewhat outdated core packages.
> > >
> > > If we can=E2=80=99t get core-updates ready within the next few weeks =
I won=E2=80=99t
> > > object to a release without it, but I think we should really try.
> >
> > Yes, that makes sense to me.
> >
> > So everyone: let=E2=80=99s join forces and get =E2=80=98core-updates=E2=
=80=99 finally merged!
>
> What is to do for core-updates to succeed? Is it "just" that
> hydra/berlin need to build it, or is there anything a human being can
> do (Or is the former necessary to define the latter?)?
>
> Is there a list of open/unresolved tasks?
>

Same questions here.

> Bj=C3=B6rn

g_bor