David,
I know that Elliot is close to a solution for PLUTO-233, which I think is the biggest outstanding Pluto 1.1 bug. It would be good to get that one bagged for beta2.
/Craig
-----"David H. DeWolf" <[EMAIL PROTECTED]> wrote: -----
To: [email protected]
From: "David H. DeWolf" <[EMAIL PROTECTED]>
Sent by: "David H. DeWolf" <[EMAIL PROTECTED]>
Date: 09/10/2006 12:00AM
Subject: Re: 1.1.0-beta2 release
Let's target a release for next weekend. I'll plan to tag on Friday
night unless someone speaks up. I'll cut the release over the weekend.
Sound good?
David
Charles Severance wrote:
> Will we make a tag that is a beta2 release candidate *before* we just
> make the beta2 artifacts?
>
> /Chuck
>
> On Sep 6, 2006, at 1:16 PM, David H. DeWolf wrote:
>
>>
>> 1) Starting now you can help test the most recent fixes by
>> using/developing against the trunk.
>>
>> 2) Watch the dev list. Once the test builds are done for the release
>> they will be posted and testing will be requested.
>>
>> David
>>
>> Charles Severance wrote:
>>> How can a person test this before it goes out? How can I help?
>>> /Chuck
>>> On Sep 5, 2006, at 7:06 PM, David H. DeWolf wrote:
>>>> that's my plan :)
>>>>
>>>> David
>>>>
>>>> Carsten Ziegeler wrote:
>>>>> David H. DeWolf schrieb:
>>>>>> Release early, release often!
>>>>>>
>>>>>> We've had a bit of activity lately, specifically around bug fixes
>>>>>> to beta1. What people working on that they'd like to get in
>>>>>> before beta2?
>>>>>>
>>>>>> I'd like to cut a release within the next 2 weeks and should have
>>>>>> the time to help out. Thoughts?
>>>>>>
>>>>> Big +1 for a b2 release; especially if we release the stuff to a maven
>>>>> repository as well!
>>>>> Carsten
>>>>
>>>>
>>
>>
>
>
