|
From: Julian S. <js...@ac...> - 2020-04-27 13:54:49
|
Greetings. Unfortunately the previous plan dated 5 Feb 2020 didn't work out, partly due to lack of time and partly because various architectures (MIPS, s390 and POWER) were still broken by the "grail" (&&-recovery) changes that landed at the start of the year. The situation has now improved. All architectures now work again -- a big thank-you to the port maintainers for fixing them. However, available time remains scarce, and the need to freeze and ship has increased. As the trunk seems in a fairly good state right now, the revised plan is as follows: at the end of day, UTC+2, Weds 29 April, a 3.16 branch will be made from the trunk. Then there will be a two week stabilisation period, so that the release will be made on 14 May. Once the branch has been made, we can cherry pick low-risk and/or important fixes that land on the trunk after the branching, providing there is a reasonable case for them. J |
|
From: Mark W. <ma...@kl...> - 2020-05-01 15:16:36
|
Hi, On Mon, Apr 27, 2020 at 03:36:57PM +0200, Julian Seward wrote: > Unfortunately the previous plan dated 5 Feb 2020 didn't work out, partly due > to lack of time and partly because various architectures (MIPS, s390 and > POWER) were still broken by the "grail" (&&-recovery) changes that landed at > the start of the year. > > The situation has now improved. All architectures now work again -- a big > thank-you to the port maintainers for fixing them. However, available time > remains scarce, and the need to freeze and ship has increased. As the trunk > seems in a fairly good state right now, the revised plan is as follows: at the > end of day, UTC+2, Weds 29 April, a 3.16 branch will be made from the trunk. > Then there will be a two week stabilisation period, so that the release will > be made on 14 May. > > Once the branch has been made, we can cherry pick low-risk and/or important > fixes that land on the trunk after the branching, providing there is a > reasonable case for them. To celebrate that we have a branch now and to make it easier for people to test I created Fedora rawhide and copr packages from the current VALGRIND_3_16_BRANCH git branch: https://koji.fedoraproject.org/koji/buildinfo?buildID=1500383 (aarch64, armv7hl, i686, ppc64le, s390x, x86_64) https://copr.fedorainfracloud.org/coprs/mjw/valgrind-3.16.0/ (Epel for CentOS 7, aarch64 and x86_64 Epel for CentOS 8, aarch64 and x86_64 Fedora 30, aarch64, i386 and x86_64 Fedora 31, aarch64 and x86_64 Fedora 32, aarch64 and x86_64) A quick check of the test results make it look like we have a pretty good branch already. Cheers, Mark |