Re: release branch policy and distributions

["Andreas K. Huettel" <dilfridge@gentoo.org>]

[-- Attachment #1: Type: text/plain, Size: 1100 bytes --]

> > For glibc 2.37 I've added the following text to the release announcement:
> > ~~~
> > Distributions are encouraged to regularly pull from the release/*
> > branches corresponding to the release they are using.  The release
> > branches will be updated with conservative bug fixes and new
> > features while retaining backwards compatibility.
> > ~~~
> >
> 
> ... I do have qualms about the definition of "conservative" here. The
> updates are certainly conservative wrt ABI but there has also been a trend
> to backport optimizations and this has occasionally led to bugs being
> introduced on the release branch, like
> https://sourceware.org/bugzilla/show_bug.cgi?id=29591.

Exactly. Please be *very* conservative about backporting performance
optimizations. Or even better, let's not backport them at all?

No offense, but for example long series of assembler patches for core 
routines that are probably understood by 2-3 persons worldwide?

-- 
Andreas K. Hüttel
dilfridge@gentoo.org
Gentoo Linux developer 
(council, qa, toolchain, base-system, perl, libreoffice)

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]