develooper Front page | perl.cvs.parrot | Postings from December 2008

[svn:parrot] r33738 - in trunk: docs/project tools/util

December 9, 2008 18:08
[svn:parrot] r33738 - in trunk: docs/project tools/util
Message ID:
Author: coke
Date: Tue Dec  9 18:07:45 2008
New Revision: 33738


Stop opening RTs; use trac's milestone instead.
Also, some untested updates to the release verbage JSON templates. Whiteknight++  beware!

Modified: trunk/docs/project/release_manager_guide.pod
--- trunk/docs/project/release_manager_guide.pod	(original)
+++ trunk/docs/project/release_manager_guide.pod	Tue Dec  9 18:07:45 2008
@@ -85,16 +85,6 @@
 Enter the date of the Saturday before the next release.
-=item C<rt.tracking>
-Create a new RT-ticket for the next release.
-Please use the release month in the ticket, and *do not*
-use the release number. Releases are date-based, while release numbers are
-feature-based. Project team members agree on the release number near the
-actual release, based on the features available in trunk at the time.
-Mark the ticket for the next release as dependent on the current release. 
-Change the URL fragment in rt.tracking to use the number of the ticket for the next release.
 =item C<wiki.bugday>
 Update the date part of the link to the wiki page for the next bugday.

Modified: trunk/tools/util/release.json
--- trunk/tools/util/release.json	(original)
+++ trunk/tools/util/release.json	Tue Dec  9 18:07:45 2008
@@ -13,9 +13,6 @@
     ""       : "Saturday",
     ""      : "13 Dec 2008",
-    "rt.root"          : "",
-    "rt.tracking"      : "Ticket/Display.html?id=60656",
     "wiki.root"        : "",
     "wiki.bugday"      : "bug_day_2008_12_13",

Modified: trunk/tools/util/templates.json
--- trunk/tools/util/templates.json	(original)
+++ trunk/tools/util/templates.json	Tue Dec  9 18:07:45 2008
@@ -59,20 +59,20 @@
 No experience with parrot necessary.
 --From: @wiki.root@@wiki.bugday@--
-There's a milestone ticket here:
+Check the list at:
-Which contains all the tickets I'd like to see resolved in @version@. If
-you just want to view the unresolved tickets, you can use this saved
+Which contains all the tickets I'd like to see resolved in @version@. To
+see all the open tickets, use:
 If you've got something you're working on that you think you'll be
 getting done before the release, please
 - add a ticket for it (if necessary);
-- add it as a dependency for this ticket
+- set its milestone to this release.
 Thanks in advance for your patches and commits. ^_^ Perl Programming lists via nntp and http.
Comments to Ask Bjørn Hansen at | Group listing | About