You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by Rick Hillegas <Ri...@Sun.COM> on 2006/09/21 16:58:00 UTC
almost ready to build the 10.2 release candidate
I think that we've wrapped up all of the outstanding issues except one:
1) Finish the scripts for injecting optional JDBC4 support into the 10.2
jarballs.
Andrew is bravely leading the charge here. He needs our help to test the
scripts on Solaris and Linux. Please pitch in if you can.
Please let us know if we need to do something else before building the
release. Otherwise, I plan to generate a release candidate as soon as
(1) is done.
Thanks,
-Rick
Re: almost ready to build the 10.2 release candidate
Posted by Army <qo...@gmail.com>.
Rick Hillegas wrote:
> Please let us know if we need to do something else before building the
> release. Otherwise, I plan to generate a release candidate as soon as
> (1) is done.
It looks like DERBY-1866 is a valid regression for 10.2 (see recent comments on
that issue). If we decide to release without a fix (a decision which I leave up
to the community), then perhaps there should be an explicit release note saying
that this is a 10.2 regression which has not been resolved in the release?
Either way I'm still looking into the issue and will post info/fix as soon as I
can. But in the meantime, just thought I'd mention it...
Army
Re: almost ready to build the 10.2 release candidate
Posted by Daniel John Debrunner <dj...@apache.org>.
Andrew McIntyre wrote:
> On 9/21/06, Rick Hillegas <Ri...@sun.com> wrote:
>
>> I think that we've wrapped up all of the outstanding issues except one:
>>
>> 1) Finish the scripts for injecting optional JDBC4 support into the 10.2
>> jarballs.
>>
>> Andrew is bravely leading the charge here. He needs our help to test the
>> scripts on Solaris and Linux. Please pitch in if you can.
>
>
> Yes, thanks Rick and John for the assistance in testing so far. I'll
> commit a couple of small changes and I'm set up to test on a Linux box
> now, so hopefully I can knock off any issues I see there today.
I see this script as "nice to have", not essential for a release of
Derby. It is posisble to Derby with JDBC 4.0 support from the sources
using the instructions in the source tree.
Just don't want to get into a situation where Derby 10.2 gets delayed
while this script becomes perfect. We could also just provide it on the
web-site or wiki directly. It is a short lived item.
Dan.
Re: almost ready to build the 10.2 release candidate
Posted by Andrew McIntyre <mc...@gmail.com>.
On 9/21/06, Rick Hillegas <Ri...@sun.com> wrote:
> I think that we've wrapped up all of the outstanding issues except one:
>
> 1) Finish the scripts for injecting optional JDBC4 support into the 10.2
> jarballs.
>
> Andrew is bravely leading the charge here. He needs our help to test the
> scripts on Solaris and Linux. Please pitch in if you can.
Yes, thanks Rick and John for the assistance in testing so far. I'll
commit a couple of small changes and I'm set up to test on a Linux box
now, so hopefully I can knock off any issues I see there today.
> Please let us know if we need to do something else before building the
> release. Otherwise, I plan to generate a release candidate as soon as
> (1) is done.
DERBY-1854 has been positively identified as a regression. Suresh has
assigned himself and produced a patch (thanks, Suresh!), so hopefully
that patch will be reviewed and go into the trunk and 10.2 before the
release (and 10.1 and 10.0 at some point as well).
I have some suggestions for the release notes as well, which I'll post
as a patch to DERBY-1860.
andrew
Re: almost ready to build the 10.2 release candidate
Posted by Rick Hillegas <Ri...@Sun.COM>.
Jean T. Anderson wrote:
>Rick Hillegas wrote:
>
>
>>Thanks to everyone for responding to my first post. At this point I am
>>inclined to do the following:
>>
>>A) Hold up the release until DERBY-1854 commits.
>>
>>B) Regard the JDBC4-injection scripts as a stretch goal. If they aren't
>>finished by the time DERBY-1854 commits, then the release notes can just
>>say "build JDBC4 the old fashioned way or consult the website for
>>instructions on how to obtain and run the injection scripts."
>>
>>
>
>A very minor suggestion: rather than "consult the website", I'd suggest
>"consult the Derby Wiki at http://wiki.apache.org/db-derby/".
>
>I think it'd work best to have those instructions in a place that can be
>swiftly tweaked as needed.
>
>
>
Thanks, Jean. This sounds better.
Regards,
-Rick
> -jean
>
>
>
>>Please let me know if this is not acceptable or if something else should
>>gate the building of a release candidate.
>>
>>
Re: almost ready to build the 10.2 release candidate
Posted by "Jean T. Anderson" <jt...@bristowhill.com>.
Rick Hillegas wrote:
> Thanks to everyone for responding to my first post. At this point I am
> inclined to do the following:
>
> A) Hold up the release until DERBY-1854 commits.
>
> B) Regard the JDBC4-injection scripts as a stretch goal. If they aren't
> finished by the time DERBY-1854 commits, then the release notes can just
> say "build JDBC4 the old fashioned way or consult the website for
> instructions on how to obtain and run the injection scripts."
A very minor suggestion: rather than "consult the website", I'd suggest
"consult the Derby Wiki at http://wiki.apache.org/db-derby/".
I think it'd work best to have those instructions in a place that can be
swiftly tweaked as needed.
-jean
> Please let me know if this is not acceptable or if something else should
> gate the building of a release candidate.
Re: almost ready to build the 10.2 release candidate
Posted by Rick Hillegas <Ri...@Sun.COM>.
Daniel John Debrunner wrote:
> Rick Hillegas wrote:
>
>>> Rick wrote on 9/18.
>>>
>>>> I plan to do one more mega-merge just before building the RC.
>>>
>>>
>>>
>>> Did this merge happen, or will it happen? The wiki page doesn't seem
>>> to have the latest merge information. Which svn revision is the 10.2
>>> branch caught up to from the trunk?
>>
>>
>> Thanks for pointing this out. I updated the wiki to note that bulk
>> merges also happened on September 8 and September 15 and that the
>> 10.2 branch has caught up to revision 446673. I have not mega-merged
>> since last Friday.
>
>
> So I assume that plan is still to do one more mega-merge.
>
> Thanks,
> Dan.
>
Hi Dan,
Yes, that's what I'm planning to do.
Regards,
-Rick
Re: almost ready to build the 10.2 release candidate
Posted by Daniel John Debrunner <dj...@apache.org>.
Rick Hillegas wrote:
>> Rick wrote on 9/18.
>>
>>> I plan to do one more mega-merge just before building the RC.
>>
>>
>> Did this merge happen, or will it happen? The wiki page doesn't seem
>> to have the latest merge information. Which svn revision is the 10.2
>> branch caught up to from the trunk?
>
> Thanks for pointing this out. I updated the wiki to note that bulk
> merges also happened on September 8 and September 15 and that the 10.2
> branch has caught up to revision 446673. I have not mega-merged since
> last Friday.
So I assume that plan is still to do one more mega-merge.
Thanks,
Dan.
Re: almost ready to build the 10.2 release candidate
Posted by Rick Hillegas <Ri...@Sun.COM>.
Daniel John Debrunner wrote:
>
>
> Rick Hillegas wrote (today):
>
>> Thanks to everyone for responding to my first post. At this point I
>> am inclined to do the following:
>>
>> A) Hold up the release until DERBY-1854 commits.
>>
>> B) Regard the JDBC4-injection scripts as a stretch goal. If they
>> aren't finished by the time DERBY-1854 commits, then the release
>> notes can just say "build JDBC4 the old fashioned way or consult the
>> website for instructions on how to obtain and run the injection
>> scripts."
>>
>> Please let me know if this is not acceptable or if something else
>> should gate the building of a release candidate.
>
>
> Rick wrote on 9/18.
>
>> I plan to do one more mega-merge just before building the RC.
>
>
> Did this merge happen, or will it happen? The wiki page doesn't seem
> to have the latest merge information. Which svn revision is the 10.2
> branch caught up to from the trunk?
Thanks for pointing this out. I updated the wiki to note that bulk
merges also happened on September 8 and September 15 and that the 10.2
branch has caught up to revision 446673. I have not mega-merged since
last Friday.
>
> Thanks,
> Dan.
>
>
Re: almost ready to build the 10.2 release candidate
Posted by Daniel John Debrunner <dj...@apache.org>.
Rick Hillegas wrote (today):
> Thanks to everyone for responding to my first post. At this point I am
> inclined to do the following:
>
> A) Hold up the release until DERBY-1854 commits.
>
> B) Regard the JDBC4-injection scripts as a stretch goal. If they aren't
> finished by the time DERBY-1854 commits, then the release notes can just
> say "build JDBC4 the old fashioned way or consult the website for
> instructions on how to obtain and run the injection scripts."
>
> Please let me know if this is not acceptable or if something else should
> gate the building of a release candidate.
Rick wrote on 9/18.
> I plan to do one more mega-merge just before building the RC.
Did this merge happen, or will it happen? The wiki page doesn't seem to
have the latest merge information. Which svn revision is the 10.2 branch
caught up to from the trunk?
Thanks,
Dan.
Re: almost ready to build the 10.2 release candidate
Posted by Rick Hillegas <Ri...@Sun.COM>.
Thanks to everyone for responding to my first post. At this point I am
inclined to do the following:
A) Hold up the release until DERBY-1854 commits.
B) Regard the JDBC4-injection scripts as a stretch goal. If they aren't
finished by the time DERBY-1854 commits, then the release notes can just
say "build JDBC4 the old fashioned way or consult the website for
instructions on how to obtain and run the injection scripts."
Please let me know if this is not acceptable or if something else should
gate the building of a release candidate.
Regards,
-Rick
Rick Hillegas wrote:
> I think that we've wrapped up all of the outstanding issues except one:
>
> 1) Finish the scripts for injecting optional JDBC4 support into the
> 10.2 jarballs.
>
> Andrew is bravely leading the charge here. He needs our help to test
> the scripts on Solaris and Linux. Please pitch in if you can.
>
> Please let us know if we need to do something else before building the
> release. Otherwise, I plan to generate a release candidate as soon as
> (1) is done.
>
> Thanks,
> -Rick