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: pass (asf.osuosl.org: local policy)
Date: Mon, 11 Jul 2005 10:15:51 -0700
From: David Van Couvering <David.Vancouvering@Sun.COM>
Subject: Re: Client data source issues
In-reply-to: <42CDB1BB.2010404@debrunners.com>
To: Derby Development <derby-dev@db.apache.org>
Message-id: <42D2A947.6020607@sun.com>
MIME-version: 1.0
Content-type: text/plain; charset=us-ascii; format=flowed
Content-transfer-encoding: 7BIT
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.6)
 Gecko/20040113
References: <42CDAE16.9030001@apache.org> <42CDB1BB.2010404@debrunners.com>

Hi, Dan.  Can you describe in more detail the process you are proposing 
here?  It sounds like you are suggesting that when someone does a bug 
fix, it would be great if it were done in the 10.1 branch *and* the trunk?

Thanks,

David

Daniel John Debrunner wrote:

> Jeremy Boynes wrote:
> 
> 
>>There seem to be quite a few issues logged against the client
>>DataSource. Do we want to fix these before releasing 10.1?
>>
>>My thought is "no" but wanted to raise the issue.
> 
> 
> I agree with you, the ones Philip is working all have workarounds and
> the ones I'm finding are somewhat edge cases. I do think that once they
> are fixed they should be put into the 10.1 branch for future releases or
> to allow users to get fixed versions. I would like to see more bug fix
> activity on the 10.1 branch that occured on the 10.0 branch, to allow
> users to get a hold of bug fixes and to present Derby as more responsive
> to bugs.
> 
> Dan.
>