Re: [DISCUSS][VOTE] Moving cloudmonkey to its own repository, have its own release process
+1 - reasonable plan. I'm not sure we need a "vote" though. Let's use lazy consensus on this one. Folks - you can see the plan. Shout if you disagree in any way. On Tue, Jun 25, 2013 at 2:48 AM, Rohit Yadav wrote: > Based on the previous discussion thread [1], we are proposing to move > cloudmonkey to a separate git repository as it really does not depend on > any of the core repo contents and to speed up its review, release > processes. Using git/prune I separate tools/cli as a git repository so as > to retain cloudmonkey's version history and David helped create this git > repository: > https://git-wip-us.apache.org/repos/asf/cloudstack-cloudmonkey.git > > Any CloudStack committer will have same rights on this repo as well. > > This thread fixes the email subject [1] and aims to attract people to > review the license, docs, code and anything else on this repo before David > will make this repo writable. David suggests this is to "ensure everyone > agrees that this is an accurate representation of what's in tools/cli". > > We can come up with the process details later too. To keep it simple, I'm > proposing; > > - Fast releases: Since cloudmonkey's releases may not be periodic, they > should be done whenever we have a suitable candidate with fixes or features > to be released > - Releases on pypi, which makes it simple. Signed tarballs etc. just like > CloudStack. > - Independent of CloudStack releases, all cloudmonkey releases should > support CloudStack 4.0+ releases and broken backward compatibilities should > be handled internally. Latest cloudmonkey release should always be ahead of > developing CloudStack release, i.e. to say you always have and support the > latest and the greatest. > > [1] http://markmail.org/thread/rgemstk42o7o4q55 > > Cheers.
Re: [DISCUSS][VOTE] Moving cloudmonkey to its own repository, have its own release process
On Tue, Jun 25, 2013 at 1:55 PM, Chip Childers wrote: > +1 - reasonable plan. I'm not sure we need a "vote" though. Let's > use lazy consensus on this one. > > Folks - you can see the plan. Shout if you disagree in any way. > Agreed with lazy consensus for the move. I would like some explicit reviews of the repo. I'd really like to get this writable and a release generated. --David
Re: [DISCUSS][VOTE] Moving cloudmonkey to its own repository, have its own release process
On Tue, Jun 25, 2013, at 01:00 PM, David Nalley wrote: > On Tue, Jun 25, 2013 at 1:55 PM, Chip Childers > wrote: > > +1 - reasonable plan. I'm not sure we need a "vote" though. Let's > > use lazy consensus on this one. > > > > Folks - you can see the plan. Shout if you disagree in any way. > > > > Agreed with lazy consensus for the move. > I would like some explicit reviews of the repo. > I'd really like to get this writable and a release generated. +1 to lazy consensus. (oh, wait...) Best, jzb -- Joe Brockmeier j...@zonker.net Twitter: @jzb http://www.dissociatedpress.net/
Re: [DISCUSS][VOTE] Moving cloudmonkey to its own repository, have its own release process
+1 to the proposal and lazy consensus On Jun 25, 2013, at 2:34 PM, Joe Brockmeier wrote: > On Tue, Jun 25, 2013, at 01:00 PM, David Nalley wrote: >> On Tue, Jun 25, 2013 at 1:55 PM, Chip Childers >> wrote: >>> +1 - reasonable plan. I'm not sure we need a "vote" though. Let's >>> use lazy consensus on this one. >>> >>> Folks - you can see the plan. Shout if you disagree in any way. >>> >> >> Agreed with lazy consensus for the move. >> I would like some explicit reviews of the repo. >> I'd really like to get this writable and a release generated. > > +1 to lazy consensus. (oh, wait...) > > Best, > > jzb > -- > Joe Brockmeier > j...@zonker.net > Twitter: @jzb > http://www.dissociatedpress.net/
Re: [DISCUSS][VOTE] Moving cloudmonkey to its own repository, have its own release process
+1 to lazine Ahmad On Jun 25, 2013, at 11:53 AM, John Burwell wrote: > +1 to the proposal and lazy consensus > > On Jun 25, 2013, at 2:34 PM, Joe Brockmeier wrote: > >> On Tue, Jun 25, 2013, at 01:00 PM, David Nalley wrote: >>> On Tue, Jun 25, 2013 at 1:55 PM, Chip Childers >>> wrote: +1 - reasonable plan. I'm not sure we need a "vote" though. Let's use lazy consensus on this one. Folks - you can see the plan. Shout if you disagree in any way. >>> >>> Agreed with lazy consensus for the move. >>> I would like some explicit reviews of the repo. >>> I'd really like to get this writable and a release generated. >> >> +1 to lazy consensus. (oh, wait...) >> >> Best, >> >> jzb >> -- >> Joe Brockmeier >> j...@zonker.net >> Twitter: @jzb >> http://www.dissociatedpress.net/ >
Re: [DISCUSS][VOTE] Moving cloudmonkey to its own repository, have its own release process
So I used the diff_dirs tool and here is the output: ke4qqq@mba ~/Documents/apache/asf/committers/tools/releases[master*]$ ./compare_dirs.pl -i ~/Documents/apache/cloudstack/incubator-cloudstack/tools/cli/ ~/Documents/apache/cloudstack/cloudstack-cloudmonkey/ File name comparison failed here: FILE/pom.xmla013255af9eb821fbdd17868b5939c3d FILE/.gitignore80b4d2b4ac347991c0e0cb51fb47dc40 Continuing... File name comparison failed here: FILE/pom.xmla013255af9eb821fbdd17868b5939c3d FILE/LICENSEd46978bef81ed50d0d3c0b74f2e8e0d5 Continuing... File name comparison failed here: FILE/pom.xmla013255af9eb821fbdd17868b5939c3d FILE/Makefileafc9ef31cb6d6303acf60eecbfb7d32d Continuing... File name comparison failed here: FILE/pom.xmla013255af9eb821fbdd17868b5939c3d FILE/README.md68e19cfaa11d6b6db2e30eec117ec23f Continuing... File name comparison failed here: FILE/pom.xmla013255af9eb821fbdd17868b5939c3d FILE/setup.py2b63d2afe3c2c9735dcc8a6ea1f9af2f Continuing... Comparison failed here: FILE:/home/ke4qqq/Documents/apache/cloudstack/incubator-cloudstack/tools/cli//setup.py:8bc9e461e46b8667274c95b9dfef1d27 FILE:/home/ke4qqq/Documents/apache/cloudstack/cloudstack-cloudmonkey//setup.py:2b63d2afe3c2c9735dcc8a6ea1f9af2f --David On Tue, Jun 25, 2013 at 2:00 PM, David Nalley wrote: > On Tue, Jun 25, 2013 at 1:55 PM, Chip Childers > wrote: >> +1 - reasonable plan. I'm not sure we need a "vote" though. Let's >> use lazy consensus on this one. >> >> Folks - you can see the plan. Shout if you disagree in any way. >> > > Agreed with lazy consensus for the move. > I would like some explicit reviews of the repo. > I'd really like to get this writable and a release generated. > > --David
Re: [DISCUSS][VOTE] Moving cloudmonkey to its own repository, have its own release process
Looks good, .gitignore, Makefile, README and LICENSE were added on the new git repo as they were needed and did not exit in tools/cli; pom.xml was removed on the new repo as it was not needed instead we have a simple Makefile. Not sure about setup.py related failures. Cheers. On Wed, Jun 26, 2013 at 1:37 AM, David Nalley wrote: > So I used the diff_dirs tool and here is the output: > > ke4qqq@mba ~/Documents/apache/asf/committers/tools/releases[master*]$ > ./compare_dirs.pl -i > ~/Documents/apache/cloudstack/incubator-cloudstack/tools/cli/ > ~/Documents/apache/cloudstack/cloudstack-cloudmonkey/ > File name comparison failed here: > FILE/pom.xmla013255af9eb821fbdd17868b5939c3d > FILE/.gitignore80b4d2b4ac347991c0e0cb51fb47dc40 > Continuing... > File name comparison failed here: > FILE/pom.xmla013255af9eb821fbdd17868b5939c3d > FILE/LICENSEd46978bef81ed50d0d3c0b74f2e8e0d5 > Continuing... > File name comparison failed here: > FILE/pom.xmla013255af9eb821fbdd17868b5939c3d > FILE/Makefileafc9ef31cb6d6303acf60eecbfb7d32d > Continuing... > File name comparison failed here: > FILE/pom.xmla013255af9eb821fbdd17868b5939c3d > FILE/README.md68e19cfaa11d6b6db2e30eec117ec23f > Continuing... > File name comparison failed here: > FILE/pom.xmla013255af9eb821fbdd17868b5939c3d > FILE/setup.py2b63d2afe3c2c9735dcc8a6ea1f9af2f > Continuing... > Comparison failed here: > > FILE:/home/ke4qqq/Documents/apache/cloudstack/incubator-cloudstack/tools/cli//setup.py:8bc9e461e46b8667274c95b9dfef1d27 > > FILE:/home/ke4qqq/Documents/apache/cloudstack/cloudstack-cloudmonkey//setup.py:2b63d2afe3c2c9735dcc8a6ea1f9af2f > > > --David > > On Tue, Jun 25, 2013 at 2:00 PM, David Nalley wrote: > > On Tue, Jun 25, 2013 at 1:55 PM, Chip Childers > > wrote: > >> +1 - reasonable plan. I'm not sure we need a "vote" though. Let's > >> use lazy consensus on this one. > >> > >> Folks - you can see the plan. Shout if you disagree in any way. > >> > > > > Agreed with lazy consensus for the move. > > I would like some explicit reviews of the repo. > > I'd really like to get this writable and a release generated. > > > > --David >
Re: [DISCUSS][VOTE] Moving cloudmonkey to its own repository, have its own release process
> > 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
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 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: Do you plan on generating a cloudmonkey release? (and acting as the RM?, should be comparatively simple, but we might need to document it.) Setup.py will need to be fixed, but I have no other concerns than that. I plan to make this writable momentarily. --David On Sat, Jun 29, 2013 at 9:27 AM, Rohit Yadav 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 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
On Sat, Jun 29, 2013 at 9:47 PM, David Nalley 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 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 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
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 wrote: > > > On Sat, Jun 29, 2013 at 9:47 PM, David Nalley 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 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 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
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 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 wrote: > >> >> >> On Sat, Jun 29, 2013 at 9:47 PM, David Nalley 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 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 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
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 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 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 > wrote: > > > >> > >> > >> On Sat, Jun 29, 2013 at 9:47 PM, David Nalley 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 > 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 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
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 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 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 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 >> wrote: >> > >> >> >> >> >> >> On Sat, Jun 29, 2013 at 9:47 PM, David Nalley 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 >> 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 >> wrote: >> >>> > >> >>> >> > >> >>> >> > Not sure about setup.py related failures. >> >>> >> > >> >>> >> >> >>> >> Me either - setup.py is pretty dramatically different between the >> two >> >>> >> repos. >> >>> >> >> >>> >> --David >> >>> >> >> >>> >> >> >> >> >> > >
