From: Bart Schaefer <firstname.lastname@example.org>
To: dana <email@example.com>
Cc: Zsh hackers list <firstname.lastname@example.org>
Subject: Branching (was Re: We should get 5.9** out soon)
Date: Sun, 3 Apr 2022 10:04:22 -0700 [thread overview]
Message-ID: <CAH+w=7a7qPFMdRppNuRqkAi8-DegNu5-jf3pyPpUF4wn36ERaA@mail.gmail.com> (raw)
On Sat, Apr 2, 2022 at 3:47 PM dana <email@example.com> wrote:
> PS: There has been some discussion in the past about changing the release
> process so that instead of going directly off master we e.g. make a 5.9
> branch as the 'cycle' is winding down and release off that.
The benefit of a separate release branch is that we don't have to
coordinate a code freeze among the full group with "git push" access.
That was not much of a problem when we had only about three people in
that set, but as we've opened it to a larger number of trusted
individuals it takes more effort.
Aside from just proceeding as we have been (which is fine for 5.9), an
alternate plan would be to have a development branch and only merge
it back to the main branch at release time. That would avoid creating
several possibly-active branches.
On the other hand, if we want to introduce "long-term support" for
major version numbers, having a branch to which events like the 5.8 ->
5.8.1 security release could be pushed would be the way to go.
next prev parent reply other threads:[~2022-04-03 17:05 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-30 16:51 We should get 5.9** out soon Bart Schaefer
2022-03-31 0:34 ` dana
2022-03-31 0:48 ` Bart Schaefer
2022-03-31 10:23 ` Peter Stephenson
2022-03-31 10:47 ` Daniel Shahaf
2022-03-31 10:54 ` Axel Beckert
2022-03-31 11:05 ` Peter Stephenson
2022-03-31 23:31 ` Daniel Shahaf
2022-04-02 22:42 ` dana
2022-04-03 16:07 ` Peter Stephenson
2022-04-03 16:39 ` Bart Schaefer
2022-04-03 17:04 ` Bart Schaefer [this message]
2022-04-03 19:34 ` Branching (was Re: We should get 5.9** out soon) dana
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:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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
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 NNTP newsgroup(s).