unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Andreas Enge <andreas@enge.fr>
To: Andy Tai <atai@atai.org>
Cc: guix-devel@gnu.org
Subject: Re: role of core-updates
Date: Mon, 4 Dec 2023 17:02:02 +0100	[thread overview]
Message-ID: <ZW33-ujncqZNIh9b@jurong> (raw)
In-Reply-To: <CAJsg1E_ByxC3ROMLhbts+o6Prhg1xwRF3hcbKNBsZ6K3uCVqtQ@mail.gmail.com>

Am Sun, Nov 26, 2023 at 10:53:46PM -0800 schrieb Andy Tai:
> Hi, hope Guix maintainers can clarify the role of the now core-updates
> branch; the current documentation does not specify the core-updates
> branch as a thing but there are clearly interests and uses of this
> branch for package updates not belonging to a feature branch like
> gnome and it is useful for, say, updating to the GNU make package
> which would have caused world rebuild.  Thanks

When we started implementing the teams idea, I thought we would get rid
of the core-updates branch altogether. I still think it should not exist
as such, but be folded into the teams workflow. I am still mildly worried
that we have this branch into which many unrelated things get dumped,
without a clear responsibility who pushes it forward and on which timeline.

There is a "core" team, but this is probably not the same thing: I think
there are packages outside of the core team scope that cause now inside
the core-updates branch.

Andreas



  parent reply	other threads:[~2023-12-04 16:02 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-27  6:53 role of core-updates Andy Tai
2023-11-27 17:59 ` Leo Famulari
2023-11-27 20:08   ` Felix Lechner via Development of GNU Guix and the GNU System distribution.
2023-12-04 16:02 ` Andreas Enge [this message]
2023-12-09 10:16   ` Ludovic Courtès
2023-12-09 10:33     ` Andreas Enge
2024-01-24 14:31       ` Andreas Enge
2024-01-24 19:22         ` [bug#68606] " Maxim Cournoyer
2024-01-25 10:18           ` Andreas Enge

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=ZW33-ujncqZNIh9b@jurong \
    --to=andreas@enge.fr \
    --cc=atai@atai.org \
    --cc=guix-devel@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 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).