From mboxrd@z Thu Jan 1 00:00:00 1970 From: Dan Partelly Subject: Re: Ensuring we don't break user systems Date: Sun, 29 Jul 2018 19:51:29 +0300 Message-ID: <1C89A082-845D-49B4-A70F-D4FFCD411124@rdsor.ro> References: <28F9E4E7-AA66-43E7-8A68-AC3E46B60959@lepiller.eu> Mime-Version: 1.0 (Mac OS X Mail 11.3 \(3445.6.18\)) Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:57339) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fjouy-0006eS-SA for guix-devel@gnu.org; Sun, 29 Jul 2018 12:51:41 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1fjouu-0007YY-0l for guix-devel@gnu.org; Sun, 29 Jul 2018 12:51:40 -0400 Received: from imap.rdsor.ro ([193.231.238.8]:60166 helo=mail.rdsor.ro) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fjout-0007YF-O3 for guix-devel@gnu.org; Sun, 29 Jul 2018 12:51:35 -0400 In-Reply-To: <28F9E4E7-AA66-43E7-8A68-AC3E46B60959@lepiller.eu> 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: Julien Lepiller Cc: guix-devel@gnu.org I pointed this out 4-5 weeks ago when trying GuixSD, on this very list. = Thanks for reaffirming the idea In all honesty the current model is = very badly broken, and you should not wait for 1.0. I had no other Linux = distro break up faster than GuixSD. A stable branch is not enough by = itself, (but is the mort important part) you need to ensure that all = substitutes are built correctly, and atomically update all substitutes = following a successful build of all packages.=20 You should not inflict current model on your users , not even for an = 0.1 > On Jul 29, 2018, at 12:40, Julien Lepiller wrote: >=20 > Hi guix! >=20 > I recently had an idea about how we should organize ourworkflow for = post 1.0. The goal is to ensure that users can always update their = system. >=20 > Currently, we push updatesto master and they may not build on other = architectures or break dependant packages. This is bad because a = security update might get blocked because an unrelated package now fails = to build. >=20 > I'd like to propose the following policy: >=20 > We wouldcreate a new branch, stable, that would be used by guix pull. = We would continue to push to master or other branches. >=20 > Once hydra finds it can build at least as many packages in master than = stable, it would make master the new stable, hopefully once a day or so. >=20 > Security updates would be provided to users by a se=C3=A9arate = channel, to ensure important updates are delivered immediately to users. >=20 > Another possibility is to use a patch management system like gerrit = with a similar policy. >=20 > WDYT? >=20