Hi Phong,

On Thu, Nov 12 2026, Nguyễn Gia Phong via "Development of GNU Guix and the GNU 
System distribution." wrote:

> Much of these have to do with our rolling release model,
> so let's put a few restriction on it.  First, crust must have
> two branches, stable and devel.  Most patches landing on master
> at the time of writing would get applied on devel.  Stable must pin
> a core release tag.

How about commits are automatically pulled into a "prebuilt" branch when
substitute coverage is acceptable?

Since Guix should ship only packages that build, it might even be
appropriate to demand full coverage.  That, in turn, would mean the
monorepo should be split.  Only then will full substitute availability
become an attainable goal.

(My apologies if all packages currently have substitutes.)

To call such a branch "stable" would be misleading.  A package's ability
to build is an entry threshold that does not mean it is free of defects
or ready to ship.

Kind regards
Felix

Reply via email to