From: "Ludovic Courtès" <email@example.com> To: Mathieu Othacehe <firstname.lastname@example.org> Cc: email@example.com, Marius Bakke <firstname.lastname@example.org> Subject: Re: Release Guix 1.1.1? Date: Tue, 28 Jul 2020 00:05:19 +0200 Message-ID: <email@example.com> (raw) In-Reply-To: <firstname.lastname@example.org> ("Ludovic \=\?utf-8\?Q\?Court\=C3\=A8s\=22'\?\= \=\?utf-8\?Q\?s\?\= message of "Sun, 24 May 2020 23:24:19 +0200") Hello! Ludovic Courtès <email@example.com> skribis: > Mathieu Othacehe <firstname.lastname@example.org> skribis: > >>> What do y'all think about targeting a 1.1.1 release a few weeks from >>> now? >>> >>> Any milestones we should try to complete before an eventual release? >> >> This seems like a very good idea. It would be good if this release could >> include: >> >> * A new shepherd release fixing this bug. > > Coming soon! (See also <https://issues.guix.gnu.org/41507>). > >> * A Cuirass update allowing to download disk-images built on top of >> master. > > Yay! > > Initially I was hoping to get support for authenticated channels in that > release¹, but I don’t know if it can be ready and well-tested on time. I think we’ve pretty much reached all these milestones. So we need to do some testing again of the installer, but at least we no longer have the excuse of adding one last feature. So I guess we could seriously work on it. Thoughts? In fact, I’ll be away from keyboard for some time, so I’m not necessarily part of “we” in the coming weeks :-) but happy to help afterwards. We could aim for beginning of September, or earlier if people are available. Ludo’.
next prev parent reply index Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-05-21 21:06 Marius Bakke 2020-05-22 0:38 ` Leo Famulari 2020-05-22 17:45 ` Mathieu Othacehe 2020-05-24 21:24 ` Ludovic Courtès 2020-07-27 22:05 ` Ludovic Courtès [this message] 2020-07-27 22:48 ` zimoun 2020-07-28 7:51 ` Mathieu Othacehe 2020-06-18 21:31 ` zimoun 2020-06-19 16:19 ` Leo Famulari
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 \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ /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
unofficial mirror of firstname.lastname@example.org Archives are clonable: git clone --mirror https://yhetil.org/guix-devel/0 guix-devel/git/0.git # If you have public-inbox 1.1+ installed, you may # initialize and index your mirror using the following commands: public-inbox-init -V2 guix-devel guix-devel/ https://yhetil.org/guix-devel \ email@example.com public-inbox-index guix-devel Example config snippet for mirrors Newsgroups are available over NNTP: nntp://news.yhetil.org/yhetil.gnu.guix.devel nntp://news.gmane.io/gmane.comp.gnu.guix.devel AGPL code for this site: git clone https://public-inbox.org/public-inbox.git