From: Leo Famulari <leo@famulari.name>
To: zimoun <zimon.toutoune@gmail.com>
Cc: Guix Devel <guix-devel@gnu.org>
Subject: Re: Release on April 18th?
Date: Fri, 5 Mar 2021 15:58:46 -0500 [thread overview]
Message-ID: <YEKbhnt1AaYz9mmI@jasmine.lan> (raw)
In-Reply-To: <86im65s685.fsf@gmail.com>
On Fri, Mar 05, 2021 at 09:20:10PM +0100, zimoun wrote:
> On #guix, I proposed [1] without an answer (yet :-)):
>
> what is the current blocking for merging core-updates? I mean
> the last merge seems from May 2020. If all the branch is not in
> a state to be mergeable, maybe we could simply merge a part of
> it. WDYT?
>
> 1: <http://logs.guix.gnu.org/guix/2021-03-05.log#194536>
Anything is possible, but I think that determining which parts are ready
to merge will be just as much work as completing the entire branch.
Unless people have been maintaining private branches with specific
updates cherry-picked and can vouch that they are working well.
> On Fri, 05 Mar 2021 at 14:27, Leo Famulari <leo@famulari.name> wrote:
> > Simon, is there a reason you chose April 18 for the release? Or could we
> > choose a later date?
>
> Because a) it is ~6 months later than previous one and I think releasing
> twice a year is the process we should adopt, b) it is an anniversary
> (first commit) and by chance the other anniversary (first public
> announce on Nov. 23rd) is spaced by ~6 month.
Agreed.
> However, I think it is a bad idea to postpone and wait for core-updates
> merge. We should fix deadlines for releasing everything ~6 months and
> simply make it happen. IMHO.
Agreed. But I don't think we can force core-updates, or we will regret
it when problems slip through. It's better to release on schedule
without core-updates.
> That’s said, when could core-update be merged to master? What could be
> the deadline? From my point of view, delaying a couple (meaning 2 or 3
> here ;-)) of weeks from April 18th sounds fine with me.
>
> Even, from my understanding, we should minor release ASAP, e.g., on
> April 18th or even before if possible. And we could also plan to
> release (major or minor) after the core-updates merge (say in June).
> Then on Nov. 23rd, I think it could be nice to have another release.
> Well, since Guix is rolling-release, releasing should be smooth.
>
> BTW, I sympathize with the frustration about core-updates not merged
> since last May. On the other hand, I did nothing to help in the merging
> process. :-( Maybe, we could organize a hackathon or synchronize a
> core-updates week: freeze the branch and address issues. WDYT?
So, based on the status of ci.guix.gnu.org, I feel that we could not have
begun working on core-updates before January 2021. And then, in January,
staging was in progress.
Now, ci.guix.gnu.org is working well, and we can work more quickly and
confidently. However, my experience in the past tells me that 6 weeks is
not quite long enough to complete the branch and validate it for a
release. But, it really depends on how many people can help.
next prev parent reply other threads:[~2021-03-05 20:59 UTC|newest]
Thread overview: 64+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-02 14:51 Release on April 18th? zimoun
2021-03-02 16:00 ` Julien Lepiller
2021-03-02 20:03 ` Leo Famulari
2021-03-05 14:31 ` Andreas Enge
2021-03-05 19:27 ` Leo Famulari
2021-03-05 20:20 ` zimoun
2021-03-05 20:58 ` Leo Famulari [this message]
2021-03-05 23:57 ` zimoun
2021-03-06 20:14 ` Tobias Geerinckx-Rice
2021-03-03 14:16 ` Ludovic Courtès
2021-03-03 18:51 ` Leo Famulari
2021-03-04 9:41 ` zimoun
2021-03-04 19:07 ` Leo Famulari
2021-03-04 22:18 ` zimoun
2021-03-04 22:43 ` Leo Famulari
2021-03-05 20:19 ` Leo Famulari
2021-03-05 23:58 ` zimoun
2021-03-06 18:56 ` Leo Famulari
2021-03-06 19:06 ` Leo Famulari
2021-03-06 23:22 ` Leo Famulari
2021-03-07 3:51 ` Raghav Gururajan
2021-03-07 5:39 ` Raghav Gururajan
2021-03-07 20:44 ` Leo Famulari
2021-03-07 20:56 ` Raghav Gururajan
2021-03-07 20:50 ` Leo Famulari
2021-03-08 9:38 ` zimoun
2021-03-05 20:21 ` Leo Famulari
2021-03-09 18:17 ` Chris Marusich
2021-03-09 21:32 ` Vincent Legoll
2021-03-10 8:30 ` Release on April 18th? (ppc64le support specifically) Efraim Flashner
2021-03-11 9:10 ` Release on April 18th? Chris Marusich
2021-03-12 8:02 ` Vincent Legoll
2021-03-12 18:42 ` Chris Marusich
2021-03-12 18:52 ` Chris Marusich
2021-03-14 12:31 ` Vincent Legoll
2021-03-15 16:36 ` Ludovic Courtès
2021-03-16 4:03 ` Let's include powerpc64le-linux in the next release (was: Re: Release on April 18th?) Chris Marusich
2021-03-16 7:08 ` Efraim Flashner
2021-03-16 8:10 ` Léo Le Bouter
2021-03-23 13:42 ` Let's include powerpc64le-linux in the next release Ludovic Courtès
2021-03-23 13:47 ` Léo Le Bouter
2021-03-23 14:01 ` Tobias Geerinckx-Rice
2021-03-30 8:23 ` Ludovic Courtès
2021-03-30 22:20 ` Vincent Legoll
2021-03-23 17:09 ` Let's include powerpc64le-linux in the next release, " Chris Marusich
2021-03-10 13:27 ` Release on April 18th? zimoun
2021-03-10 15:30 ` Efraim Flashner
2021-03-10 15:59 ` zimoun
2021-03-10 18:33 ` Efraim Flashner
2021-03-11 8:58 ` Chris Marusich
2021-03-11 13:30 ` Efraim Flashner
2021-03-12 8:33 ` Chris Marusich
2021-03-12 10:11 ` Andreas Enge
2021-03-12 13:43 ` Efraim Flashner
-- strict thread matches above, loose matches on Subject: below --
2021-02-28 6:53 I've rebased wip-ppc64le onto core-updates Chris Marusich
2021-02-28 20:42 ` Léo Le Bouter
2021-03-01 19:14 ` Tobias Platen
2021-03-01 21:36 ` jbranso
2021-03-10 10:17 ` Ludovic Courtès
2021-03-10 10:37 ` Efraim Flashner
2021-03-11 8:24 ` Chris Marusich
2021-03-11 8:37 ` Léo Le Bouter
2021-03-15 16:25 ` Ludovic Courtès
2021-03-16 4:26 ` I've rebased wip-ppc64le onto core-updates, Re: Release on April 18th? Chris Marusich
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=YEKbhnt1AaYz9mmI@jasmine.lan \
--to=leo@famulari.name \
--cc=guix-devel@gnu.org \
--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).