Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Received-SPF: pass (nike.apache.org: local policy)
Date: Wed, 19 Mar 2008 20:27:48 +0100
From: Dyre Tjeldvoll <Dyre.Tjeldvoll@Sun.COM>
Subject: Re: beta build version
In-reply-to: <47E14EC8.5060504@sbcglobal.net>
Sender: Dyre.Tjeldvoll@Sun.COM
To: derby-dev@db.apache.org
Message-id: <47E16934.9070504@sun.com>
MIME-version: 1.0
Content-type: text/plain; format=flowed; charset=ISO-8859-1
Content-transfer-encoding: 7BIT
References: <47E14EC8.5060504@sbcglobal.net>
User-Agent: Thunderbird 2.0.0.12 (Windows/20080213)

Kathey Marsden wrote:
> I noticed the beta build version has an 'M'
> [C:\testcompat\jars\derby.jar] 10.4.1.0 beta - (637204M)
> [C:\testcompat\jars\derbytools.jar] 10.4.1.0 beta - (637204M)
> [C:\testcompat\jars\derbynet.jar] 10.4.1.0 beta - (637204M)
> [C:\testcompat\jars\derbyclient.jar] 10.4.1.0 beta - (637204M)
> ------------------------------------------------------
> not a big deal for beta, but for the release, it would be good to  make 
> sure all changes are checked
> in before the build.

Yes, I read this in the instructions for creating a release. I do think 
that the 'M' is there because I did not commit the changes I had made to 
releaseSummary.xml. I didn't want to do that because I felt it was 
rather unfinished (see the mail I sent about the feature descriptions).

On a related note: Should releaseSummary.xml be committed to trunk, and 
then merged to 10.4? In a way this seems unnecessary, since its content 
will only ever be needed on a specific branch, but the 10.3 content is 
currently found on trunk, so I guess it has been committed to trunk in 
the past...

Also: The release instructions seem to suggest that the CHANGES file was 
deprecated in 10.3, and that I shouldn't try to create it for 10.4. Is 
that understanding correct?


Dyre