Re: [Valgrind-developers] release 3.12.1 ?

[Julian S. <js...@ac...>]

Carl, hi.

There have been quite a few fixes on the trunk since 3.12 was released,
and I'm somewhat reluctant to merge them all to the branch, not least
because some of the fixes are quite big.  On the other hand I'd like to
get all of these fixes to users sooner rather than later.

I have the following alternative proposal: do a 3.13 release in early
May.  This would mean we could ship all the fixes on the trunk, and would
avoid the work of merging to the branch.  With a freeze/branch date of
Friday 21 April and a release date two weeks later, on Friday 5 May.

How does that sound?

The big 3 things that I'd like to fix before the freeze point are:

(1) some AVX2 insn sequences run the JIT out of space:
    https://bugs.kde.org/show_bug.cgi?id=375839

(2) on some processors, ARM64 hangs to due LL/SC looping:
    https://bugs.kde.org/show_bug.cgi?id=369459

(3) See if we can do anything about the poor state of the
    Mac OS 10.12 port.

Whatever other fixes we can get in before the freeze window, will
also be good, of course.

I don't regard the proposed 3.13 as shipping anything particularly new,
but instead as stabilising and solidifying what we shipped with 3.12.

J