From: "Ludovic Courtès" <ludo@gnu.org>
To: Leo Famulari <leo@famulari.name>
Cc: guix-devel@gnu.org, Carl Dong <contact@carldong.me>
Subject: Re: Help wanted: Nightly builds for Guix
Date: Sat, 21 Mar 2020 16:55:43 +0100 [thread overview]
Message-ID: <87a7491z40.fsf@gnu.org> (raw)
In-Reply-To: <20200319185048.GA19460@jasmine.lan> (Leo Famulari's message of "Thu, 19 Mar 2020 14:50:48 -0400")
Hello!
Leo Famulari <leo@famulari.name> skribis:
> On Thu, Mar 19, 2020 at 05:29:37PM +0000, Carl Dong wrote:
>> I'm wondering where best to start with this. Perhaps it'd be informative to know
>> how regular releases are done and see what's missing there (and perhaps what
>> needs automation)?
>
> Check the release target in our Makefile. I remember some detailed
> descriptions of the entire process from Ludovic in the past, but I can't
> remember where to find those messages.
The release process is documented at:
https://git.savannah.gnu.org/cgit/guix/maintenance.git/tree/doc/release.org
As for nightly builds: CI currently builds things like:
https://ci.guix.gnu.org/search?query=guix-binary ;binary tarball
https://ci.guix.gnu.org/search?query=disk-image ;ISO9660 image
It’s inconvenient to grab, though, for someone who doesn’t already have
Guix. Perhaps we should address that somehow?
Thanks,
Ludo’.
next prev parent reply other threads:[~2020-03-21 15:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-19 17:29 Help wanted: Nightly builds for Guix Carl Dong
2020-03-19 17:38 ` Vincent Legoll
2020-03-19 18:50 ` Leo Famulari
2020-03-21 15:55 ` Ludovic Courtès [this message]
2020-03-20 14:13 ` Mathieu Othacehe
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87a7491z40.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=contact@carldong.me \
--cc=guix-devel@gnu.org \
--cc=leo@famulari.name \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).