Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Received-SPF: error (idunn.apache.osuosl.org: domain Sun.COM from
 192.18.42.249 cause and error)
Date: Thu, 21 Sep 2006 13:30:03 -0700
From: Rick Hillegas <Richard.Hillegas@Sun.COM>
Subject: Re: almost ready to build the 10.2 release candidate
In-reply-to: <4512A878.1060302@sun.com>
Sender: Richard.Hillegas@Sun.COM
To: derby-dev@db.apache.org
Message-id: <4512F64B.6030809@sun.com>
MIME-version: 1.0
Content-type: text/plain; format=flowed; charset=ISO-8859-1
Content-transfer-encoding: 7BIT
References: <4512A878.1060302@sun.com>
User-Agent: Mozilla Thunderbird 1.0.6 (Windows/20050716)

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