From mboxrd@z Thu Jan 1 00:00:00 1970 From: Leo Famulari Subject: Re: =?utf-8?B?4oCYY29yZS11cGRhdGVz?= =?utf-8?B?4oCZ?= schedule Date: Thu, 6 Apr 2017 11:08:45 -0400 Message-ID: <20170406150845.GA5287@jasmine> References: <87mvbuylwq.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:35357) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1cw91u-000234-7V for guix-devel@gnu.org; Thu, 06 Apr 2017 11:08:59 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1cw91r-0005Au-1T for guix-devel@gnu.org; Thu, 06 Apr 2017 11:08:58 -0400 Content-Disposition: inline In-Reply-To: <87mvbuylwq.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 =?iso-8859-1?Q?Court=E8s?= Cc: guix-devel On Thu, Apr 06, 2017 at 10:34:29AM +0200, Ludovic Courtès wrote: > This ‘core-updates’ cycle was terribly long, so I suggest 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. > 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).