Re: [DISCUSS][VOTE] Moving cloudmonkey to its own repository, have its own release process

[Rohit Yadav <bh...@apache.org>]

Hey! Been sometime on this thread.

David, can you confirm if the cloudmonkey repo is writable by CloudStack
committers so I can populate the README file with more details, add some
unit tests to enforce contract of interfaces and services and then
eventually help with a release.

Any suggestions, feedback?

Cheers.

On Sun, Jun 30, 2013 at 11:02 PM, Rohit Yadav <bh...@apache.org> wrote:

>
>
> On Sat, Jun 29, 2013 at 9:47 PM, David Nalley <da...@gnsa.us> wrote:
>
>> Rohit:
>>
>> Do you plan on generating a cloudmonkey release? (and acting as the
>> RM?, should be comparatively simple, but we might need to document
>> it.)
>>
>
> Sure, why not. I can be the initial RM. We can document the process on
> wiki which should be fairly straight forward and put some (help)
> documentation or links to it on the README file.
>
>
>> Setup.py will need to be fixed, but I have no other concerns than
>> that. I plan to make this writable momentarily.
>>
>
> Pl. go ahead and also fix setup.py, when I do diff -Naur with the latest
> it shows no differences for me. I'm not sure how to fix in history because
> when I do diff for all commits where setup.py was changed I see no
> differences in those commits.
>
> Regards.
>
>
>>
>> --David
>>
>> On Sat, Jun 29, 2013 at 9:27 AM, Rohit Yadav <bh...@apache.org> wrote:
>> > More than 72 hours now. Let's make it writable and publish latest
>> > cloudmonkey on pypi.
>> >
>> > Cheers.
>> >
>> > On Wed, Jun 26, 2013 at 3:02 AM, David Nalley <da...@gnsa.us> wrote:
>> >
>> >> >
>> >> > Not sure about setup.py related failures.
>> >> >
>> >>
>> >> Me either - setup.py is pretty dramatically different between the two
>> >> repos.
>> >>
>> >> --David
>> >>
>>
>
>

Re: [DISCUSS][VOTE] Moving cloudmonkey to its own repository, have its own release process

[Rohit Yadav <ro...@gmail.com>]

Sorry, I did not have bandwidth to reply but now. Just to update people on
this; in our next steps

- Remove tools/cli from cloudstack's repo and fix README and link to the
cloudmonkey repo, inform users, devs
- Write a wiki on cloudmonkey's release process, which is around "ship
fast, break things"
- Release cloudmonkey whenever there are changes


Regards.

On Sun, Jul 7, 2013 at 10:19 PM, Rohit Yadav <ro...@gmail.com> wrote:

> Thanks David.
> Will start contributing those things in my free time (mostly weekends) and
> help with a release soon.
>
> Cheers.
>
>
> On Sun, Jul 7, 2013 at 8:47 PM, David Nalley <da...@gnsa.us> wrote:
>
>> Sorry - I really meant to get to it before now.
>> It's now writable. Enjoy.
>>
>> --David
>>
>> On Sun, Jul 7, 2013 at 7:06 AM, Rohit Yadav <bh...@apache.org> wrote:
>> > Hey! Been sometime on this thread.
>> >
>> > David, can you confirm if the cloudmonkey repo is writable by CloudStack
>> > committers so I can populate the README file with more details, add some
>> > unit tests to enforce contract of interfaces and services and then
>> > eventually help with a release.
>> >
>> > Any suggestions, feedback?
>> >
>> > Cheers.
>> >
>> > On Sun, Jun 30, 2013 at 11:02 PM, Rohit Yadav <bh...@apache.org>
>> wrote:
>> >
>> >>
>> >>
>> >> On Sat, Jun 29, 2013 at 9:47 PM, David Nalley <da...@gnsa.us> wrote:
>> >>
>> >>> Rohit:
>> >>>
>> >>> Do you plan on generating a cloudmonkey release? (and acting as the
>> >>> RM?, should be comparatively simple, but we might need to document
>> >>> it.)
>> >>>
>> >>
>> >> Sure, why not. I can be the initial RM. We can document the process on
>> >> wiki which should be fairly straight forward and put some (help)
>> >> documentation or links to it on the README file.
>> >>
>> >>
>> >>> Setup.py will need to be fixed, but I have no other concerns than
>> >>> that. I plan to make this writable momentarily.
>> >>>
>> >>
>> >> Pl. go ahead and also fix setup.py, when I do diff -Naur with the
>> latest
>> >> it shows no differences for me. I'm not sure how to fix in history
>> because
>> >> when I do diff for all commits where setup.py was changed I see no
>> >> differences in those commits.
>> >>
>> >> Regards.
>> >>
>> >>
>> >>>
>> >>> --David
>> >>>
>> >>> On Sat, Jun 29, 2013 at 9:27 AM, Rohit Yadav <bh...@apache.org>
>> wrote:
>> >>> > More than 72 hours now. Let's make it writable and publish latest
>> >>> > cloudmonkey on pypi.
>> >>> >
>> >>> > Cheers.
>> >>> >
>> >>> > On Wed, Jun 26, 2013 at 3:02 AM, David Nalley <da...@gnsa.us>
>> wrote:
>> >>> >
>> >>> >> >
>> >>> >> > Not sure about setup.py related failures.
>> >>> >> >
>> >>> >>
>> >>> >> Me either - setup.py is pretty dramatically different between the
>> two
>> >>> >> repos.
>> >>> >>
>> >>> >> --David
>> >>> >>
>> >>>
>> >>
>> >>
>>
>
>

Re: [DISCUSS][VOTE] Moving cloudmonkey to its own repository, have its own release process

[Rohit Yadav <ro...@gmail.com>]

Thanks David.
Will start contributing those things in my free time (mostly weekends) and
help with a release soon.

Cheers.


On Sun, Jul 7, 2013 at 8:47 PM, David Nalley <da...@gnsa.us> wrote:

> Sorry - I really meant to get to it before now.
> It's now writable. Enjoy.
>
> --David
>
> On Sun, Jul 7, 2013 at 7:06 AM, Rohit Yadav <bh...@apache.org> wrote:
> > Hey! Been sometime on this thread.
> >
> > David, can you confirm if the cloudmonkey repo is writable by CloudStack
> > committers so I can populate the README file with more details, add some
> > unit tests to enforce contract of interfaces and services and then
> > eventually help with a release.
> >
> > Any suggestions, feedback?
> >
> > Cheers.
> >
> > On Sun, Jun 30, 2013 at 11:02 PM, Rohit Yadav <bh...@apache.org>
> wrote:
> >
> >>
> >>
> >> On Sat, Jun 29, 2013 at 9:47 PM, David Nalley <da...@gnsa.us> wrote:
> >>
> >>> Rohit:
> >>>
> >>> Do you plan on generating a cloudmonkey release? (and acting as the
> >>> RM?, should be comparatively simple, but we might need to document
> >>> it.)
> >>>
> >>
> >> Sure, why not. I can be the initial RM. We can document the process on
> >> wiki which should be fairly straight forward and put some (help)
> >> documentation or links to it on the README file.
> >>
> >>
> >>> Setup.py will need to be fixed, but I have no other concerns than
> >>> that. I plan to make this writable momentarily.
> >>>
> >>
> >> Pl. go ahead and also fix setup.py, when I do diff -Naur with the latest
> >> it shows no differences for me. I'm not sure how to fix in history
> because
> >> when I do diff for all commits where setup.py was changed I see no
> >> differences in those commits.
> >>
> >> Regards.
> >>
> >>
> >>>
> >>> --David
> >>>
> >>> On Sat, Jun 29, 2013 at 9:27 AM, Rohit Yadav <bh...@apache.org>
> wrote:
> >>> > More than 72 hours now. Let's make it writable and publish latest
> >>> > cloudmonkey on pypi.
> >>> >
> >>> > Cheers.
> >>> >
> >>> > On Wed, Jun 26, 2013 at 3:02 AM, David Nalley <da...@gnsa.us> wrote:
> >>> >
> >>> >> >
> >>> >> > Not sure about setup.py related failures.
> >>> >> >
> >>> >>
> >>> >> Me either - setup.py is pretty dramatically different between the
> two
> >>> >> repos.
> >>> >>
> >>> >> --David
> >>> >>
> >>>
> >>
> >>
>

Re: [DISCUSS][VOTE] Moving cloudmonkey to its own repository, have its own release process

[David Nalley <da...@gnsa.us>]

Sorry - I really meant to get to it before now.
It's now writable. Enjoy.

--David

On Sun, Jul 7, 2013 at 7:06 AM, Rohit Yadav <bh...@apache.org> wrote:
> Hey! Been sometime on this thread.
>
> David, can you confirm if the cloudmonkey repo is writable by CloudStack
> committers so I can populate the README file with more details, add some
> unit tests to enforce contract of interfaces and services and then
> eventually help with a release.
>
> Any suggestions, feedback?
>
> Cheers.
>
> On Sun, Jun 30, 2013 at 11:02 PM, Rohit Yadav <bh...@apache.org> wrote:
>
>>
>>
>> On Sat, Jun 29, 2013 at 9:47 PM, David Nalley <da...@gnsa.us> wrote:
>>
>>> Rohit:
>>>
>>> Do you plan on generating a cloudmonkey release? (and acting as the
>>> RM?, should be comparatively simple, but we might need to document
>>> it.)
>>>
>>
>> Sure, why not. I can be the initial RM. We can document the process on
>> wiki which should be fairly straight forward and put some (help)
>> documentation or links to it on the README file.
>>
>>
>>> Setup.py will need to be fixed, but I have no other concerns than
>>> that. I plan to make this writable momentarily.
>>>
>>
>> Pl. go ahead and also fix setup.py, when I do diff -Naur with the latest
>> it shows no differences for me. I'm not sure how to fix in history because
>> when I do diff for all commits where setup.py was changed I see no
>> differences in those commits.
>>
>> Regards.
>>
>>
>>>
>>> --David
>>>
>>> On Sat, Jun 29, 2013 at 9:27 AM, Rohit Yadav <bh...@apache.org> wrote:
>>> > More than 72 hours now. Let's make it writable and publish latest
>>> > cloudmonkey on pypi.
>>> >
>>> > Cheers.
>>> >
>>> > On Wed, Jun 26, 2013 at 3:02 AM, David Nalley <da...@gnsa.us> wrote:
>>> >
>>> >> >
>>> >> > Not sure about setup.py related failures.
>>> >> >
>>> >>
>>> >> Me either - setup.py is pretty dramatically different between the two
>>> >> repos.
>>> >>
>>> >> --David
>>> >>
>>>
>>
>>