On Fri, May 4, 2012 at 12:05 PM, sebb wrote:
>
> BTW, I'm seeing test errors on Win XP:
>
Yeah, but who runs Win XP? ;)
I'm just having a bit of fun on Star Wars Day, not trying to start a flame war.
-
To unsubscribe, e-mail: d
On 4 May 2012 17:11, Mark Thomas wrote:
>
>
> sebb wrote:
>
>>On 4 May 2012 14:06, Mark Thomas wrote:
>>> On 13/04/2012 22:16, ma...@apache.org wrote:
sebb wrote:
> On 12 April 2012 20:46, Mark Thomas wrote:
>> 1. Fix all the open bugs. DONE
>> 2. Clean up the docs. DONE
sebb wrote:
>On 4 May 2012 14:06, Mark Thomas wrote:
>> On 13/04/2012 22:16, ma...@apache.org wrote:
>>> sebb wrote:
>>>
On 12 April 2012 20:46, Mark Thomas 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
On 4 May 2012 14:06, Mark Thomas wrote:
> On 13/04/2012 22:16, ma...@apache.org wrote:
>> sebb wrote:
>>
>>> On 12 April 2012 20:46, Mark Thomas 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 PO
On 13/04/2012 22:16, ma...@apache.org wrote:
> sebb wrote:
>
>> On 12 April 2012 20:46, Mark Thomas 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 believ
sebb wrote:
>On 12 April 2012 20:46, Mark Thomas wrote:
>> 1. Fix all the open bugs. DONE - until someone opens another Jira ;)
>> 2. Clean up the docs. TODO
>> 3. Release 2.0.0.M1
>> 4. Work on DBCP2, updating POOL2 as required (e.g. moving the
>abandoned
>> object code to POOL2)
>> 5. React to
Gary Gregory wrote:
>I do not recall releasing M milestone versions in the past. I know
>Eclipse uses milestones but the concept here feels more like an alpha
>or beta. You could call a -snapshot past a certain date or an RC a
>milestone I suppose.
I'm happy will alpha at this point if that is w
On 12 April 2012 20:46, Mark Thomas wrote:
> 1. Fix all the open bugs. DONE - until someone opens another Jira ;)
> 2. Clean up the docs. TODO
> 3. Release 2.0.0.M1
> 4. Work on DBCP2, updating POOL2 as required (e.g. moving the abandoned
> object code to POOL2)
> 5. React to feedback on 2.0.0.M1
I do not recall releasing M milestone versions in the past. I know
Eclipse uses milestones but the concept here feels more like an alpha
or beta. You could call a -snapshot past a certain date or an RC a
milestone I suppose. Can we just sync up pool and dbcp on their
respective trunks?
I could see
1. Fix all the open bugs. DONE - until someone opens another Jira ;)
2. Clean up the docs. TODO
3. Release 2.0.0.M1
4. Work on DBCP2, updating POOL2 as required (e.g. moving the abandoned
object code to POOL2)
5. React to feedback on 2.0.0.M1
6. Release 2.0.0.Mn as required
7. Release 2.0.0
Though
10 matches
Mail list logo