unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: ng0 <contact.ng0@cryptolab.net>
To: Leo Famulari <leo@famulari.name>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: ‘core-updates’ schedule
Date: Fri, 7 Apr 2017 15:34:38 +0000	[thread overview]
Message-ID: <20170407153438.slh6ur5exh6svbci@abyayala> (raw)
In-Reply-To: <20170406150845.GA5287@jasmine>

Leo Famulari transcribed 1.1K bytes:
> On Thu, Apr 06, 2017 at 10:34:29AM +0200, Ludovic Courtès wrote:
> > This ‘core-updates’ cycle was terribly long, so I suggest to write down
> > a schedule and then try hard to stick to it.  ;-)
> 
> At the beginning of the cycle, I was confident that we could build and
> merge it in 2 or 3 weeks. But, it took about 6 weeks before we could
> merge.
> 
> Something we can all do to speed up the process is try `guix package -u`
> and `guix system build`, starting at the beginning of the freeze. [0]
> 
> You will find build failures before they show up on Hydra, and find bugs
> and regressions before we merge core-updates into master. Our build farm
> is relatively slow and unreliable, so it's inefficient to wait for it to
> find build failures; it won't find applications bugs at all in many
> cases.
> 
> > Last but not least: who wants to be the timekeeper?  The position mostly
> > consists in firmly reminding people of the schedule.  :-)
> 
> I tried to do it this time around, but we kept finding bugs and
> experiencing build failures that we couldn't ignore.
> 
> [0] I was able to rely on core-updates after ~3 weeks (excluding
> libreoffice).
> 

Recently I've started studying other communities and how they function,
among them Rust. I wonder how much of what Guix does can be further
automated.
So that it maybe doesn't take 6 weeks or more for certain features to be
merged (building the binary substitutes is another issue of time and
resources).

      parent reply	other threads:[~2017-04-07 15:34 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-06  8:34 ‘core-updates’ schedule Ludovic Courtès
2017-04-06 15:08 ` Leo Famulari
2017-04-07 15:22   ` Ludovic Courtès
2017-04-08 17:11     ` Leo Famulari
2017-04-07 15:34   ` ng0 [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20170407153438.slh6ur5exh6svbci@abyayala \
    --to=contact.ng0@cryptolab.net \
    --cc=guix-devel@gnu.org \
    --cc=leo@famulari.name \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).