|
From: Mark W. <mj...@re...> - 2013-05-08 09:47:03
|
On Thu, 2013-05-02 at 12:18 +0200, Julian Seward wrote:
> It'll soon be 9 months since 3.8.0 shipped, so 3.9.0 needs to go out
> in the next two months or so. I'd like to propose a freeze date of
> Friday 31 May (all new features/fixes should be in by then), and a two
> week stabilisation/test period, ending in release, on Friday 14 June.
That sounds like a good plan.
There are current 40 patches in the fedora valgrind 3.8.1 package [1]
and I would love to get rid of them. I believe they are now all already
in current subversion or at least proposed in bugs. I'll go over them
all again and make sure they really are in before May 31.
I made it so that recent fedora valgrind packages put a summary and all
diff files from failing regtests in the build.log. So it should be easy
to provide an overview of regtests for the architectures supported by
fedora (i686, x86_64, ppc, ppc64, arm7hl and s390x) [2].
If you make pre-release tar balls end of May I can push them to the
fedora rawhide koji builders. And I can probably get the same regtests
overview for RHEL5 and RHEL6 architectures.
> There's still a number of things I'd like to get fixed before release.
> - any further Dwarf4 fixes that we need
Do you have any particular bugs in mind for this?
Thanks,
Mark
[1] Fedora valgrind package source. Look in the fedora.spec file to see
a list of bug numbers corresponding to the patches:
http://pkgs.fedoraproject.org/cgit/valgrind.git/tree/
[2] Fedora koji builders, look in the latest build.log to see an
overview of the regtests at the end:
http://koji.fedoraproject.org/koji/packageinfo?packageID=98
http://ppc.koji.fedoraproject.org/koji/packageinfo?packageID=8430
http://arm.koji.fedoraproject.org/koji/packageinfo?packageID=9521
http://s390.koji.fedoraproject.org/koji/packageinfo?packageID=7265
|