cloudstack-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Rohit Yadav <bhais...@apache.org>
Subject Re: [DISCUSS][VOTE] Moving cloudmonkey to its own repository, have its own release process
Date Sun, 07 Jul 2013 11:06:41 GMT
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 <bhaisaab@apache.org> wrote:

>
>
> On Sat, Jun 29, 2013 at 9:47 PM, David Nalley <david@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 <bhaisaab@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 <david@gnsa.us> wrote:
>> >
>> >> >
>> >> > Not sure about setup.py related failures.
>> >> >
>> >>
>> >> Me either - setup.py is pretty dramatically different between the two
>> >> repos.
>> >>
>> >> --David
>> >>
>>
>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message