beta build version

[Kathey Marsden <km...@sbcglobal.net>]

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.

Kathey

Re: beta build version

[Myrna van Lunteren <m....@gmail.com>]

On 3/19/08, Rick Hillegas <Ri...@sun.com> wrote:
> > 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?
> The release instructions certainly treat CHANGES as a deprecated file.
> Maybe Myrna or Kathey can shed some light on this issue.
>
> Regards,
> -Rick
> >
> >
> > Dyre
>
During the initial 10.3 process I looked at what was in the 10.2
'CHANGES' file (note: not 'CHANGES.html') and it was fairly identical
to what was in the release notes.
There was a discussion about it and I think I concluded
'RELEASE-NOTES.html' was enough.
I think part of this discussion is maybe in this thread:
http://www.nabble.com/Release-Notes-to5931299.html

However, subsequently, there was discussion to the effect that we
should not have all changes in the Release Notes, instead, we should
only have those affecting (end-)users. Thus the 'CHANGES.html' file
was born, listing (also, I think) changes not visible to end-users.

Part of the discussion can be followed in this thread:
http://www.nabble.com/10.3-Release-Notes-to11502532.html#a11502532

In my edits of the wiki I left a reference to 'CHANGES' - not
'CHANGES.html' - for the possibility we'd pull another release off the
10.2 branch. I agree the name is confusing. But what better name for a
file to list the changes? It's unlikely now that we'll pull another
release off 10.2, probably better to remove reference to the 10.2
'CHANGES' file and only mention 'CHANGES.html'.

HTH...
Myrna

Re: beta build version

[Rick Hillegas <Ri...@Sun.COM>]

Dyre Tjeldvoll wrote:
> 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...
Hi Dyre,

I don't see any reason to commit releaseSummary.xml to the trunk.
>
> 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?
The release instructions certainly treat CHANGES as a deprecated file. 
Maybe Myrna or Kathey can shed some light on this issue.

Regards,
-Rick
>
>
> Dyre

Re: beta build version

[Dyre Tjeldvoll <Dy...@Sun.COM>]

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