Hi Simon
Simon Josefsson via "Development of GNU Guix and the GNU System distribution." <[email protected]> writes: > Noé Lopez <[email protected]> writes: > >> The first release candidate is going smoothly, a few bugs were found and >> we are working to fix them. Therefore, we are aiming for a final release >> target of January 19th! > > Yay! > > 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. Rutherther > > The obvious choice is A) but I don't like that this leads to an old > 'guix' tool inside the container. Chosing B) assumes that you will > create and push such a commit relatively shortly after tagging v1.5.0, > otherwise the distance between the v1.5.0 tag and the update of the guix > package will be too far and may include other irrelevant commits. > > The best from my perspective would be if the commit after the v1.5.0 tag > was a commit to update the guix package definition to the v1.5.0 commit. > Then I would pick the latter commit, so that the guix tool is v1.5.0. > > I plan to create tagged v1.5.0 container images for pure Guix, Guix on > Debian and Ubuntu/Trisquel with Guix. > > /Simon
