From: Dan Partelly <dan_partelly@rdsor.ro>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel@gnu.org
Subject: Re: Ensuring we don't break user systems
Date: Mon, 30 Jul 2018 09:33:42 +0300 [thread overview]
Message-ID: <09F2CFD4-C906-45BB-9757-613499DF9FD4@rdsor.ro> (raw)
In-Reply-To: <87sh41boe1.fsf@gnu.org>
However, you do not need any tool support to switch a “stable” branch as a first step , ensuring you inimize the OS user exposure to both serious Guix bugs and potential Guile bugs.
> On Jul 30, 2018, at 02:41, Ludovic Courtès <ludo@gnu.org> wrote:
>
> Hello!
>
> Julien Lepiller <julien@lepiller.eu> skribis:
>
>> I'd like to propose the following policy:
>>
>> We wouldcreate a new branch, stable, that would be used by guix pull. We would continue to push to master or other branches.
>>
>> 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.
>
> I’m all for it. We “just” need support for this in Cuirass and/or some
> other tool…
>
> Ludo’.
>
next prev parent reply other threads:[~2018-07-30 6:33 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-29 9:40 Ensuring we don't break user systems Julien Lepiller
2018-07-29 9:45 ` Pierre Neidhardt
2018-07-29 16:58 ` Dan Partelly
2018-07-29 16:51 ` Dan Partelly
2018-07-29 17:28 ` Christopher Baines
2018-07-29 17:59 ` Dan Partelly
2018-07-30 21:16 ` Nils Gillmann
2018-07-30 21:24 ` Amirouche Boubekki
2018-07-30 21:30 ` Nils Gillmann
2018-07-31 6:17 ` Dan Partelly
2018-07-31 7:45 ` Julien Lepiller
2018-07-29 17:51 ` Julien Lepiller
2018-07-29 18:07 ` Dan Partelly
2018-07-29 23:41 ` Ludovic Courtès
2018-07-30 6:33 ` Dan Partelly [this message]
2018-07-30 10:58 ` Hartmut Goebel
2018-07-31 12:40 ` Pjotr Prins
2018-07-31 13:15 ` Clément Lassieur
2018-07-31 13:18 ` Julien Lepiller
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=09F2CFD4-C906-45BB-9757-613499DF9FD4@rdsor.ro \
--to=dan_partelly@rdsor.ro \
--cc=guix-devel@gnu.org \
--cc=ludo@gnu.org \
/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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.