I've committed a fix for the final blocker JIRA (WHIRR-91) against
whirr 0.2.0. I'll work on creating a release candidate.

Patrick

On Sat, Oct 30, 2010 at 4:28 PM, Tom White <[email protected]> wrote:
> Feel free to take a look at it.
>
> Thanks!
> Tom
>
> On Sat, Oct 30, 2010 at 4:11 PM, Patrick Hunt <[email protected]> wrote:
>> Tom were you still planning to do 91? If not lmk and I'll take a stab
>> at it. I'd like to get an RC built asap.
>>
>> Thanks,
>>
>> Patrick
>>
>> On Wed, Oct 27, 2010 at 2:30 PM, Patrick Hunt <[email protected]> wrote:
>>> On Wed, Oct 27, 2010 at 1:24 PM, Tom White <[email protected]> wrote:
>>>> Do you think WHIRR-116 is a blocker too?
>>>
>>> I don't think so given the docs are available in the releases
>>> themselves. Would be nice to have at some point though.
>>>
>>> I do notice that it's
>>> http://incubator.apache.org/whirr/quick-start-guide.html
>>> rather than say whirr/docs/current/... which would facilitate having
>>> multiple versions under docs with current being a symbolic link to the
>>> most recent stable release docs. I'll update the jira.
>>>
>>> Patrick
>>>
>>>>>
>>>>> Patrick
>>>>>
>>>>> On Wed, Oct 27, 2010 at 11:58 AM, Tom White <[email protected]> wrote:
>>>>>> +1
>>>>>>
>>>>>> Thanks for volunteering to be the release manager!
>>>>>>
>>>>>> It would be nice to fix all four, but I agree that only WHIRR-91 is a 
>>>>>> blocker.
>>>>>>
>>>>>> Cheers,
>>>>>> Tom
>>>>>>
>>>>>> On Wed, Oct 27, 2010 at 10:32 AM, Patrick Hunt <[email protected]> 
>>>>>> wrote:
>>>>>>> Hi Folks, do you think it's a good time for a 0.2.0 release? 21 issues
>>>>>>> fixed so far, 4 open. Only one of those seems like it would be good to
>>>>>>> fix before 0.2.0
>>>>>>> https://issues.apache.org/jira/browse/WHIRR-91
>>>>>>>
>>>>>>> In particular updating to the new jclouds and addressing the AMI issue
>>>>>>> (107) seems worthy of a new release.
>>>>>>>
>>>>>>> I'd be happy to serve as release manager if everyone else is too busy. 
>>>>>>> :-)
>>>>>>>
>>>>>>> Patrick
>>>>>>>
>>>>>>
>>>>>
>>>>
>>>
>>
>

Reply via email to