From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: "Jakub Kądziołka" <kuba@kadziolka.net>,
"Guix Devel" <guix-devel@gnu.org>
Subject: Re: Update on the timeline for the release v1.2.
Date: Fri, 30 Oct 2020 22:41:46 -0400 [thread overview]
Message-ID: <87k0v7yv4l.fsf@gmail.com> (raw)
In-Reply-To: <87wnzj1shv.fsf@gnu.org> ("Ludovic Courtès"'s message of "Wed, 21 Oct 2020 17:57:48 +0200")
Hello everyone,
Sorry for being late in the discussion.
Ludovic Courtès <ludo@gnu.org> writes:
> zimoun <zimon.toutoune@gmail.com> skribis:
>
>>> > The proposed coming timeline is:
>>> >
>>> > - freeze starting the Oct. 26th
>>> > - last round for testing all over the week
>>> > - unfreeze the Oct. 29th and then create the branch
>>> > - minor bug fixes and all the papeword around (NEWS, blog, etc.)
>>> > - release Nov. 6th.
>>>
>>> Overall LGTM, but could you clarify what you mean by “freeze” on
>>> Oct. 26–29? No “important” changes to ‘master’, including to the
>>> manual, is that correct?
>>
>> Yes, no "important" changes to 'master' which means:
>> - no package or service updates
>
> I would phrase it as no _important_ package or service updates.
> Updating non-critical leaf packages or services is probably fine.
That's kind of already what master is for, so to me "important" doesn't
help that much in discerning what is OK to what is not :-).
>> - no manual entry
>> - only serious fixes under guix/ or installer(s)
>>
>> From my point of view, it is easier to freeze 'master' since everybody
>> can "guix pull" and check that everything is fine.
>> Otherwise, instead of the freeze, let create the branch and so "guix
>> pull --branch=version-1.2.0". It is up to you.
> Yeah we could also branch on the 26th and cherry-pick harmless changes
> from ‘master’, so people can still have fun on ‘master’.
>
> Mathieu, Marius, Maxim, Tobias: thoughts?
This sounds like a better idea to me. If something needs freezing, it's
technically much easier/safer to branch. I don't think it's reasonable
to expect all of our ~60 committers to have seen this email and know
they shouldn't push any important updates to master between now and the
6th of November (if I followed correctly).
Thank you!
Maxim
next prev parent reply other threads:[~2020-10-31 2:42 UTC|newest]
Thread overview: 61+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-29 12:16 Release v1.2 timetable zimoun
2020-09-29 15:07 ` Danny Milosavljevic
2020-10-07 14:51 ` zimoun
2020-10-07 15:39 ` Danny Milosavljevic
2020-10-07 15:56 ` Weird things found while fixing basic Guix packages Danny Milosavljevic
2020-10-12 11:53 ` Ludovic Courtès
2020-10-07 16:29 ` Release v1.2 timetable Danny Milosavljevic
2020-10-12 11:52 ` 32-bit builds on 64-bit hardware/VMs Ludovic Courtès
2020-10-12 12:06 ` Andreas Enge
2020-10-13 13:54 ` Ludovic Courtès
2020-10-07 16:31 ` Release v1.2 timetable Danny Milosavljevic
2020-10-05 10:18 ` pelzflorian (Florian Pelz)
2020-10-05 11:16 ` Julien Lepiller
2020-10-05 12:38 ` Miguel Ángel Arruga Vivas
2020-10-05 13:50 ` Julien Lepiller
2020-10-05 13:48 ` Ludovic Courtès
2020-10-05 21:17 ` zimoun
2020-10-06 6:57 ` Mathieu Othacehe
2020-10-07 14:36 ` zimoun
2020-10-21 9:14 ` Ludovic Courtès
2020-10-22 7:55 ` Mathieu Othacehe
2020-10-23 8:39 ` zimoun
2020-10-26 22:52 ` Ludovic Courtès
2020-10-06 6:59 ` Efraim Flashner
2020-10-06 7:05 ` Mathieu Othacehe
2020-10-06 7:26 ` Efraim Flashner
2020-10-06 7:57 ` Mathieu Othacehe
2020-10-07 14:39 ` zimoun
2020-10-09 18:25 ` Andreas Enge
2020-10-09 18:37 ` Danny Milosavljevic
2020-10-12 11:47 ` Shipping more installer images? Ludovic Courtès
2020-10-12 13:48 ` Danny Milosavljevic
2020-10-13 13:51 ` Ludovic Courtès
2020-10-13 14:19 ` Mathieu Othacehe
2020-10-13 21:23 ` Ludovic Courtès
2020-10-13 16:29 ` Danny Milosavljevic
2020-10-13 15:07 ` Efraim Flashner
2020-10-13 21:25 ` Ludovic Courtès
2020-10-19 15:17 ` Update on the timeline for the release v1.2 zimoun
2020-10-19 18:26 ` Miguel Ángel Arruga Vivas
2020-10-19 19:27 ` pelzflorian (Florian Pelz)
2020-10-19 21:57 ` Julien Lepiller
2020-10-21 12:44 ` Ludovic Courtès
2020-10-21 14:14 ` zimoun
2020-10-21 15:57 ` Ludovic Courtès
2020-10-21 18:03 ` Julien Lepiller
2020-10-21 21:27 ` Marius Bakke
2020-10-21 22:16 ` Ludovic Courtès
2020-10-21 22:23 ` zimoun
2020-10-21 22:36 ` zimoun
2020-10-26 22:44 ` Ludovic Courtès
2020-10-31 2:41 ` Maxim Cournoyer [this message]
2020-10-31 22:28 ` Branching for v1.2? Ludovic Courtès
2020-11-01 2:21 ` Miguel Ángel Arruga Vivas
2020-11-02 16:56 ` Ludovic Courtès
2020-11-02 8:43 ` zimoun
2020-11-02 13:20 ` Miguel Ángel Arruga Vivas
2020-11-02 15:00 ` Julien Lepiller
2020-11-02 17:56 ` pelzflorian (Florian Pelz)
2020-11-03 12:51 ` Tobias Geerinckx-Rice
2020-11-03 13:46 ` pelzflorian (Florian Pelz)
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87k0v7yv4l.fsf@gmail.com \
--to=maxim.cournoyer@gmail.com \
--cc=guix-devel@gnu.org \
--cc=kuba@kadziolka.net \
--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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.