From mboxrd@z Thu Jan 1 00:00:00 1970 From: Julien Lepiller Subject: Ensuring we don't break user systems Date: Sun, 29 Jul 2018 11:40:17 +0200 Message-ID: <28F9E4E7-AA66-43E7-8A68-AC3E46B60959@lepiller.eu> 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]:33300) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fjiBc-0001Gx-6u for guix-devel@gnu.org; Sun, 29 Jul 2018 05:40:25 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1fjiBY-0003rf-QA for guix-devel@gnu.org; Sun, 29 Jul 2018 05:40:24 -0400 Received: from lepiller.eu ([2a00:5884:8208::1]:48960) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1fjiBY-0003qf-DK for guix-devel@gnu.org; Sun, 29 Jul 2018 05:40:20 -0400 Received: from [10.208.49.33] (tor-exit-01.jelleschneiders.com [145.239.90.27]) by lepiller.eu (OpenSMTPD) with ESMTPSA id 5daac79a (TLSv1.2:ECDHE-RSA-CHACHA20-POLY1305:256:NO) for ; Sun, 29 Jul 2018 09:41:46 +0000 (UTC) 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: guix-devel@gnu.org Hi guix! I recently had an idea about how we should organize ourworkflow for post 1= =2E0=2E The goal is to ensure that users can always update their system=2E Currently, we push updatesto master and they may not build on other archit= ectures or break dependant packages=2E This is bad because a security updat= e might get blocked because an unrelated package now fails to build=2E I'd like to propose the following policy: We wouldcreate a new branch, stable, that would be used by guix pull=2E We= would continue to push to master or other branches=2E Once hydra finds it can build at least as many packages in master than sta= ble, it would make master the new stable, hopefully once a day or so=2E Security updates would be provided to users by a se=C3=A9arate channel, to= ensure important updates are delivered immediately to users=2E Another possibility is to use a patch management system like gerrit with a= similar policy=2E WDYT?