From mboxrd@z Thu Jan 1 00:00:00 1970 From: Pjotr Prins Subject: Re: Ensuring we don't break user systems Date: Tue, 31 Jul 2018 14:40:23 +0200 Message-ID: <20180731124023.gyurqjxqgysjzmmh@thebird.nl> References: <28F9E4E7-AA66-43E7-8A68-AC3E46B60959@lepiller.eu> <87sh41boe1.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:53322) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fkTwy-00015P-Sa for guix-devel@gnu.org; Tue, 31 Jul 2018 08:40:29 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1fkTwv-0008PZ-OB for guix-devel@gnu.org; Tue, 31 Jul 2018 08:40:28 -0400 Received: from mail.thebird.nl ([94.142.245.5]:52202) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1fkTwv-0008NP-Gz for guix-devel@gnu.org; Tue, 31 Jul 2018 08:40:25 -0400 Content-Disposition: inline In-Reply-To: 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: Hartmut Goebel Cc: guix-devel@gnu.org On Mon, Jul 30, 2018 at 12:58:08PM +0200, Hartmut Goebel wrote: > Julien Lepiller skribis: > >> We wouldcreate a new branch, stable, that would be used by guix pull. We would continue to push to master or other branches. > > +1 Alternatively guix pull should only fetch the last tagged release. This has the advantage some people can test it before going into the wider world. Essentially a mini release cycle. And it does not have to be every day: 1. Decide on a time point (git hash) for the next guix pull (branch it) 2. Ask some people to test it (in addition to automated testing) 3. When OK tag release 4. Guix pull starts using that A rolling guix pull is a rather bad idea for stability ;). Unlike the main releases I think this can be done weekly or bi-monthly. Pj.