Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Derby Development" <derby-dev@db.apache.org>
Received-SPF: neutral (hermes.apache.org: local policy)
Message-ID: <4293B41F.4050600@sbcglobal.net>
Date: Tue, 24 May 2005 16:09:19 -0700
From: Army <qozinx@sbcglobal.net>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US;
 rv:1.7.1) Gecko/20040707
MIME-Version: 1.0
To: Derby Development <derby-dev@db.apache.org>
Subject: Re: Planning for a 10.1 release
References: <54ac72d705051719171a779686@mail.gmail.com> <42935A7F.400@sun.com>
 <54ac72d705052415473ee5eb7f@mail.gmail.com>
In-Reply-To: <54ac72d705052415473ee5eb7f@mail.gmail.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit

Andrew McIntyre wrote:
> - Scanning through the list, I noticed Army mentioned basic XML
> support. Army, any estimate on when this might be contributed? Or is
> this for a future release?

I'm hoping to submit this support sometime later tonight or tomorrow.  But that 
said, I do _NOT_ think we want to officially include XML support in this 
release.  It's an entirely new feature that adds a good amount of code, and some 
of it is based on SQL/XML standards that aren't yet solidified (they're in 
working draft only).

I imagine it will take some time to get a thorough review, and I also imagine 
that there are things I'll have to change in response to people's feedback.  If 
your suggesting a release in the next two weeks, that seems too risky to me.

I _do_ think it'd be good to get the support into the trunk codeline soon so 
that people can play with it and make comments--but I think it should remain 
undocumented and strictly unofficial until a later release.  I.e. maybe it goes 
into the release jars, but we don't document the release as having official XML 
support...is that possible/desirable?  If not, then I guess it'd be best to wait 
until after the release is cut before submitting to the trunk...

Does that make sense?
Army