cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Reinhard Pötz <reinh...@apache.org>
Subject Is it necessary to increase the development version number (SNAPSHOT) after a release?
Date Wed, 06 Aug 2008 07:43:25 GMT
Grzegorz Kossakowski wrote:
> reinhard@apache.org pisze:
>> Author: reinhard
>> Date: Tue Aug  5 12:42:45 2008
>> New Revision: 682901
>>
>> URL: http://svn.apache.org/viewvc?rev=682901&view=rev
>> Log:
>> back in snapshot mode
>>
>> Modified:
>>     cocoon/trunk/tools/pom.xml
>>
>> Modified: cocoon/trunk/tools/pom.xml
>> URL: 
>> http://svn.apache.org/viewvc/cocoon/trunk/tools/pom.xml?rev=682901&r1=682900&r2=682901&view=diff

>>
>> ============================================================================== 
>>
>> --- cocoon/trunk/tools/pom.xml (original)
>> +++ cocoon/trunk/tools/pom.xml Tue Aug  5 12:42:45 2008
>> @@ -26,7 +26,7 @@
>>    <parent>
>>      <groupId>org.apache.cocoon</groupId>
>>      <artifactId>cocoon</artifactId>
>> -    <version>7</version>
>> +    <version>5-SNAPSHOT</version>
>>      <relativePath>../parent</relativePath>
> 
> Development version is lower than released one. Is it intended?

yes, I was too lazy to touch nearly every POM file in our repository 
just to increase the version number of our parent POMs. I haven't done 
this for the last release either and AFAICT, no problem occurred.

Does anybody know if it can cause problems if the development version 
number isn't increased after a release?

-- 
Reinhard Pötz                           Managing Director, {Indoqa} GmbH
                          http://www.indoqa.com/en/people/reinhard.poetz/

Member of the Apache Software Foundation
Apache Cocoon Committer, PMC member                  reinhard@apache.org
________________________________________________________________________

Mime
View raw message