Hello,

Steve George <st...@futurile.net> writes:

> -- >8 -- >8
>
> * %system_packages: packages required to boot and install a minimal Guix 
> System
>   or install Guix on a foreign distribution.  This only includes default
>   options **required** by the installer which **must** work for a release 
> since
>   they are part of the default installer path.  For example, this would 
> include
>   the guix daemon, kernels, boot loaders, file-systems and minimal utilities.
> * %desktop_packages: additional desktop environments and other options from
>   the installer. This includes packages that are part of the installer
>   (but not default) and other popular options as chosen by the Release Team.
>   Packages **should** work, but they may receive less QA attention from the
>   Release Team than %system_packages.
> * %base_packages: important packages that anyone may wish to install on Guix 
> and
>   consequently the project wants to maintain substitutes for. This may include
>   important toolchains, runtimes and utilities. The Release Team **may**
>   perform QA on these packages.
>
> Guix would still make all packages and services part of a release (the entire
> archive).  Guix teams would be asked to test the parts of the archive that 
> they
> look after. But, only Release Critical bugs in the `package sets` could block
> a release.
>
> The Release Team may identify other package sets as needed.
>
> -- >8 -- >8

These are supposed to be the names of variables used in
‘etc/manifests/release.scm’?  Maybe we can omit the variable names after
all?

What matters here is the description of each one, which LGTM: things
that must work, should work, and have substitutes available.

Thanks,
Ludo’.

Reply via email to