From: Marius Bakke <mbakke@fastmail.com>
To: Ricardo Wurmus <rekado@elephly.net>, swedebugia <swedebugia@riseup.net>
Cc: guix-devel@gnu.org
Subject: Re: New release soon?
Date: Wed, 14 Nov 2018 18:57:07 +0100 [thread overview]
Message-ID: <875zwz5yq4.fsf@fastmail.com> (raw)
In-Reply-To: <8736s3vq6l.fsf@elephly.net>
[-- Attachment #1: Type: text/plain, Size: 759 bytes --]
Ricardo Wurmus <rekado@elephly.net> writes:
> swedebugia <swedebugia@riseup.net> writes:
>
>> Considering the change to guile-gcrypt and the bugs we have found and
>> fixed since 0.15 I think we should release 0.16.0 soon.
>>
>> Or perhaps a maintenance 0.15.1 if the features added do not hold up
>> to a minor release.
>>
>> What do you think?
>
> The next release will hopefully be 1.0.0. We wanted to get this
> released sometime before FOSDEM 2019.
I think it could be useful to do a 0.16 release in the interim, since
it's difficult to build 0.15 from source currently (because of the
broken Python test in 'master' which OOMs (on) many kernels).
The many "guix pull" and UI improvements would also be nice to have "out
of the box" on new installs.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]
next prev parent reply other threads:[~2018-11-14 17:57 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-14 8:28 New release soon? swedebugia
2018-11-14 11:44 ` Ricardo Wurmus
2018-11-14 17:57 ` Marius Bakke [this message]
2018-11-16 18:10 ` Ludovic Courtès
2018-11-16 21:15 ` Ricardo Wurmus
2018-11-16 21:20 ` Ludovic Courtès
2018-11-16 22:03 ` Björn Höfling
2018-11-17 0:58 ` Gábor Boskovits
2018-11-17 14:14 ` Getting ‘core-updates’ merged Ludovic Courtès
2018-11-22 9:41 ` Ludovic Courtès
2018-11-22 19:54 ` Björn Höfling
2018-11-23 13:52 ` Ludovic Courtès
2018-11-23 21:44 ` Julien Lepiller
2018-11-24 9:19 ` Danny Milosavljevic
2018-11-25 15:54 ` Ludovic Courtès
2018-11-26 17:59 ` Danny Milosavljevic
2018-11-26 18:18 ` Danny Milosavljevic
2018-11-28 10:46 ` Ludovic Courtès
2018-11-26 17:54 ` Björn Höfling
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=875zwz5yq4.fsf@fastmail.com \
--to=mbakke@fastmail.com \
--cc=guix-devel@gnu.org \
--cc=rekado@elephly.net \
--cc=swedebugia@riseup.net \
/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).