From: ludo@gnu.org (Ludovic Courtès)
To: Ricardo Wurmus <rekado@elephly.net>
Cc: guix-devel@gnu.org
Subject: Re: preparing the next release v0.15.0
Date: Fri, 15 Jun 2018 11:42:03 +0200 [thread overview]
Message-ID: <87bmccv11w.fsf@gnu.org> (raw)
In-Reply-To: <87efh9bws8.fsf@elephly.net> (Ricardo Wurmus's message of "Thu, 14 Jun 2018 10:24:39 +0200")
Hi!
Ricardo Wurmus <rekado@elephly.net> skribis:
>> Can we aim for a v1.0 release? At least for the package manager? I am
>> facing people that say Guix is not mature and therefore insecure and
>> therefore they can justifiably ignore my pleas for installation
>> without even looking.
>
> I would like to leave 1.0 for the future.
>
> Things that I’d like to see in 1.0 include a new manifest format that
> records more information about the version of Guix, retiring of
> GUIX_PACKAGE_PATH, and more.
Ditto. In terms of programming effort, we’re very close to what we’ve
been targeting for 1.0.
Ludo’.
next prev parent reply other threads:[~2018-06-15 9:42 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-13 21:07 preparing the next release v0.15.0 Ricardo Wurmus
2018-06-14 5:46 ` Pjotr Prins
2018-06-14 8:24 ` Ricardo Wurmus
2018-06-14 19:46 ` Pierre Neidhardt
2018-06-15 9:42 ` Ludovic Courtès [this message]
2018-06-14 9:14 ` Clément Lassieur
2018-07-02 9:44 ` Ludovic Courtès
2018-07-02 15:25 ` Efraim Flashner
2018-07-03 19:43 ` Ludovic Courtès
2018-07-03 20:24 ` Ricardo Wurmus
2018-07-04 7:28 ` Ludovic Courtès
2018-07-02 15:29 ` Nils Gillmann
2018-06-15 9:53 ` Ludovic Courtès
2018-06-15 13:11 ` Ricardo Wurmus
2018-06-18 20:31 ` Ricardo Wurmus
2018-06-18 22:44 ` Pierre Neidhardt
2018-06-19 1:49 ` Kei Kebreau
2018-06-19 7:25 ` Gábor Boskovits
2018-06-19 12:36 ` Marius Bakke
2018-06-19 12:48 ` Julien Lepiller
2018-06-19 14:32 ` swedebugia
2018-06-20 20:45 ` Ricardo Wurmus
2018-06-20 18:38 ` Kei Kebreau
2018-06-20 20:33 ` Nils Gillmann
2018-06-20 21:10 ` Ludovic Courtès
2018-06-21 1:05 ` Kei Kebreau
2018-06-21 10:45 ` Ricardo Wurmus
2018-06-20 21:11 ` Marius Bakke
2018-06-20 21:55 ` swedebugia
2018-06-21 1:06 ` Kei Kebreau
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87bmccv11w.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guix-devel@gnu.org \
--cc=rekado@elephly.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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.