From: "Ludovic Courtès" <ludo@gnu.org>
To: Mathieu Othacehe <othacehe@gnu.org>
Cc: guix-devel@gnu.org, Marius Bakke <mbakke@fastmail.com>
Subject: Re: Release Guix 1.1.1?
Date: Tue, 28 Jul 2020 00:05:19 +0200 [thread overview]
Message-ID: <87365cvckg.fsf@gnu.org> (raw)
In-Reply-To: <87o8qdxbzw.fsf@gnu.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 <ludo@gnu.org> skribis:
> Mathieu Othacehe <othacehe@gnu.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[1].
>
> Coming soon! (See also <https://issues.guix.gnu.org/41507>).
>
>> * A Cuirass update allowing to download disk-images built on top of
>> master[2].
>
> 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 other threads:[~2020-07-27 22:05 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-21 21:06 Release Guix 1.1.1? 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 \
--in-reply-to=87365cvckg.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guix-devel@gnu.org \
--cc=mbakke@fastmail.com \
--cc=othacehe@gnu.org \
/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).