|
From: Mark W. <ma...@kl...> - 2022-09-05 18:29:17
|
Hi, The last few releases were 6 months apart around in April and October. I propose we try to do the next release in October again. If possible I would like to try to aim for October 22. Which gives us ~7 weeks from now. Please look at features and bugs you could finish in about a month, then we have ~2 weeks for stabilization and fixups. Cheers, Mark |
|
From: Paul F. <pj...@wa...> - 2022-09-25 09:34:22
|
> On 5 Sep 2022, at 20:29, Mark Wielaard <ma...@kl...> wrote: > > Hi, > > The last few releases were 6 months apart around in April and October. > I propose we try to do the next release in October again. If possible I > would like to try to aim for October 22. Which gives us ~7 weeks from > now. > > Please look at features and bugs you could finish in about a month, > then we have ~2 weeks for stabilization and fixups. > Hi Mark Are we going to review the LOONGARCH patches for 3.20? On my side, there are a few bugzilla items I’ve been following recently: https://bugs.kde.org/show_bug.cgi?id=458915 <https://bugs.kde.org/show_bug.cgi?id=458915> https://bugs.kde.org/show_bug.cgi?id=304980 <https://bugs.kde.org/show_bug.cgi?id=304980> (this one looks like it needs some DWARF expertise) I think I’ll have time for this old one https://bugs.kde.org/show_bug.cgi?id=131186 <https://bugs.kde.org/show_bug.cgi?id=131186> There’s https://bugs.kde.org/show_bug.cgi?id=452779 <https://bugs.kde.org/show_bug.cgi?id=452779> which is affecting chimera and gentoo On FreeBSD someone sent my a patch for handling the case where the kernel sysctl has disabled mmap of WRITE+EXECUTE segments. I haven’t tested it, particularly for older FreeBSDs. Finally, one of the gdbserver retests started failing on FreeBSD recently, I’d like to debug it if I have time. A+ Paul |
|
From: Carl L. <ce...@us...> - 2022-10-18 17:50:34
|
Mark:
On Mon, 2022-09-05 at 20:29 +0200, Mark Wielaard wrote:
> Hi,
>
> The last few releases were 6 months apart around in April and
> October.
> I propose we try to do the next release in October again. If possible
> I
> would like to try to aim for October 22. Which gives us ~7 weeks from
> now.
>
> Please look at features and bugs you could finish in about a month,
> then we have ~2 weeks for stabilization and fixups.
I was thinking the date is fast approaching and I hadn't seen anything
on a release.
At this point, the Power support is all in place I don't have anything
pending. Not sure about other architectures.
I will be out of the office next week so will not be able to test any
release candidates next week.
Anyway, just thought someone should poke at this and see how things
stand for doing a release.
Carl Love
|
|
From: Nicholas N. <n.n...@gm...> - 2022-10-18 20:04:14
|
It would be great to have a new release out. Currently you have to use a trunk build of Valgrind with Rust code because of Dwarf 5 features that Rust uses. Nick On Wed, 19 Oct 2022 at 04:51, Carl Love <ce...@us...> wrote: > > Mark: > > On Mon, 2022-09-05 at 20:29 +0200, Mark Wielaard wrote: > > Hi, > > > > The last few releases were 6 months apart around in April and > > October. > > I propose we try to do the next release in October again. If possible > > I > > would like to try to aim for October 22. Which gives us ~7 weeks from > > now. > > > > Please look at features and bugs you could finish in about a month, > > then we have ~2 weeks for stabilization and fixups. > > I was thinking the date is fast approaching and I hadn't seen anything > on a release. > > At this point, the Power support is all in place I don't have anything > pending. Not sure about other architectures. > > I will be out of the office next week so will not be able to test any > release candidates next week. > > Anyway, just thought someone should poke at this and see how things > stand for doing a release. > > Carl Love > > > > _______________________________________________ > Valgrind-developers mailing list > Val...@li... > https://lists.sourceforge.net/lists/listinfo/valgrind-developers > |
|
From: Mark W. <ma...@kl...> - 2022-10-18 21:31:08
|
Hi, On Wed, Oct 19, 2022 at 07:03:56AM +1100, Nicholas Nethercote wrote: > It would be great to have a new release out. Currently you have to use a > trunk build of Valgrind with Rust code because of Dwarf 5 features that > Rust uses. I admit that I had wanted to do more work before the release, thinking 7 weeks was enough time. Now it suddenly is in less than a week... But I don't believe we have any regressions. So it is probably still a good idea to just do a new release. Lots of people only use actualy releases. continued below... On Wed, 19 Oct 2022 at 04:51, Carl Love <ce...@us...> wrote: > I was thinking the date is fast approaching and I hadn't seen anything > on a release. > > At this point, the Power support is all in place I don't have anything > pending. Not sure about other architectures. > > I will be out of the office next week so will not be able to test any > release candidates next week. > > Anyway, just thought someone should poke at this and see how things > stand for doing a release. I think Power is indeed in a good state. Paul said on irc that FreeBSD also looks good. He is looking at some FreeBSD 14 (the unstable dev branch) issues, but those shouldn't be blocking. There are some issues with the auxchecks against newer glibc, that runs an older gnu scientific library testsuite which shows some issues with random* tests. But I think this isn't a valgrind bug, it looks like a change in how glibc handles some random bits/calls. But I don't know about any other issues/regressions. I'll try to do a test/rc release tomorrow and see how things look. Cheers, Mark |
|
From: Paul F. <pj...@wa...> - 2022-10-19 05:21:12
|
On 10/18/22 22:03, Nicholas Nethercote wrote: > It would be great to have a new release out. Currently you have to use a > trunk build of Valgrind with Rust code because of Dwarf 5 features that > Rust uses. > > Nick Hi I'm also ready to go. A+ Paul |