From mboxrd@z Thu Jan  1 00:00:00 1970
From: ludo@gnu.org (Ludovic =?utf-8?Q?Court=C3=A8s?=)
Subject: Re: [PATCH 1/7] gnu: gobject-introspection: Update to 1.44.0.
Date: Wed, 22 Apr 2015 23:00:33 +0200
Message-ID: <87618nzxn2.fsf@gnu.org>
References: <1429524721-21449-1-git-send-email-iyzsong@gmail.com>
	<87618p19aw.fsf@gnu.org> <20150421211500.GA6274@debian>
	<87pp6x6s6v.fsf@netris.org>
	<20150422120642.GB4297@debian.math.u-bordeaux1.fr>
	<87d22w6w9f.fsf@netris.org>
	<20150422155401.GA6017@debian.math.u-bordeaux1.fr>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Return-path: <guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org>
Received: from eggs.gnu.org ([2001:4830:134:3::10]:44131)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <ludo@gnu.org>) id 1Yl1lD-0003QU-34
	for guix-devel@gnu.org; Wed, 22 Apr 2015 17:00:43 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <ludo@gnu.org>) id 1Yl1l9-00058t-Ls
	for guix-devel@gnu.org; Wed, 22 Apr 2015 17:00:42 -0400
Received: from fencepost.gnu.org ([2001:4830:134:3::e]:41043)
	by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from <ludo@gnu.org>)
	id 1Yl1l9-00058p-Dz
	for guix-devel@gnu.org; Wed, 22 Apr 2015 17:00:39 -0400
In-Reply-To: <20150422155401.GA6017@debian.math.u-bordeaux1.fr> (Andreas
	Enge's message of "Wed, 22 Apr 2015 17:54:01 +0200")
List-Id: "Development of GNU Guix and the GNU System distribution."
	<guix-devel.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/guix-devel>,
	<mailto:guix-devel-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/guix-devel>
List-Post: <mailto:guix-devel@gnu.org>
List-Help: <mailto:guix-devel-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/guix-devel>,
	<mailto:guix-devel-request@gnu.org?subject=subscribe>
Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org
Sender: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org
To: Andreas Enge <andreas@enge.fr>
Cc: guix-devel@gnu.org

Andreas Enge <andreas@enge.fr> skribis:

> Now, I would still like some guidelines for what to commit to master and =
what
> to core-updates, that we could possibly write down in HACKING (and update=
 when
> the hydra situation changes). Does something like "If you modify PACKAGE =
from
> base.scm, or 'guix refresh -l PACKAGE' shows that >=3D N packages are aff=
ected,
> then commit to core-updates" make sense? If yes, what should be the value
> of N? If not, what would be a better idea?

I personally use =E2=80=98guix refresh -l=E2=80=99 as the metric to decide =
whether to
create a branch or not.  I think it=E2=80=99s a good one though the ideal o=
ne
would be makespan.  Another consideration is the current build farm
load.

The =E2=80=9CCommit Access=E2=80=9D section mentions =E2=80=9Cupgrades that=
 trigger a lot of
rebuilds=E2=80=9D, which is quite vague but appeals to =E2=80=9Ccommon sens=
e.=E2=80=9D  I=E2=80=99m not
sure this can usefully worded as strictly as you suggest.  WDYT?

Thanks,
Ludo=E2=80=99.