From: raingloom <raingloom@riseup.net>
To: Maxim Cournoyer <maxim.cournoyer@gmail.com>
Cc: Guix Devel <guix-devel@gnu.org>
Subject: Re: Release v1.4 (or 2.0): process and schedule ?
Date: Mon, 20 Dec 2021 04:43:17 +0100 [thread overview]
Message-ID: <20211220044317.6bf51fdd@riseup.net> (raw)
In-Reply-To: <87v8zk2fe3.fsf@gmail.com>
On Sun, 19 Dec 2021 21:12:36 -0500
Maxim Cournoyer <maxim.cournoyer@gmail.com> wrote:
> Hi Simon,
>
> zimoun <zimon.toutoune@gmail.com> writes:
>
> > Hi,
> >
> > Now core-updates-frozen is merged. Now The Big Change [1 ]is done.
> > Do we go for v1.4 or v2.0?
>
> As I've mentioned previously, I'd go for a 1.4.0 release, since
> overall we've refined and improved (greatly!) what we already had
> rather than introduced something revolutionary. I'd keep a 2.0.0 for
> when we have p2p distributed substitutes, a custom graphical tool
> and/or integration with the 'Software' application in GNOME, this
> kind of big user-facing changes. But that's just my personal opinion
> :-). If the majority feels a 2.0.0 is more suitable, I won't mind.
Agreed, if we go by something like semver.
next prev parent reply other threads:[~2021-12-20 6:44 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-15 8:37 Release process and schedule ? zimoun
2021-12-17 10:03 ` Release v1.4 (or 2.0): " zimoun
2021-12-20 2:12 ` Maxim Cournoyer
2021-12-20 3:43 ` raingloom [this message]
2021-12-20 9:04 ` zimoun
2021-12-20 9:14 ` zimoun
2021-12-20 21:24 ` Ludovic Courtès
2021-12-20 22:54 ` zimoun
2021-12-20 18:12 ` Bengt Richter
2021-12-21 20:48 ` Vagrant Cascadian
2021-12-21 21:20 ` Vagrant Cascadian
2022-01-03 14:31 ` Ludovic Courtès
2022-01-03 16:32 ` Vagrant Cascadian
2021-12-27 3:46 ` Maxim Cournoyer
2022-01-03 14:33 ` Ludovic Courtès
2022-01-04 16:24 ` Maxim Cournoyer
2022-01-04 19:32 ` Chris Marusich
2022-01-06 13:49 ` Maxim Cournoyer
2022-01-09 2:21 ` Chris Marusich
2022-01-18 5:05 ` Maxim Cournoyer
2022-01-18 13:20 ` Ludovic Courtès
2022-01-15 19:26 ` Vagrant Cascadian
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=20211220044317.6bf51fdd@riseup.net \
--to=raingloom@riseup.net \
--cc=guix-devel@gnu.org \
--cc=maxim.cournoyer@gmail.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
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).