bigtop-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Andrew Purtell <apurt...@apache.org>
Subject Re: [Feature Request] PuppetForge module for 'bigtop-deploy'
Date Wed, 03 Jun 2015 04:52:32 GMT
Hi Jazz, it's been a while.
Thanks for your interest in Bigtop, writing in, and filing the JIRA!



On Wed, Jun 3, 2015 at 12:43 PM, Jazz Yao-Tsung Wang <jazzwang.tw@gmail.com>
wrote:

> Hi Evans Ye,
>
> I've created a JIRA for this improvement.
> https://issues.apache.org/jira/browse/BIGTOP-1889
>
> Great thanks for all the support of BigTop team.
>
> - Jazz
>
> On Tue, Jun 2, 2015 at 1:45 AM, Evans Ye <evansye@apache.org> wrote:
>
>> I think it's better to create a JIRA and track the progress there.
>> Jazz, would you mind to create one?
>> Maybe you can just copy your message in mail there. :)
>>
>> 2015-06-02 1:24 GMT+08:00 Roman Shaposhnik <roman@shaposhnik.org>:
>>
>>> On Mon, Jun 1, 2015 at 9:51 AM, Evans Ye <evansye@apache.org> wrote:
>>> > Yup. I think this is a great idea to promote bigtop.
>>> > The solution makes our puppet recipes and packages much easier to
>>> access by
>>> > users.
>>> > I think the only concern is how we're going to maintain the code on
>>> > puppetforge.
>>> > The easiest way is to ship the code to puppetforge once we released a
>>> new
>>> > version of bigtop.
>>> > Probably we can give this a shot in the upcoming 1.0 release, so that
>>> we can
>>> > have one more item to list in the announcement. :)
>>>
>>> Strong +1 to the initial drop of Bigtop 1.0 puppet code. From that point
>>> on, we
>>> can update anytime we do a release, I suppose.
>>>
>>> Thanks,
>>> Roman.
>>>
>>
>>
>


-- 
Best regards,

   - Andy

Problems worthy of attack prove their worth by hitting back. - Piet Hein
(via Tom White)

Mime
View raw message