help / color / mirror / code / Atom feed
From: dana <dana@dana.is>
To: "Bart Schaefer" <schaefer@brasslantern.com>
Cc: "Zsh hackers list" <zsh-workers@zsh.org>
Subject: Re: Branching (was Re: We should get 5.9** out soon)
Date: Sun, 03 Apr 2022 14:34:11 -0500	[thread overview]
Message-ID: <6a3e3908-d017-443b-be9b-e78840dc2265@www.fastmail.com> (raw)
In-Reply-To: <CAH+w=7a7qPFMdRppNuRqkAi8-DegNu5-jf3pyPpUF4wn36ERaA@mail.gmail.com>

On Sun 3 Apr 2022, at 12:04, Bart Schaefer wrote:
> 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.
> ...
> 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.

Yes, these were the two situations i was thinking of that could benefit
from having separate branches. Branching off at release-freeze time and
then back-porting any necessary additions from master is the method i
have experience with, but maybe some people on the team would be annoyed
by the extra steps


      reply	other threads:[~2022-04-03 19:34 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           ` Branching (was Re: We should get 5.9** out soon) Bart Schaefer
2022-04-03 19:34             ` dana [this message]

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=6a3e3908-d017-443b-be9b-e78840dc2265@www.fastmail.com \
    --to=dana@dana.is \
    --cc=schaefer@brasslantern.com \
    --cc=zsh-workers@zsh.org \


* 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).