Rutherther <[email protected]> writes: >> Is there a recommendation how to prepare container images for the >> release? >> >> A) Build them for the git commit tag v1.5.0. Then the 'guix' tool >> inside the generated container will be older than v1.5.0. >> >> B) Build them for the commit that updates the guix packaging definition >> to use the v1.5.0 commit in master. Will you make such a commit shortly >> after tagging v1.5.0? > > Yes, making such commit is part of the release process itself. We need > it to generate the installer images. Those should install 1.5.0 guix for > users. > > The result will remain (forever) in the version branch, version-1.5.0. > So I would advise users to use that branch if they want to bootstrap by > themselves and not use the published artifacts.
Perfect, thank you! I will pin at the commit on the version-1.5.0 branch that merges the v1.5.0 tag. /Simon
signature.asc
Description: PGP signature
