unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel@gnu.org
Subject: Re: GNU Guix 1.4.0 released
Date: Tue, 03 Jan 2023 10:08:53 -0500	[thread overview]
Message-ID: <87v8ln1wqi.fsf@gmail.com> (raw)
In-Reply-To: <874jt89e9e.fsf@gnu.org> ("Ludovic Courtès"'s message of "Tue, 03 Jan 2023 10:08:29 +0100")

Hi Ludo,

Ludovic Courtès <ludo@gnu.org> writes:

> Hi!
>
> Maxim Cournoyer <maxim.cournoyer@gmail.com> skribis:
>
>> Congrats, and yay!  It's a hell of a release! :-) Let's try to make more
>> punctual ones from now on, and also try to lower the amount of manual
>> labor producing one incurs (by streamlining the process), as speaking
>> for me, this was one of the reasons I kept putting it back.
>
> Definitely, let’s see how we can make the process smoother.
>
> In my experience though, a lot of the work is coordination: keeping
> track of what needs to be done, open bugs, calling for testing, etc.
>
> I think we should start thinking about the next release, forming a
> small release team, and I’ll be happy to mentor!

Great!  I think it'd be nice to have automation as much as possible,
with the end goal of pressing a button and having all the artifacts and
texts (at least templates of the final) produced.

-- 
Thanks,
Maxim


  reply	other threads:[~2023-01-03 15:09 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-19 14:25 GNU Guix 1.4.0 released Ludovic Courtès
2022-12-27  3:37 ` Maxim Cournoyer
2023-01-03  9:08   ` Ludovic Courtès
2023-01-03 15:08     ` Maxim Cournoyer [this message]
2023-01-03 16:09     ` indieterminacy
2023-01-03 18:42       ` Joshua Branson
2023-01-03 20:35         ` indieterminacy
2023-01-03 23:16         ` indieterminacy
2023-01-05  9:57     ` Simon Tournier
2023-01-09 17:19       ` Setting up the release team Ludovic Courtès
2023-01-14 12:04       ` GNU Guix 1.4.0 released Tobias Platen

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=87v8ln1wqi.fsf@gmail.com \
    --to=maxim.cournoyer@gmail.com \
    --cc=guix-devel@gnu.org \
    --cc=ludo@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).