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?=E2=80=98core-updates=E2=80=99?= schedule Date: Fri, 07 Apr 2017 17:22:13 +0200 Message-ID: <871st42qfu.fsf@gnu.org> References: <87mvbuylwq.fsf@gnu.org> <20170406150845.GA5287@jasmine> 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]:48227) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1cwViP-00066k-46 for guix-devel@gnu.org; Fri, 07 Apr 2017 11:22:21 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1cwViL-0006hJ-WA for guix-devel@gnu.org; Fri, 07 Apr 2017 11:22:21 -0400 In-Reply-To: <20170406150845.GA5287@jasmine> (Leo Famulari's message of "Thu, 6 Apr 2017 11:08:45 -0400") 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: Leo Famulari Cc: guix-devel Heya! Leo Famulari skribis: > On Thu, Apr 06, 2017 at 10:34:29AM +0200, Ludovic Court=C3=A8s wrote: >> This =E2=80=98core-updates=E2=80=99 cycle was terribly long, so I sugges= t to write down >> a schedule and then try hard to stick to it. ;-) > > At the beginning of the cycle, I was confident that we could build and > merge it in 2 or 3 weeks. But, it took about 6 weeks before we could > merge. > > Something we can all do to speed up the process is try `guix package -u` > and `guix system build`, starting at the beginning of the freeze. [0] > > You will find build failures before they show up on Hydra, and find bugs > and regressions before we merge core-updates into master. Our build farm > is relatively slow and unreliable, so it's inefficient to wait for it to > find build failures; it won't find applications bugs at all in many > cases. True (I did that but could have done it earlier.) >> Last but not least: who wants to be the timekeeper? The position mostly >> consists in firmly reminding people of the schedule. :-) > > I tried to do it this time around, but we kept finding bugs and > experiencing build failures that we couldn't ignore. > > [0] I was able to rely on core-updates after ~3 weeks (excluding > libreoffice). Yeah, that=E2=80=99s right. I=E2=80=99m not saying it would have been easy= to avoid the delay; it=E2=80=99s obviously very tricky to get right, and gets more diffi= cult as the package collection grows. Clearly you and Marius did a great job at fixing bugs and making sure we=E2=80=99d make progress! My thought was that fixing specific dates might help get everyone psychologically prepared and ready to focus on stabilizing the branch when the time comes. Ludo=E2=80=99.