Glibc stable release process (Glibc 2.26.1)
Arjan van de Ven
arjan@linux.intel.com
Wed Oct 4 12:52:00 GMT 2017
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
More information about the Libc-alpha
mailing list