svn commit: r419325 - /perl/Apache-SizeLimit/trunk/RELEASE

[pg...@apache.org]

Author: pgollucci
Date: Wed Jul  5 13:20:10 2006
New Revision: 419325

URL: http://svn.apache.org/viewvc?rev=419325&view=rev
Log:
after .9 make the next one 1.0


Modified:
    perl/Apache-SizeLimit/trunk/RELEASE

Modified: perl/Apache-SizeLimit/trunk/RELEASE
URL: http://svn.apache.org/viewvc/perl/Apache-SizeLimit/trunk/RELEASE?rev=419325&r1=419324&r2=419325&view=diff
==============================================================================
--- perl/Apache-SizeLimit/trunk/RELEASE (original)
+++ perl/Apache-SizeLimit/trunk/RELEASE Wed Jul  5 13:20:10 2006
@@ -70,7 +70,7 @@
   b. edit ./Changes:
      - start a new item with incremented version + '-dev'
 
-  =item 0.10-dev
+  =item 1.0-dev
 
   c. bump up version numbers in this file to make it easier to do the
      next release.
@@ -78,4 +78,4 @@
      $ perl -pi -e 's/(\d+)\.(\d+)/join(".", $1, $2+1)/eg' RELEASE
 
   d. commit Changes
-     % svn ci -m "start 0.10-dev cycle" Changes RELEASE lib/Apache/SizeLimit.pm
+     % svn ci -m "start 1.0-dev cycle" Changes RELEASE lib/Apache/SizeLimit.pm

Re: svn commit: r419325 - /perl/Apache-SizeLimit/trunk/RELEASE

[Geoffrey Young <ge...@modperlcookbook.org>]

pgollucci@apache.org wrote:
> Author: pgollucci
> Date: Wed Jul  5 13:20:10 2006
> New Revision: 419325
> 
> URL: http://svn.apache.org/viewvc?rev=419325&view=rev
> Log:
> after .9 make the next one 1.0

ok, the first one was because I'm bad at math.  but how about we
prepopulate with .91 instead of pre-declaring that the next release will
automatically become an official 1.0?  I'm fine if that's the case, but
the development cycle should dictate a 1.0 release, not an automatic
version bump scheme.

--Geoff

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@perl.apache.org
For additional commands, e-mail: dev-help@perl.apache.org