|
From: <sv...@va...> - 2005-08-27 19:30:41
|
Author: njn Date: 2005-08-27 20:30:36 +0100 (Sat, 27 Aug 2005) New Revision: 4543 Log: Add .txt extensions to those files missing them, for consistency. Added: trunk/docs/internals/release-HOWTO.txt trunk/docs/internals/roadmap.txt Removed: trunk/docs/internals/release-HOWTO trunk/docs/internals/roadmap Modified: trunk/docs/internals/Makefile.am Modified: trunk/docs/internals/Makefile.am =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/Makefile.am 2005-08-27 18:00:21 UTC (rev 4542) +++ trunk/docs/internals/Makefile.am 2005-08-27 19:30:36 UTC (rev 4543) @@ -3,7 +3,7 @@ m_replacemalloc.txt \ m_syswrap.txt module-structure.txt notes.txt porting-HOWTO.txt \ porting-to-ARM.txt \ - release-HOWTO roadmap \ + release-HOWTO.txt roadmap.txt \ segments-seginfos.txt threads-syscalls-signals.txt \ tm-mutexstates.dot tm-threadstates.dot tracking-fn-entry-exit.txt \ xml-output.txt Deleted: 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-27 18:00:21 UTC (rev 4542) +++ trunk/docs/internals/release-HOWTO 2005-08-27 19:30:36 UTC (rev 4543) @@ -1,111 +0,0 @@ -------------------------------------------------------------------------= ----- -TODO list when doing a Valgrind release (with release number "X.Y.Z") -------------------------------------------------------------------------= ----- - -First of all: - -- Tell valgrind-developers you want to do a release. Give a timeframe f= or - everyone to check in any final features/bug-fixes they want in the - release. - -- Go over the docs, make sure they're up to date. - -- Update version number and date in docs/xml/vg-entities.xml. (Exact - release date probably won't be known yet, updating it is in the list b= elow - of tasks for the official release.) - -- Write release notes, add to NEWS. Include a list of fixed bugs from - 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. - -- Other files that might need updating: README, README_DEVELOPERS, - README_PACKAGERS. - -- Add X.Y.Z and X.Y.Z.SVN versions to Bugzilla (ask Dirk to do it) - -- If there are any binary incompatible tool API changes against the last - stable release, ensure that VG_CORE_INTERFACE_VERSION in - include/pub_tool_tooliface.h has been increased since the last release= . - - -For each release candidate (should do release candidates for big release= s, -bug-fix-only releases might not need one): - -- Do pre-release testing: - - Make sure regtests run ok on all platforms of interest. - - Make sure Mozilla and OpenOffice run ok on all platforms of interest= . - -- Change release number in AC_INIT() in configure.in to "X.Y.Z-rcN", whe= re - 'N' is the release candidate number. - -- Make the tarball ("make dist") and put it on the web somewhere (it doe= sn't - have to be on valgrind.org if another site is easier). - -- Ensure the tarball builds, runs, regtests on the platforms of interest= . - However redundant this seems, sometimes it can be that a from-the-repo - build works whereas a from-the-tarball one doesn't, usually due to som= e - trivial installation problem. - -- Announce the release: - - Email valgrind-users and valgrind-developers (but not valgrind-annou= nce). =20 - - Make clear it's a release candidate. =20 - - Make sure you tell everyone where to download from. - - Include the release notes in the email (maybe not necessary for rele= ase - candidates 2+). - -- Wait 2--3 days for feedback. If bugs appear: - - Fix them. - - Update the bug-fix list in NEWS if necessary. - - Do another release candidate. - - -For the official release: - -- Again, update date in docs/xml/vg-entities.xml for the official releas= e - date. - -- Do pre-release testing: - - Make sure regtests run ok on all platforms of interest. - - Make sure Mozilla and OpenOffice run ok on all platforms of interest= . - -- Change release number in AC_INIT() in configure.in to "X.Y.Z". - -- Make the tarball ("make dist"). - -- Check tarball builds, installs, regtests on platforms of interest. - If not, fix and repeat until success. - -- Tag the repository ("VALGRIND_X_Y_Z"). - =20 -- Update website:=20 - - Put the tarball up. - - Update the docs -- both the tarball'd docs, and the online-readable = docs. - - Update www.valgrind.org/downloads/source_code.html. =20 - - Update www.valgrind.org/downloads/archive.html. =20 - - Put the release notes at www.valgrind.org/info/release-notes-X.Y.Z.t= xt. - - Add a news item to the front page and also to valgrind.org/info/news= .html. - Include a link to the release notes. - - Update the "release-date" and "release-version" in php/.htconfx. - - Other pages that might need updating: devel/cvs_svn.html. - -- Change release number in AC_INIT() in configure.in to "X.Y.Z.SVN", whe= re - X.Y.Z is one more than the release just done. - -- Announce the release: - - Email valgrind-users, valgrind-developers, and valgrind-announce. - - Email Linux Weekly News. - - Include the release notes in the email. - -- Go on holiday. Copied: trunk/docs/internals/release-HOWTO.txt (from rev 4539, trunk/docs= /internals/release-HOWTO) Deleted: trunk/docs/internals/roadmap =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/roadmap 2005-08-27 18:00:21 UTC (rev 4542) +++ trunk/docs/internals/roadmap 2005-08-27 19:30:36 UTC (rev 4543) @@ -1,42 +0,0 @@ -=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=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D -Valgrind Roadmap -=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=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D - -This file serves as a rough roadmap for Valgrind development. It shows = a -minimal set of features we hope to implement for each version. It's in -reverse chronological order. - -------------------------------------------------------------------------= ----- -3.1.0 -------------------------------------------------------------------------= ----- -Scheduled for around November 2005. - -Definite --------- -* Get 32-bit and 64-bit programs working smoothly on AMD64 (Tom?). Seve= ral - levels of smoothness here, we should aim for at least level 3. - - 1. Be able to build a 32-bit valgrind on a 64-bit machine, so you can - build and install both, and manually choose between bin/valgrind an= d - bin64/valgrind. - 2. Build both automatically when installing. - 3. Choose the appropriate executable automatically at startup just fro= m - "valgrind". - 4. With --trace-children=3Dyes, allow 32-bit programs to exec 64-bit - programs and vice versa, and invoke the appropriate Valgrind - automatically. - -* Get PPC32 working usably with Memcheck (Julian). Has already improved= a - lot since. Get Cachegrind working with it (Nick). - -* Rewrite address space manager; statically link the core with - each tool; remove all glibc dependencies (Julian). - -Maybe ------ -* Get pthread modelling and Helgrind working again. Requires function - wrapping (Nick). - -* Reinstate Addrcheck and/or implement V-bit compression in Memcheck (?)= . - - Copied: trunk/docs/internals/roadmap.txt (from rev 4541, trunk/docs/inter= nals/roadmap) |