This is the mail archive of the libc-alpha@sourceware.org mailing list for the glibc project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: Glibc stable release process (Glibc 2.26.1)

On 10/04/2017 02:52 PM, Arjan van de Ven wrote:

On 10/4/2017 1:36 AM, Andreas Schwab wrote:

On Okt 04 2017, Siddhesh Poyarekar <siddhesh@sourceware.org> wrote:


0. Must not break ABI on that branch


We must not break the ABI on any branch.  What you probably mean is that
we must not extend the ABI on the release branch.


and no new symvers
I'd expect this to be both backward (like usual) but also forward compatible 
as a goal.

now if a CVE requires a new symver, I'm sure that will trump that rule
No, if a new symbol version is required, we cannot backport the fix. We need to leave it unfixed or come up with a different fix. 

Thanks,
Florian
Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]