From mboxrd@z Thu Jan  1 00:00:00 1970
From: ludo@gnu.org (Ludovic =?utf-8?Q?Court=C3=A8s?=)
Subject: Re: =?utf-8?Q?Let=E2=80=99s?= freeze and build
	=?utf-8?Q?=E2=80=98core-updates=E2=80=99!?=
Date: Tue, 14 Feb 2017 17:22:46 +0100
Message-ID: <87tw7wspwp.fsf@gnu.org>
References: <87mvdpw3b3.fsf@gnu.org>
	<87zihoizr4.fsf@kirby.i-did-not-set--mail-host-address--so-tickle-me>
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]:42681)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <ludo@gnu.org>) id 1cdfsR-0002wT-Rd
	for guix-devel@gnu.org; Tue, 14 Feb 2017 11:22:53 -0500
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <ludo@gnu.org>) id 1cdfsO-00053b-Gy
	for guix-devel@gnu.org; Tue, 14 Feb 2017 11:22:51 -0500
In-Reply-To: <87zihoizr4.fsf@kirby.i-did-not-set--mail-host-address--so-tickle-me>
	(Marius Bakke's message of "Tue, 14 Feb 2017 16:00:15 +0100")
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: Marius Bakke <mbakke@fastmail.com>
Cc: guix-devel@gnu.org

Hey Marius,

Marius Bakke <mbakke@fastmail.com> skribis:

> Ludovic Court=C3=A8s <ludo@gnu.org> writes:
>
>> Hello Guix!
>>
>> Since I=E2=80=99m about to leave keyboard for a couple of weeks, here=E2=
=80=99s a to-do
>> list for those of you who=E2=80=99ll be around.  :-)
>>
>> The last things I wanted to push for =E2=80=98core-updates=E2=80=99 were=
 a reproducible
>> Guile (done in b5efd14a9add1bcb4a44fa5b9c1b47706f3df9da), and a subset
>> or all of the aarch64 patches, depending on their status (should not be
>> a blocker IMO).
>>
>> So, here=E2=80=99s a plan:
>>
>>   =E2=80=A2 Once Efraim has pushed some of the aarch64 patches, do anoth=
er
>>     evaluation of the =E2=80=9Ccore=E2=80=9D package set for that branch=
, and check for
>>     anything wrong.  From there on, forbid full-rebuild changes.
>>
>>   =E2=80=A2 Once the =E2=80=9Ccore=E2=80=9D subset builds correctly on a=
ll the supported
>>     platforms (those that Hydra supports), merge =E2=80=98master=E2=80=
=99.  Maybe update
>>     a couple of things like GnuTLS while we=E2=80=99re at it.  From ther=
e on
>>     forbid non-trivial changes.
>>
>>   =E2=80=A2 Build all the packages.  (To do that, someone with access to=
 Hydra
>>     must change the =E2=80=9Csubset=E2=80=9D argument to =E2=80=9Call=E2=
=80=9D in the config of the
>>     =E2=80=98core-updates=E2=80=99 jobset.)
>>
>>   =E2=80=A2 Fix things.
>>
>>   =E2=80=A2 Once most regressions have been addressed and most binaries =
are
>>     available, merge =E2=80=98core-updates=E2=80=99 into =E2=80=98master=
=E2=80=99.
>>
>> How does that sound?
>
> This sounds great. I have a question:
>
> The 'staging' branch contains a number of minor updates and it's been
> more than a month since the last merge. Should we do a staging
> evaluation first (i.e. next few days), or just merge it to core-updates?

Good point.  I=E2=80=99d just merge it into =E2=80=98core-updates=E2=80=99 =
at this point.

Ludo=E2=80=99.