Nguyễn Gia Phong <[email protected]> writes:

> Conceptually, I find the notion of filing a MR to reserve a spot
> in the queue before stablizing the changes to be hinky,
> but it does not work the other way around as relevant packages
> will change when a branch gets to the front of the queue.

Unfortunately the move to Codeberg has left things in an in between
state, and it's only recently that I've found some energy to try and get
back to a better place regarding testing patches and branches. There's
still a long way to go though.

> Meanwhile, dependent channels are right there for the grab.
> I've proposed it before, and perhaps the process was too complex:
> https://lists.gnu.org/archive/html/guix-devel/2026-06/msg00184.html

...

> I will try to send out a GCD draft after the upcoming 1.6,
> and any early feedback is also appreciated.

I'm still very much of the opinion that packages should be kept together
in Guix. Even if dividing up the problem helps initially (and it might,
since at the moment one of the problems is that the package graph
doesn't reflect how people are grouping changes to packages), I still
think it's easy to tackle the big long term maintenance challenges if
all the packages (core + crust as you put it) are together in one
channel.

There's a whole lot of work needed just to get back to where things were
before regarding testing patches (now Pull Requests) and branches (which
should be Pull Requests now), but I'm hopeful that there's plenty of
room for improvement beyond this point.

I'll use the new terminology to describe this, but one idea I was
looking at previously was not having stateful branches, but instead
generating branches from groups of Pull Requests. I think this would
make it much easier to manage what changes are going together on a
branch, leaving combining and testing these changes to QA.

I think something like this combined with doing more testing earlier, so
doing at least some building and testing of all branches, not just the
ones about to be merged would greatly improve the situation.

Attachment: signature.asc
Description: PGP signature

Reply via email to