On 05/04/2011 20:05, Simone Tripodi wrote:
> Hi Phil,
> sorry if I'm late on it due to the [discovery] (I'd like to put an end
> at least to one thing I touch :P) but I would suggest following the
> Mark Thomas' suggestion:
>
> - move the current /trunk on a branch, something like POOL_2_FEATURE;
Hi Phil,
sorry if I'm late on it due to the [discovery] (I'd like to put an end
at least to one thing I touch :P) but I would suggest following the
Mark Thomas' suggestion:
- move the current /trunk on a branch, something like POOL_2_FEATURE;
- move the current POOL_1_X to /trunk;
- push the si
Hi Phil!
I'm at work now, but this evening at home I'll be able start taking
care of 0) and 1)!
Just for the record: time ago, in the commons-pool wiki page, I
reported some points we already discussed in the ML, I hope they can
help you for designing the roadmap.
Have a nice day!
Simo
http://pe
On 4/4/11 7:19 AM, Simone Tripodi wrote:
> Hi Phil,
> I think I can be helpful there, but I din't understand which steps are
> needed to get the trunk in a better order, I would be glad to fix it!
> Thanks in advance! :)
Thanks, Simo!
After cleaning up my local checkout, I see now that things are
Hi Phil,
I think I can be helpful there, but I din't understand which steps are
needed to get the trunk in a better order, I would be glad to fix it!
Thanks in advance! :)
Simo
http://people.apache.org/~simonetripodi/
http://www.99soft.org/
On Mon, Apr 4, 2011 at 4:08 PM, Phil Steitz wrote:
>
On 4/4/11 4:25 AM, sebb wrote:
> On 4 April 2011 07:36, Phil Steitz wrote:
>> I will be sending the 1.5.6 release announcement shortly. When
>> updating the pool website, I started by trying to use trunk, but
>> found the output confusing, since we are in process of changing the
>> groupId and pa
On 4 April 2011 07:36, Phil Steitz wrote:
> I will be sending the 1.5.6 release announcement shortly. When
> updating the pool website, I started by trying to use trunk, but
> found the output confusing, since we are in process of changing the
> groupId and package name. I decided, therefore, to
I will be sending the 1.5.6 release announcement shortly. When
updating the pool website, I started by trying to use trunk, but
found the output confusing, since we are in process of changing the
groupId and package name. I decided, therefore, to publish based on
the updated 1_5_X branch. Once w
