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...@oracle.com> on 2013/04/08 21:50:45 UTC
10.10.1 polls closing in a few hours
If you plan to vote, please do so. If you want me to keep the polls open
for another week, please let me know soon.
Thanks,
-Rick
Re: 10.10.1 polls closing in a few hours
Posted by Katherine Marsden <km...@sbcglobal.net>.
On 4/8/2013 2:09 PM, Mike Matrigali wrote:
> I would like polls to stay open for another week also, to better
> understand the existing 10.10 regressions. Also it would be great if
> we got some compatibility testing in before the vote, as once those
> errors are in a release it is hard to recover from them.
>
I will keep working on compatibility evaluation in the coming week and
file Jira issues for what I find as I hit it, whether or not there is a
release today.
Re: 10.10.1 polls closing in a few hours
Posted by Mike Matrigali <mi...@sbcglobal.net>.
On 4/8/2013 1:17 PM, Katherine Marsden wrote:
> On 4/8/2013 12:50 PM, Rick Hillegas wrote:
>> If you plan to vote, please do so. If you want me to keep the polls
>> open for another week, please let me know soon.
>>
> I think I would like it to stay open another week or until we understad
> DERBY-6092. Even if it ends up to be a java bug that was triggered by a
> Derby code change, we might need to put a work around in the code if it
> has manifested itself as a functional regression.
>
>
>
I would like polls to stay open for another week also, to better
understand the existing 10.10 regressions. Also it would be great if
we got some compatibility testing in before the vote, as once those
errors are in a release it is hard to recover from them.
/mikem
Re: 10.10.1 polls closing in a few hours
Posted by Katherine Marsden <km...@sbcglobal.net>.
On 4/8/2013 12:50 PM, Rick Hillegas wrote:
> If you plan to vote, please do so. If you want me to keep the polls
> open for another week, please let me know soon.
>
I think I would like it to stay open another week or until we understad
DERBY-6092. Even if it ends up to be a java bug that was triggered by a
Derby code change, we might need to put a work around in the code if it
has manifested itself as a functional regression.