unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Efraim Flashner <efraim@flashner.co.il>
To: Leo Famulari <leo@famulari.name>
Cc: guix-devel <guix-devel@gnu.org>
Subject: branch naming conventions [was Re: Guix Day: Notes from the CI session]
Date: Wed, 10 Feb 2021 16:09:15 +0200	[thread overview]
Message-ID: <YCPpC7ufute0jIgB@3900XT> (raw)
In-Reply-To: <YCMCvOaqhfLb0L82@jasmine.lan>

[-- Attachment #1: Type: text/plain, Size: 1488 bytes --]

On Tue, Feb 09, 2021 at 04:46:36PM -0500, Leo Famulari wrote:
> On Mon, Feb 08, 2021 at 06:07:25PM +0100, Ludovic Courtès wrote:
> > ## Open issue: branching strategy
> > 
> >   - currently: building all of `master` + the "core" of `core-updates`
> >   - schedule
> >     - currently ad-hoc: volunteers get to choose when to freeze/merge
> >   - actions
> >     - pushes to `core-updates` should cancel all pending builds on that branch (see Guix Build Coordinator)
> >     - have a dashboard showing active branches, statuses (wild-west, frozen), and merge deadlines
> >       - could be implemented in Cuirass
> >       - specs could have extra properties (such as "merge deadline") that Cuirass would display
> >       - or it could use status info from the Data Service, as in https://data.guix-patches.cbaines.net/
> >     - naming convention: `core-updates-frozen` vs `core-updates`, etc.
> 
> So, does anyone want to change the naming conventions?
> 
> I like the idea of, in normal times, only pushing to "core-updates-next"
> and "staging-next", and then freezing and building "core-updates" and
> "staging".

My concern about that is that it basically swaps what we have now. Using
-frozen makes it a bit clearer that we're building it out.

-- 
Efraim Flashner   <efraim@flashner.co.il>   אפרים פלשנר
GPG key = A28B F40C 3E55 1372 662D  14F7 41AA E7DC CA3D 8351
Confidentiality cannot be guaranteed on emails sent or received unencrypted

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2021-02-10 14:10 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-08 17:07 Guix Day: Notes from the CI session Ludovic Courtès
2021-02-09 21:45 ` Leo Famulari
2021-02-10 17:11   ` Mathieu Othacehe
2021-02-10 17:27     ` Leo Famulari
2021-02-10 21:11     ` Ludovic Courtès
2021-02-13 23:12     ` Leo Famulari
2021-02-14  8:42       ` Mathieu Othacehe
2021-02-14 18:57         ` Leo Famulari
2021-02-10 21:47   ` Ludovic Courtès
2021-02-11 21:04   ` Andreas Enge
2021-02-11 21:16     ` Leo Famulari
2021-02-09 21:46 ` Leo Famulari
2021-02-10 14:09   ` Efraim Flashner [this message]
2021-02-10 16:49     ` branch naming conventions [was Re: Guix Day: Notes from the CI session] Leo Famulari
2021-02-10 21:49       ` Ludovic Courtès
2021-02-11 21:14         ` Leo Famulari
2021-02-12  9:57           ` Efraim Flashner

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=YCPpC7ufute0jIgB@3900XT \
    --to=efraim@flashner.co.il \
    --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).