unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Vagrant Cascadian <vagrant@debian.org>
To: Maxim Cournoyer <maxim.cournoyer@gmail.com>,
	zimoun <zimon.toutoune@gmail.com>
Cc: Guix Devel <guix-devel@gnu.org>
Subject: Re: Release v1.4 (or 2.0): process and schedule ?
Date: Tue, 21 Dec 2021 12:48:35 -0800	[thread overview]
Message-ID: <877dbxznto.fsf@ponder> (raw)
In-Reply-To: <87v8zk2fe3.fsf@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1862 bytes --]

On 2021-12-19, Maxim Cournoyer wrote:
> zimoun <zimon.toutoune@gmail.com> writes:
>> 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.
>
>> In both case, what is the target for a release date?  I propose January
>> 31rst.  WDYT?
>
> I'd like to fix #52051 before issuing the first release candidate (RC).
> Assuming this can be made before the end of January with the first RC
> coming out around New Year, and that the kind of collaboration I've seen
> in the last weeks continues at the same intensity, this seems
> achievable.

Would it be appropriate to fix the ~700 low-hanbging fruit issues that
are identified by:

  guix lint --checkers=description,synopsis

It is not the most exciting work technically, but it is relatively easy,
and low risk, maybe the worst it does is put a bit more work on
translators...

Maybe there are also other low hanging fruit guix lint knows about that
would not be particularly disruptive?

It is not particularly urgent for a release, per se, but I suspect it
will just grow and grow without some sort of cycle to address such
trivial issues... and doing such cleanup before making a release would
aim for a higher standard of craftspersonship. :)


I can maybe try to help stir up a coordinated effort, if folks are
interested in pursuing this line of thinking!


live well,
  vagrant

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 227 bytes --]

  parent reply	other threads:[~2021-12-21 20:49 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
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 [this message]
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=877dbxznto.fsf@ponder \
    --to=vagrant@debian.org \
    --cc=guix-devel@gnu.org \
    --cc=maxim.cournoyer@gmail.com \
    --cc=zimon.toutoune@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).