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 21:07:40 +0300 Message-ID: <23782D92-97F4-4B27-BC09-7AF89FA82CE0@rdsor.ro> References: <28F9E4E7-AA66-43E7-8A68-AC3E46B60959@lepiller.eu> <1C89A082-845D-49B4-A70F-D4FFCD411124@rdsor.ro> <20180729195142.2e0af31d@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]:41375) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fjq6g-0000FE-8i for guix-devel@gnu.org; Sun, 29 Jul 2018 14:07:51 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1fjq6b-0002uJ-AE for guix-devel@gnu.org; Sun, 29 Jul 2018 14:07:50 -0400 Received: from imap.rdsor.ro ([193.231.238.8]:40196 helo=mail.rdsor.ro) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fjq6b-0002tJ-2v for guix-devel@gnu.org; Sun, 29 Jul 2018 14:07:45 -0400 In-Reply-To: <20180729195142.2e0af31d@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 It also has the effect that guix is pulled from a reasonably tested = branch and it is proven that it compiles. Given how central the package = manager is to the GuixSD, this is something which IMO should have been = done from long ago. IT saves users time,=20 and show the developers care , if nothing else. But yeah, this proposal = is IMO sound both technically and socially. > system or profile will always succeed and use substitutes, but it > doesn't give any guarantee on adding a package to the system or a user > profile. >=20 >>=20 >>=20 >>=20 >>> 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 >=20 >=20