Re: [Valgrind-users] Bug fix release?
On Tue, Aug 8, 2017 at 2:02 PM, John Reiser wrote: > There was a recent fix for a bug in 3.13.0 "--xml-socket doesn't work": >> >> https://bugs.kde.org/show_bug.cgi?id=382998 >> > > How does the valgrind project make a decision about releasing a bug fix >> version? >> > > The number, nature, severity, and impact of the bugs; > the intrusiveness of the fixes, and the resources available > to create a new version, test it, and distribute the result. > > >> Is there any possibility this fix will be in a release "soon" or at least >> before mid-2018? >> > > The patch already has been applied to the source tree, > so it will be in the next regular major release, which probably > will be some time in the last 3 months of this calendar year. > I'd say that it is unlikely that there will be a special bug fix release. > Great - thanks for the info John! - Andy > > The fix for this bug is so trivial that almost any software developer > should be successful at checking out the code and re-building it. > So why don't you try that? (See README, README_DEVELOPERS, > README_PACKAGERS, etc.) > > -- > > > -- > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > ___ > Valgrind-users mailing list > Valgrind-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/valgrind-users > -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot___ Valgrind-users mailing list Valgrind-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/valgrind-users
Re: [Valgrind-users] Bug fix release?
There was a recent fix for a bug in 3.13.0 "--xml-socket doesn't work": https://bugs.kde.org/show_bug.cgi?id=382998 How does the valgrind project make a decision about releasing a bug fix version? The number, nature, severity, and impact of the bugs; the intrusiveness of the fixes, and the resources available to create a new version, test it, and distribute the result. Is there any possibility this fix will be in a release "soon" or at least before mid-2018? The patch already has been applied to the source tree, so it will be in the next regular major release, which probably will be some time in the last 3 months of this calendar year. I'd say that it is unlikely that there will be a special bug fix release. The fix for this bug is so trivial that almost any software developer should be successful at checking out the code and re-building it. So why don't you try that? (See README, README_DEVELOPERS, README_PACKAGERS, etc.) -- -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot ___ Valgrind-users mailing list Valgrind-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/valgrind-users
[Valgrind-users] Bug fix release?
There was a recent fix for a bug in 3.13.0 "--xml-socket doesn't work": https://bugs.kde.org/show_bug.cgi?id=382998 This bug prevents using valgrind with Qt Creator on macOS 10.12. It's a showstopper for some because we can't downgrade to 3.12.0 (it doesn't work on macOS 10.12). (See https://bugreports.qt.io/browse/QTCREATORBUG-18473 ) How does the valgrind project make a decision about releasing a bug fix version? Is there any possibility this fix will be in a release "soon" or at least before mid-2018? Thanks! - Andy -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot___ Valgrind-users mailing list Valgrind-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/valgrind-users
