commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From sebb <seb...@gmail.com>
Subject Re: POOL2 release plan
Date Fri, 04 May 2012 16:19:50 GMT
On 4 May 2012 17:11, Mark Thomas <markt@apache.org> wrote:
>
>
> sebb <sebbaz@gmail.com> wrote:
>
>>On 4 May 2012 14:06, Mark Thomas <markt@apache.org> wrote:
>>> On 13/04/2012 22:16, markt@apache.org wrote:
>>>> sebb <sebbaz@gmail.com> wrote:
>>>>
>>>>> On 12 April 2012 20:46, Mark Thomas <markt@apache.org> wrote:
>>>>>> 1. Fix all the open bugs. DONE
>>>>>> 2. Clean up the docs. DONE
>>>>>> 3. Release 2.0.0.M1
>>>
>>> I think we are ready for an alpha release of POOL2. I'm leaning
>>towards
>>> Alpha since I don't believe POOL2 is feature complete - specifically
>>I'm
>>> expecting to add some abandoned object tracking to POOL2.
>>
>>Does Alpha mean we don't guarantee binary compatibiity?
>
> Until we do a non-alpha/beta release I don't think we guarantee anything.
>
>>BTW, I'm seeing test errors on Win XP:
>>
>>Failed tests:
>> testMinIdle(org.apache.commons.pool2.impl.TestGenericKeyedObjectPool):
>>Should be 5 idle, found 0
>>testMinIdleMaxTotalPerKey(org.apache.commons.pool2.impl.TestGenericKeyedObjectPool):
>>Should be 5 idle, found 0
>>testConstructors(org.apache.commons.pool2.impl.TestGenericKeyedObjectPool):
>>expected:<0> but was:<1>
>
> OK. I'll take a look. I haven't run them in a few days and was expecting the CI to flag
up problems.

Continuum seems to be stuck; both Pool and VFS show as having active
builds, but there's nothing going on, and atttempts to schedule a
build fail.

I'll ping the builds list.

>>
>>Tests in error:
>>testConstructors(org.apache.commons.pool2.impl.TestGenericKeyedObjectPool):
>>factory may not be null
>>
>>The last one is probably a test bug, as the ctor specifically rejects
>>null factory.
>
> +1. I think I added that recently.
>
>>> The only stumbling block is I don't have the first clue how to do the
>>> release. Any pointers and/or offers of help.
>>
>>I can probably help with that.
>
> Excellent. Thanks.
>
> Mark
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org


Mime
View raw message