From mboxrd@z Thu Jan 1 00:00:00 1970 From: ng0 Subject: Re: =?utf-8?B?4oCYY29yZS11cGRhdGVz?= =?utf-8?B?4oCZ?= schedule Date: Fri, 7 Apr 2017 15:34:38 +0000 Message-ID: <20170407153438.slh6ur5exh6svbci@abyayala> 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]:51546) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1cwVuT-00014t-Fa for guix-devel@gnu.org; Fri, 07 Apr 2017 11:34:50 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1cwVuO-00041M-JK for guix-devel@gnu.org; Fri, 07 Apr 2017 11:34:49 -0400 Content-Disposition: inline In-Reply-To: <20170406150845.GA5287@jasmine> 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 Leo Famulari transcribed 1.1K bytes: > 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 sug= gest to write down > > a schedule and then try hard to stick to it. ;-) >=20 > 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. >=20 > 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] >=20 > You will find build failures before they show up on Hydra, and find bug= s > and regressions before we merge core-updates into master. Our build far= m > is relatively slow and unreliable, so it's inefficient to wait for it t= o > find build failures; it won't find applications bugs at all in many > cases. >=20 > > Last but not least: who wants to be the timekeeper? The position mos= tly > > consists in firmly reminding people of the schedule. :-) >=20 > I tried to do it this time around, but we kept finding bugs and > experiencing build failures that we couldn't ignore. >=20 > [0] I was able to rely on core-updates after ~3 weeks (excluding > libreoffice). >=20 Recently I've started studying other communities and how they function, among them Rust. I wonder how much of what Guix does can be further automated. So that it maybe doesn't take 6 weeks or more for certain features to be merged (building the binary substitutes is another issue of time and resources).