Hi all,
I think the criteria for any additional PRs to be considered for 4.11.0.0 release should be: - Is it a blocker, especially blocking the release? - Is is fixing any test failures or regressions? - Is it release related, for example - packaging, systemvmtemplate, db-upgrade path related Is this agreeable? In case we miss any bugfix PRs, they may be sent to the 4.11 branch (to be cut soon), and in future and make its way to a minor release such as 4.11.1.0 etc. For the purpose of keeping up with the release schedule, I think we should be reluctant to move the goal post again. I'll update on outstanding milestone PRs by EOD today. Thanks for your understanding. - Rohit <https://cloudstack.apache.org> ________________________________ From: Khosrow Moossavi <kmooss...@cloudops.com> Sent: Tuesday, January 9, 2018 10:55:59 PM To: dev@cloudstack.apache.org; us...@cloudstack.apache.org Subject: Squeeze another PR (#2398) in 4.11 milestone Hi community We've found [1] and fixed [2] an issue in 4.10 regarding snapshots remaining on primary storage (XenServer + Swift) which causes VDI chain gets full after some time and user cannot take another snapshot. Please include this in 4.11 milestone if you see fit. [1]: https://issues.apache.org/jira/browse/CLOUDSTACK-10222 [2]: https://github.com/apache/cloudstack/pull/2398 Thanks Khosrow rohit.ya...@shapeblue.com www.shapeblue.com 53 Chandos Place, Covent Garden, London WC2N 4HSUK @shapeblue
