bug-texinfo
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: git structure and release policy


From: Gavin Smith
Subject: Re: git structure and release policy
Date: Tue, 8 Nov 2022 19:55:43 +0000

On Tue, Nov 08, 2022 at 09:48:31PM +0200, Eli Zaretskii wrote:
> > From: Gavin Smith <gavinsmith0123@gmail.com>
> > Date: Tue, 8 Nov 2022 19:34:51 +0000
> > Cc: bug-texinfo@gnu.org
> > 
> > When we did a new major release, would we merge "master" into "release"?
> 
> No, you just cut a new release branch.  The release branch is only for
> a certain release or a series of releases, depending on the
> development strategy.  Basically, as long as you expect the next
> release to be a bugfix release, you keep developing it on the same
> release branch, and once you decide on a feature release, you cut a
> new release branch.  The name of the release branch can be the first
> version released from that branch, or some variant of that.

Thanks, that makes sense.




reply via email to

[Prev in Thread] Current Thread [Next in Thread]