Re: git structure and release policy

[Sam James]

> On 8 Nov 2022, at 16:34, Gavin Smith <gavinsmith0123@gmail.com> 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 Texinfo 6.8 was released (in July 2021), glibc 2.34
> was released (in August 2021) which broke compilation of Texinfo.  It might
> have been good to have made a new release at that point (e.g. 6.9 or
> 6.8.1).  It is frustrating to have a known problem that is stopping
> the project being built for some users.  A less severe problem was that
> the "info" program would crash if the user's language was set to
> Brazilian Portuguese.
> 
> I know distributions (like Debian) often have a very limited number of
> patches which they apply to releases for fixes such as this.  When there
> is a fix it would be good to be able to make a quick release with just
> that fix in it.

As a distro person (and indeed the person who reported the glibc 2.34 problem
- thanks for fixing it so quickly!), I'd really appreciate this and thanks
for thinking of us.

Even a 'stable' and 'master' branch would work fine, but Eli's suggestion
is very straightforward too.

Best,
sam

signature.asc
Description: Message signed with OpenPGP