You are viewing a plain text version of this content. The canonical link for it is here.
Posted to test-commits@perl.apache.org by go...@apache.org on 2006/03/02 02:17:41 UTC
svn commit: r382226 - /perl/Apache-Test/trunk/RELEASE
Author: gozer
Date: Wed Mar 1 17:17:38 2006
New Revision: 382226
URL: http://svn.apache.org/viewcvs?rev=382226&view=rev
Log:
Followup change to geoff's r379805:
update replace command so it self-modifies
Modified:
perl/Apache-Test/trunk/RELEASE
Modified: perl/Apache-Test/trunk/RELEASE
URL: http://svn.apache.org/viewcvs/perl/Apache-Test/trunk/RELEASE?rev=382226&r1=382225&r2=382226&view=diff
==============================================================================
--- perl/Apache-Test/trunk/RELEASE (original)
+++ perl/Apache-Test/trunk/RELEASE Wed Mar 1 17:17:38 2006
@@ -60,7 +60,7 @@
5. Announce the package
a. post ... to the modperl, announce lists
- Subject: [ANNOUNCE] Apache-Test 1.30
+ Subject: [ANNOUNCE] Apache-Test 1.29
include
- MD5 sig (as it comes from CPAN upload announce).
- the latest Changes
@@ -72,15 +72,12 @@
b. edit ./Changes:
- start a new item with incremented version + '-dev'
- =item 1.31-dev
+ =item 1.30-dev
c. bump up version numbers in this file to make it easier to do the
next release.
- $ perl -pi -e 's/\.31/.32/g; s/\.30/\.31/g; s/\.29/\.30/g' RELEASE
-
- now reload this file and bump up the last number of the first
- command.
+ $ perl -pi -e 's/(\d+)\.(\d+)/join(".", $1, $2+1)/eg' RELEASE
d. commit Changes
- % svn ci -m "start 1.29-dev cycle" Changes RELEASE lib/Apache/Test.pm
+ % svn ci -m "start 1.30-dev cycle" Changes RELEASE lib/Apache/Test.pm
Re: svn commit: r382226 - /perl/Apache-Test/trunk/RELEASE
Posted by "Philippe M. Chiasson" <go...@ectoplasm.org>.
Geoffrey Young wrote:
>>+ $ perl -pi -e 's/(\d+)\.(\d+)/join(".", $1, $2+1)/eg' RELEASE
>
> aah, even better :)
It's all about lazyness ;-)
>> d. commit Changes
>>- % svn ci -m "start 1.29-dev cycle" Changes RELEASE lib/Apache/Test.pm
>>+ % svn ci -m "start 1.30-dev cycle" Changes RELEASE lib/Apache/Test.pm
>
> actually, I don't think you want to do this - the above command will
> increment this line so that it reads properly when it's time for this step.
I noticed that, but I just looked at mp2's RELEASE document, and it was worded
like that too. I guess it all depends on the particular habit of the RELEASE
manager. I just keep the file open while I release, and I don't reload it if
it has changed on disk.
Feel free to adjust to your preference ;-)
--------------------------------------------------------------------------------
Philippe M. Chiasson m/gozer\@(apache|cpan|ectoplasm)\.org/ GPG KeyID : 88C3A5A5
http://gozer.ectoplasm.org/ F9BF E0C2 480E 7680 1AE5 3631 CB32 A107 88C3A5A5
Re: svn commit: r382226 - /perl/Apache-Test/trunk/RELEASE
Posted by Geoffrey Young <ge...@modperlcookbook.org>.
> + $ perl -pi -e 's/(\d+)\.(\d+)/join(".", $1, $2+1)/eg' RELEASE
aah, even better :)
> d. commit Changes
> - % svn ci -m "start 1.29-dev cycle" Changes RELEASE lib/Apache/Test.pm
> + % svn ci -m "start 1.30-dev cycle" Changes RELEASE lib/Apache/Test.pm
actually, I don't think you want to do this - the above command will
increment this line so that it reads properly when it's time for this step.
--Geoff