> On 8 Nov 2022, at 16:34, Gavin Smith wrote:
>
> I thought we could discuss whether we should use any kind of git branch
> structure for the development of Texinfo. A related question is whether
> we should do minor releases for bug fixes and translation updates. For
> example, shortly after
On Tue, Nov 08, 2022 at 09:48:31PM +0200, Eli Zaretskii wrote:
> > From: Gavin Smith
> > Date: Tue, 8 Nov 2022 19:34:51 +
> > 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 branc
> From: Gavin Smith
> Date: Tue, 8 Nov 2022 19:34:51 +
> 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
dev
On Tue, Nov 08, 2022 at 07:07:49PM +0200, Eli Zaretskii wrote:
> > What kind of structure should we use to apply fixes to both the main
> > line of development and to the release branch?
>
> There are basically 2 workflows:
>
> . fixes for the release branch are committed to that branch, and th
> From: Gavin Smith
> Date: Tue, 8 Nov 2022 16:34:03 +
>
> We have always developed Texinfo in a linear fashion (in git and before
> that SVN). However, the development repository is not necessarily always
> in a fit state to be released with new work being done. So one question
> I have is
I thought we could discuss whether we should use any kind of git branch
structure for the development of Texinfo. A related question is whether
we should do minor releases for bug fixes and translation updates. For
example, shortly after Texinfo 6.8 was released (in July 2021), glibc 2.34
was rel
