|
From: <sv...@va...> - 2005-08-03 17:01:56
|
Author: sewardj Date: 2005-08-03 18:01:51 +0100 (Wed, 03 Aug 2005) New Revision: 4313 Log: Hopefully this is the final commit for 3.0.0. Modified: trunk/NEWS trunk/configure.in trunk/docs/internals/release-HOWTO Modified: trunk/NEWS =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D --- trunk/NEWS 2005-08-03 16:40:10 UTC (rev 4312) +++ trunk/NEWS 2005-08-03 17:01:51 UTC (rev 4313) @@ -149,7 +149,8 @@ 101543 Support fadvise64 syscalls 75247 x86_64/amd64 support (the biggest "bug" we have ever fixed) =20 -(3.0RC1: 27 July 05, vex r1303, valgrind r4283). +(3.0RC1: 27 July 05, vex r1303, valgrind r4283). +(3.0.0: 3 August 05, vex r1313, valgrind r4313). =20 =20 =20 Modified: trunk/configure.in =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D --- trunk/configure.in 2005-08-03 16:40:10 UTC (rev 4312) +++ trunk/configure.in 2005-08-03 17:01:51 UTC (rev 4313) @@ -1,5 +1,5 @@ # Process this file with autoconf to produce a configure script. -AC_INIT(Valgrind, 3.0.RC1, val...@li...) +AC_INIT(Valgrind, 3.0.0, val...@li...) AC_CONFIG_SRCDIR(coregrind/m_main.c) AM_CONFIG_HEADER(config.h) AM_INIT_AUTOMAKE Modified: trunk/docs/internals/release-HOWTO =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D --- trunk/docs/internals/release-HOWTO 2005-08-03 16:40:10 UTC (rev 4312) +++ trunk/docs/internals/release-HOWTO 2005-08-03 17:01:51 UTC (rev 4313) @@ -15,8 +15,20 @@ of tasks for the official release.) =20 - Write release notes, add to NEWS. Include a list of fixed bugs from - Bugzilla. [[We should decide a defined way of obtaining this list so = it's - consistent and so we don't have to work it out anew each time.]] + Bugzilla. It's unclear how to do this consistently. The approach + taken for 3.0.0 was to go to this page in KDE's bugzilla: + http://bugs.kde.org/query.cgi + and to create a search where + "Status and severity" / Status field is set to RESOLVED + and + "Involved People" / Email, bug-owner contains "jseward" + since I believe js...@ac... is the owner of all bugs. + This creates a long list of bugs which does not conveniently stop=20 + at the previous release. Work backwards through this list until + either (1) you run out of patience, or (2) most of the bugs seem + to pertain to previous releases and are now irrelevant. In short + this is not a very scientific or robust way to collect up all + bugs fixed since last time. =20 - Other files that might need updating: README, README_DEVELOPERS, README_PACKAGERS. |