From: zimoun <zimon.toutoune@gmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: Guix Devel <guix-devel@gnu.org>,
GNU Guix maintainers <guix-maintainers@gnu.org>
Subject: Re: Release v1.4?
Date: Sun, 05 Jun 2022 19:57:37 +0200 [thread overview]
Message-ID: <864k0z0z8u.fsf@gmail.com> (raw)
In-Reply-To: <87y1yditsq.fsf@gnu.org>
Hi,
On Fri, 03 Jun 2022 at 18:41, Ludovic Courtès <ludo@gnu.org> wrote:
> guix time-machine --branch=staging -- …
>
> Remaining things to check:
>
> - [ ] system tests
> - [ ] status on non-x86_64 architectures
I agree. To me, it is part of the same effort. From my point of view,
we missed the window for releasing at the previous core-updates merge.
I would like to avoid to miss it. :-)
Somehow, we all have various constraints on our agenda so if we do not
set some deadlines in advance, it is hard to free some slots compared to
the continuous other “urgent” tasks from elsewhere.
My email is a call (July is a proposal) for synchronizing our agenda and
agree on some deadlines and make them happen.
Cheers,
simon
next prev parent reply other threads:[~2022-06-05 17:58 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-01 8:35 Release v1.4? zimoun
2022-06-03 16:41 ` Ludovic Courtès
2022-06-05 17:57 ` zimoun [this message]
2022-06-05 22:31 ` vidak
2022-06-06 15:39 ` Maxim Cournoyer
2022-06-06 21:17 ` Merging ‘staging’? Ludovic Courtès
2022-06-08 11:50 ` Efraim Flashner
2022-06-08 21:24 ` Ludovic Courtès
2022-06-10 7:57 ` Efraim Flashner
2022-06-11 9:53 ` Ludovic Courtès
2022-06-11 10:49 ` Tom Fitzhenry
2022-06-12 3:58 ` Efraim Flashner
2022-06-12 21:08 ` Ludovic Courtès
2022-06-13 7:03 ` Ludovic Courtès
2022-06-14 4:01 ` Thiago Jung Bauermann
2022-06-14 10:32 ` Release ? (was: Merging ‘staging’?) zimoun
2022-06-14 13:08 ` Efraim Flashner
2022-06-15 9:21 ` Release ? Ludovic Courtès
2022-06-09 17:19 ` Merging ‘staging’? pelzflorian (Florian Pelz)
2022-06-09 17:41 ` Efraim Flashner
2022-06-09 19:02 ` pelzflorian (Florian Pelz)
2022-06-10 6:07 ` pelzflorian (Florian Pelz)
2022-06-11 7:35 ` pelzflorian (Florian Pelz)
2022-07-15 10:52 ` Rock64 segfaults (was: Merging ‘staging’?) Timotej Lazar
2022-06-12 4:54 ` Merging ‘staging’? Thiago Jung Bauermann
2022-06-12 21:06 ` Ludovic Courtès
2022-06-10 15:47 ` Release v1.4? Josselin Poiret
2022-06-15 8:54 ` Ludovic Courtès
2022-06-15 16:51 ` Gábor Boskovits
2022-06-16 8:59 ` Josselin Poiret
2022-06-17 15:31 ` Ludovic Courtès
2022-06-17 15:37 ` Brian Cully via Development of GNU Guix and the GNU System distribution.
2022-06-19 3:33 ` Further thoughts on Xorg "vs" Wayland etc -- was: " bokr
2022-06-19 18:16 ` Philip McGrath
2022-06-22 13:31 ` Ludovic Courtès
2022-06-28 9:02 ` Efraim Flashner
2022-06-17 15:45 ` Josselin Poiret
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=864k0z0z8u.fsf@gmail.com \
--to=zimon.toutoune@gmail.com \
--cc=guix-devel@gnu.org \
--cc=guix-maintainers@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).