Re: Release branch added to git

[Gavin Smith]

On Sat, Nov 12, 2022 at 02:30:11PM -0800, Raymond Toy wrote:
> On Sat, Nov 12, 2022 at 2:27 PM Gavin Smith <gavinsmith0123@gmail.com>
> wrote:
> 
> > On Tue, Nov 08, 2022 at 07:55:44PM +0000, Gavin Smith wrote:
> > > > 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.
> >
> >
> > I have added a release branch to the git repository, called "release/7.0".
> > Please do not commit anything to it right now if you have access.
> >
> 
> Can you clarify how this is related to the tag texinfo-7.0?  Will they have
> the same stuff?

The tag texinfo-7.0 is a fixed tag, which is at the base of the release/7.0
branch.  As more commits are made to release/7.0, the release/7.0 branch
will move ahead, leaving texinfo-7.0 behind.  At some point soon, there
will be a texinfo-7.0.1 release, which will occur on the release/7.0
branch.  If there are more bug-fixes/translation updates/other minor or
harmless updates, these may also be made on the release/7.0 branch, tagged
in fixed positions as texinfo-7.0.2, texinfo-7.0.3, etc., along the branch.