From: Pjotr Prins <pjotr.public12@thebird.nl>
To: Hartmut Goebel <h.goebel@crazy-compilers.com>
Cc: guix-devel@gnu.org
Subject: Re: Ensuring we don't break user systems
Date: Tue, 31 Jul 2018 14:40:23 +0200 [thread overview]
Message-ID: <20180731124023.gyurqjxqgysjzmmh@thebird.nl> (raw)
In-Reply-To: <da46bbfb-87ed-6924-74b0-f022350bdc10@crazy-compilers.com>
On Mon, Jul 30, 2018 at 12:58:08PM +0200, Hartmut Goebel wrote:
> Julien Lepiller <julien@lepiller.eu> 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.
next prev parent reply other threads:[~2018-07-31 12:40 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
2018-07-30 10:58 ` Hartmut Goebel
2018-07-31 12:40 ` Pjotr Prins [this message]
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=20180731124023.gyurqjxqgysjzmmh@thebird.nl \
--to=pjotr.public12@thebird.nl \
--cc=guix-devel@gnu.org \
--cc=h.goebel@crazy-compilers.com \
/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.