From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ricardo Wurmus Subject: Re: core-updates schedule Date: Mon, 20 Aug 2018 11:59:25 +0200 Message-ID: <878t51tl36.fsf@elephly.net> References: <87a7q6rkub.fsf@elephly.net> <87600o7tvp.fsf@elephly.net> <87efetif51.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:53632) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1frh2Y-0005dd-2s for guix-devel@gnu.org; Mon, 20 Aug 2018 06:04:07 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1frgyP-0004mP-Fm for guix-devel@gnu.org; Mon, 20 Aug 2018 05:59:46 -0400 In-reply-to: <87efetif51.fsf@gnu.org> List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org Sender: "Guix-devel" To: Ludovic =?utf-8?Q?Court=C3=A8s?= Cc: guix-devel@gnu.org Ludovic Court=C3=A8s writes: > Hi there! > > Ricardo Wurmus skribis: > >> Ricardo Wurmus writes: > > [...] > >>> This is a reminder about the =E2=80=9Ccore-updates=E2=80=9D branch. Ou= r plan was to >>> freeze the branch on <2018-08-06 Mon> and aim to merge the branch into >>> =E2=80=9Cmaster=E2=80=9D on <2018-08-20 Mon>, dependent on how long it = takes to fix all >>> problems and build most packages. >>> >>> Freezing the branch means that only commits to fix build failures may be >>> pushed. >>> >>> We will need volunteers to watch build failures on the Hydra web >>> interface. >> >> I=E2=80=99m still working on the GNOME updates. I branched them off >> core-updates some weeks ago and today I finally succeeded in building >> the =E2=80=9Cgnome=E2=80=9D package. Many of the changes, I assume, wil= l cause a large >> number of packages to be rebuilt, so I=E2=80=99d like to merge the chang= es into >> core-updates. > > I=E2=80=99m late to the party, but what=E2=80=99s the status? It seems w= e a bit behind > schedule, but it looks like a good time to resume work on this. The GNOME updates are ready (in a separate branch), but I haven=E2=80=99t b= een able to actually test them as I could not rebuild all of core-updates on my laptop to install a GNOME system. We left out most of the changes that were needed for GNOME, though some of them were also made on staging and some have been cherry picked into core-updates. Some of the delays are due to the work on staging, which had to be merged into core-updates first. (This has already been done.) > Today I=E2=80=99ll try switching to glibc 2.28, and if it works well, I= =E2=80=99d like > to make it the last big change in =E2=80=98core-updates=E2=80=99. Marius was working glibc 2.28 and that was the last big change I wanted to allow into core-updates. I don=E2=80=99t know how close Marius was in getting this done. -- Ricardo