commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michael A. Smith" <...@apache.org>
Subject Re: [collections] project.xml and versionning Was: cvs commit: jakarta-commons/collections project.xml
Date Sun, 27 Oct 2002 14:25:28 GMT
done.

regards,
michael


Martin van den Bemt wrote:
> Make it 2.2-dev and change it to 3.0 if the changes ask for a new major
> release number. 
> So +1 ;)
> Shall I change it ?
> 
> Mvgr,
> Martin
> 
> On Sat, 2002-10-26 at 23:45, Henri Yandell wrote:
> 
>>Yeah, project.xml is important to update. I don't think it goes into the
>>collections-src release, so it's only important to make sure the one in
>>cvs outputs the right version number.
>>
>>Seems we're mainly looking at 2 questions:
>>
>>1) Should the project.xml represent the next builder. ie) 2.2 or 3.0.
>>2) Should it include a -dev.
>>
>>I'm +1 on both. I say we call it 2.2-dev. Or 2.2-SNAPSHOT if we want that
>>functionality by default.
>>
>>We also probably need to consider upgrading the release-howto on the
>>website to mention that project.xml needs upgrading, for collections and
>>for other projects.
>>
>>Hen
>>
>>On Sat, 26 Oct 2002, Steve Downey wrote:
>>
>>
>>>The difference, to me at least, is that project.xml is machine readable. That
>>>version number can end up in all sorts of places. My concern is
>>>distinguishing a genuine release from a development or nightly build.
>>>
>>>In theory that's pretty easy, but in practice, someone always forgets. A
>>>nightly release is promoted into QA in order to test a fix for a bug, and
>>>then no one remembers when and where it came from. And then we go through a
>>>cycle of the gee it works for me game.
>>>
>>>Right now 'maven dist' builds 'commons-collections-2.1.jar', and packages it
>>>into 'commons-collections-2.1.tar.gz' and so forth.
>>>
>>>On Saturday 26 October 2002 02:24 pm, Henri Yandell wrote:
>>>
>>>>only one was me sticking ClassMap in, which needs me to do some doccing on
>>>>it to explain it further, and possibly modify its lookup algorithm.
>>>>
>>>>The STATUS.html [I think it's that] has a 'Next Release' bit that I left
>>>>as '?' when doing the last release. Figuring out what the next release is
>>>>will involve updating that :)
>>>>
>>>>Hen
>>>>
>>>>On 26 Oct 2002, Martin van den Bemt wrote:
>>>>
>>>>>If you know what the next release is going to be named ;)
>>>>>
>>>>>Mvgr,
>>>>>Martin
>>>>>
>>>>>On Sat, 2002-10-26 at 18:39, Steve Downey wrote:
>>>>>
>>>>>>Shouldn't it be 2.2, or 2.1-dev, or 2.2-dev? Whatever it is, the result
>>>>>>of building it now isn't the 2.1 release.
>>>>>>[OK, so it might be. I don't think there have been any checkins since
>>>>>>release]
>>>>>>
>>>>>>On Saturday 26 October 2002 07:04 am, mvdb@apache.org wrote:
>>>>>>
>>>>>>>mvdb        2002/10/26 04:04:46
>>>>>>>
>>>>>>>  Modified:    collections project.xml
>>>>>>>  Log:
>>>>>>>  Updated the version in project.xml.
>>>>>>>  Thanx Moritz Petersen for pointing us to that.
>>>>>>>
>>>>>>>  Revision  Changes    Path
>>>>>>>  1.6       +1 -1      jakarta-commons/collections/project.xml
>>>>>>>
>>>>>>>  Index: project.xml
>>>>>>>  ===================================================================
>>>>>>>  RCS file: /home/cvs/jakarta-commons/collections/project.xml,v
>>>>>>>  retrieving revision 1.5
>>>>>>>  retrieving revision 1.6
>>>>>>>  diff -u -r1.5 -r1.6
>>>>>>>  --- project.xml	14 Sep 2002 02:17:18 -0000	1.5
>>>>>>>  +++ project.xml	26 Oct 2002 11:04:46 -0000	1.6
>>>>>>>  @@ -4,7 +4,7 @@
>>>>>>>     <extend>../project.xml</extend>
>>>>>>>     <name>Collections</name>
>>>>>>>     <id>commons-collections</id>
>>>>>>>  -  <currentVersion>2.0</currentVersion>
>>>>>>>  +  <currentVersion>2.1</currentVersion>
>>>>>>>     <inceptionYear>2002</inceptionYear>
>>>>>>>     <gumpRepositoryId>jakarta</gumpRepositoryId>
>>>>>>>     <shortDescription>Commons Collections</shortDescription>

-- 
Michael A. Smith
mas@apache.org



--
To unsubscribe, e-mail:   <mailto:commons-dev-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: <mailto:commons-dev-help@jakarta.apache.org>


Mime
View raw message