RE: [VOTE] Apache Cloudstack 4.10.0.0 RC3

Hi All, From my view point 'we' have been the architects of our own downfall. Once a code freeze is in place NO new features, NO enhancements should be going in. Once we're at an RC stage, NO new bug fixes other that for the blockers should be going in. that way the release gets out, and the

Re: [VOTE] Apache Cloudstack 4.10.0.0 RC3

I tend to agree with you here, Daan. I know the downside we’ve discussed in the past is that overall community participation in the RC process has dropped off when such a new branch is created (since the community as a whole tends to focus more on the new branch rather than on testing the RC

Re: [VOTE] Apache CloudStack 4.10.0.0 RC6

+1 (binding) I am not concerned about the code changes that went into this RC since the previous RC, so I am still happy with the amount of automated and manual testing that I performed on a previous RC. On 6/25/17, 11:07 PM, "Rajani Karuturi" wrote: Hi All,

Weekly Update on GSoC'17 project

Hello, Last weeks work mainly revolved around about building cloudstack again as I have some issues with jettty versions in cloudstack. Jetty version 9 and above are required to run websockets my last build had version 8.1.15 due to which I was not able to establish a websocket

Kernel security update for CVE-2017-1000364 breaks cloudstack startup scripts with jsvc on Ubuntu 14.04 or 16.04

Hello, When I tested the CloudStack 4.10 RC5 on Ubuntu 16.04, I've indicate an issue about the startup of cloudstack-management service. The error message is : "jsvc.exec error: Service killed by signal 11" Today I've made some maintenance operations on my CS 4.9.2.0 platform and after the