Ludovic Courtès <l...@gnu.org> writes: > Hello Guix! > > The release process as documented in doc/release.org was terrible > because it involved a lengthy sequence of error-prone manual steps. > > Commit 334dce145122683e576ca4cb6c68c360d4aada7e adds a ‘release’ > makefile target. “make release” produces the source tarball, the binary > tarballs, and the GuixSD installation images, which can then be directly > uploaded. Offloading must be set up to build binary tarballs for all > the architectures.
Thank you so much! This is great! > Anyway, I would welcome feedback especially from you Ricardo since you > felt the pain before. :-) An easy way to test is by building for a > single architecture: > > make release -j4 SUPPORTED_SYSTEMS=x86_64-linux \ > GUIXSD_SUPPORTED_SYSTEMS=x86_64-linux > > Note that this will make a couple of commits on your behalf, to update > the ‘guix’ package, so be careful. I’m going to give this a try soon. > I’m also interested in thoughts on how to automate other bits from the > release process, though they are probably less critical: > > https://git.savannah.gnu.org/cgit/guix/maintenance.git/tree/doc/release.org I’ll take a look at this again after testing the release target. Thanks again for all the hard work! -- Ricardo GPG: BCA6 89B6 3655 3801 C3C6 2150 197A 5888 235F ACAC https://elephly.net
