db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "TomohitoNakayama" <tomon...@basil.ocn.ne.jp>
Subject Re: 10.1.2 Release status page
Date Tue, 27 Sep 2005 09:56:25 GMT
Hello.

I may misunderstand the version number scheme ....

The fourth digit of the first release for first version of specified third digit is not always
"1" ?
If rc2 was failed and rc3 was passed in Dan's example , version number of released program
is 10.1.2.2 ?

I thought fourth digit of the first release forfirst version of specified third digit  is
always "1"....

Best regards .

/*

         Tomohito Nakayama
         tomonaka@basil.ocn.ne.jp
         tomohito@rose.zero.ad.jp
         tmnk@apache.org

         Naka
         http://www5.ocn.ne.jp/~tomohito/TopPage.html

*/
----- Original Message ----- 
From: "Kathey Marsden" <kmarsdenderby@sbcglobal.net>
To: "Derby Development" <derby-dev@db.apache.org>
Sent: Tuesday, September 27, 2005 6:17 AM
Subject: Re: 10.1.2 Release status page


> TomohitoNakayama wrote:
> 
>> Hello.
>>
>> I feel it strange that version number was decreased between rc-X and
>> released version ......
>>
> I don't think we ever decrease the version.  In Dan's example "10.1.2.2
> bumped after rc2"   means that  the version on the branch was bumped
> after  rc2 was made and  is done in preparation for the next release.
> rc2 was version 10.1.2.1 and would be released as is if accepted  as the
> official release.
> 
>> I think fourth (really meant third)  version number should be
>> increased when program was officialy released , because rc-X is not
>> yet program of the version officialy acknowledged .
>>
> 
> In general we bump the version when the work begins, so for example we
> bumped the trunk to 10.2 right after 10.1 branched to mark that the
> version as shown by sysinfo is 10.2 work under progress. 
> 
> If the last digit indicates an  external release of jars (snapshot,
> release candidate, or release), then we bump it right after each post to
> the website, to indicate we are working on the next external release.
> 
> Since our third digit represents only that this is a bug fix release and
> more testing has been done, then it makes sense to me bump it just
> before the release candidate is made to mark the beginning of testing. 
> 
> 
> Kathey
> 
>>>
>>> For a branch I would say (using 10.1 as an example)
>>>
>>> - bump fourth digit at least after every snapshot, release candidate or
>>> release
>>> - bump third digit for the first candidate of a release
>>>
>>> 10.1.1.0 Initial release
>>> 10.1.1.1 bumped after release
>>> 10.1.1.2 bumped after snapshot (of 10.1.1.1)
>>> 10.1.1.3 bumped after snapshot (of 10.1.1.2)
>>> 10.1.2.0 release candicate one for 10.1.2
>>> 10.1.2.1 bumped after rc1
>>> rc1 goes for voting, some issues & fixes made to the branch
>>> 10.1.2.1 release candicate two for 10.1.2
>>> 10.1.2.2 bumped after rc2
>>> rc2 accepted as official 10.1.2 release, its version is 10.1.2.1
>>>
>>> (and similar release candidate version changes could happen on the
>>> intiial release, but I matched what is in 10.1 at the moment).
>>>
>>> Dan.
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>> -- 
>>> No virus found in this incoming message.
>>> Checked by AVG Anti-Virus.
>>> Version: 7.0.344 / Virus Database: 267.11.3/107 - Release Date:
>>> 2005/09/20
>>>
>>
>>
> 
> 
> 
> 
> 
> -- 
> No virus found in this incoming message.
> Checked by AVG Anti-Virus.
> Version: 7.0.344 / Virus Database: 267.11.6/111 - Release Date: 2005/09/23
>


-- 
No virus found in this outgoing message.
Checked by AVG Anti-Virus.
Version: 7.0.344 / Virus Database: 267.11.7/112 - Release Date: 2005/09/26


Mime
View raw message