Re: [VOTE] Apache CloudStack 4.10.0.0 RC6

Hi all, I 'm sorry for voting -1 again. Issue : https://issues.apache.org/jira/browse/CLOUDSTACK-9980 Caused by : https://github.com/apache/cloudstack/pull/2089 Fixed by : https://github.com/apache/cloudstack/pull/2162 Kris - Nuage Networks On 26 June 2017 at 18:58, Tutkowski, Mike

Re: [VOTE] Apache Cloudstack 4.10.0.0 RC3

I'm glad you guys (Paul and Rafael) agree with me. We should cut a branch once the first RC is built. Then we should only allow blockers in to fix RC issues. This should speed up our releases in the future. > On Jun 27, 2017, at 10:14 AM, Rafael Weingärtner >

Re: [VOTE] Apache Cloudstack 4.10.0.0 RC3

+1 to what Paul said. IMHO, as soon as we start a release candidate to close a version, all merges should stop (period); the only exceptions should be PRs that address specific problems in the RC. I always thought that we had a protocol for that [1]; maybe for this version, we have not followed

Re: ***Cloudstack EUUG - CFP***

Hi Giles, I could give a talk on live migration with KVM that we have since one year here. That might help to get the feature fixed and merged for CS. Let me know. https://github.com/apache/cloudstack/pull/1709 Marc-Aurèle On Thu, Jun 22, 2017 at 1:41 PM, Wido den Hollander

Re: [VOTE] Apache CloudStack 4.10.0.0 RC6

Hi Kris, Can you please apply 2162 locally and see if you are OK with the changes? We shouldn't be spending one RC cycle for one issue. Ideally, we should have more CIs running on PRs from different usage perspectives(like managed storage, nuage, basic network, local storage, etc.). That would

Re: [VOTE] Apache Cloudstack 4.10.0.0 RC3

We can do a release every month as long as we have enough people actively participating in the release process. We have people who wants to have their code/features checked in. We, very clearly do not have enough people working on releases/blockers. How many of us are testing/voting on releases