[DISCUSS] 5.0.0 and 6.0.0

2016-06-14 Thread John Burwell
All, We have been discussing whether or not the next release would introduce the need to increment the major revision number from 4 to 5 (i.e. become 5.0.0). While I think we are very close to the time to have a 5.0.0 release, I don’t think the next release will introduce any backwards

Re: 4.9+ release

2016-06-14 Thread ilya
I agree and support John's comments below. Regards ilya On 6/14/16 2:44 PM, John Burwell wrote: > All, > > Completely agree with Daan. Per semantic versioning, a major revision > increase must introduce a backwards incompatible change in the public API, > removal of one of more supported

Re: 4.9+ release

2016-06-14 Thread John Burwell
All, Completely agree with Daan. Per semantic versioning, a major revision increase must introduce a backwards incompatible change in the public API, removal of one of more supported devices, reduction in the list of supported distributions. I agree that when we require Java8+, drop Ubuntu

[GitHub] cloudstack pull request #1591: Updating Alert codes

2016-06-14 Thread dcarbone
GitHub user dcarbone opened a pull request: https://github.com/apache/cloudstack/pull/1591 Updating Alert codes Updating codes per values present here: https://github.com/apache/cloudstack/blob/4.8/api/src/org/apache/cloudstack/alert/AlertService.java#L39 You can merge this pull

RE: 4.9+ release

2016-06-14 Thread Paul Angus
+1 Daan. My recollection was that major version number changes were only to be triggered by breaks in backward compatibility (API). Kind regards, Paul Angus paul.an...@shapeblue.com  www.shapeblue.com 53 Chandos Place, Covent Garden, London WC2N 4HSUK @shapeblue -Original

Re: .install and .postinstall files

2016-06-14 Thread Nicolás Vázquez
Thanks Rafael! My bad, it was '.postinst' extension instead of '.postinstall' 2016-06-14 12:37 GMT-03:00 Rafael Fonseca : > Hey Nicolas, > > The .install file should be used by dpkg when the deb packages are built > with dpkg-buildpackage, i don't know about .postinstall

Re: .install and .postinstall files

2016-06-14 Thread Rafael Fonseca
Hey Nicolas, The .install file should be used by dpkg when the deb packages are built with dpkg-buildpackage, i don't know about .postinstall extension, usually you have to specify post-install scripts somewhere.. a grep -r on the code base should expose if that postinstall file is called from

.install and .postinstall files

2016-06-14 Thread Nicolás Vázquez
Hi all, A quick question: Where are 'debian/cloudstack-management.install' and 'debian/cloudstack-management.postinstall' files used? I see the first one declares folders to be created but I don't know where is this file used. Thanks, Nicolas

Re: 4.9+ release

2016-06-14 Thread Daan Hoogland
You know that would require more then one byte for our minor version, Will. I would be very pleased to go to 5.0 before that time. On Tue, Jun 14, 2016 at 3:43 PM, Will Stevens wrote: > Daan is just trying to get us to version 4.256. :P > > *Will STEVENS* > Lead

Re: 4.9+ release

2016-06-14 Thread Will Stevens
Daan is just trying to get us to version 4.256. :P *Will STEVENS* Lead Developer *CloudOps* *| *Cloud Solutions Experts 420 rue Guy *|* Montreal *|* Quebec *|* H3J 1S6 w cloudops.com *|* tw @CloudOps_ On Tue, Jun 14, 2016 at 9:41 AM, Daan Hoogland wrote: > -1 to what

Re: 4.9+ release

2016-06-14 Thread Daan Hoogland
-1 to what Wido said. None of those points warant a major release number upgrade. these should all be in 4.10, -.11, -12 etc. major incompatibilities like API refactor, dropping backend support for this or that hyporvisor or DB refactor are the things that warrant 5.0, IMNSHO On Tue, Jun 14,

[GitHub] cloudstack issue #1547: Fixes for VirtualRouters in Basic Networking, especi...

2016-06-14 Thread NuxRo
Github user NuxRo commented on the issue: https://github.com/apache/cloudstack/pull/1547 +1 merging, I'm also interested in this if it affects Advanced zone + Security Groups. Will test ASAP. --- If your project is set up for it, you can reply to this email and have your reply

[GitHub] cloudstack issue #1581: CLOUDSTACK-9404 Fixed ordering of network ACL rules ...

2016-06-14 Thread swill
Github user swill commented on the issue: https://github.com/apache/cloudstack/pull/1581 ### CI RESULTS ``` Tests Run: 85 Skipped: 0 Failed: 0 Errors: 0 Duration: 4h 01m 52s ``` **Associated Uploads**

[GitHub] cloudstack issue #1547: Fixes for VirtualRouters in Basic Networking, especi...

2016-06-14 Thread swill
Github user swill commented on the issue: https://github.com/apache/cloudstack/pull/1547 @ustcweizhou I can't wait forever on this. What I will likely do if I don't hear back from you is merge this and then cut the RC right away. I am hoping to cut the RC tomorrow, so if you can give

Re: 4.9+ release

2016-06-14 Thread Will Stevens
+1. :) On Jun 14, 2016 5:07 AM, "Wido den Hollander" wrote: > > > Op 14 juni 2016 om 10:55 schreef Rajani Karuturi : > > > > > > 4.10 or 5.0? > > > > I would say 4.10 > > > We are in the 4.* release cycle from a long time. > > Just wanted to check if anyone is

Re: 4.9+ release

2016-06-14 Thread Rohit Yadav
+1 to what Wido said. I think we should not be incrementing the major version unless we're breaking compatibility, introducing major UI/API/db changes. Regards, Rohit Yadav rohit.ya...@shapeblue.com  www.shapeblue.com 53 Chandos Place, Covent Garden, London WC2N 4HSUK @shapeblue On Jun 14

Re: 4.9+ release

2016-06-14 Thread Nux!
+1 what Wido said -- Sent from the Delta quadrant using Borg technology! Nux! www.nux.ro - Original Message - > From: "Wido den Hollander" > To: "Rajani Karuturi" , dev@cloudstack.apache.org > Sent: Tuesday, 14 June, 2016 10:07:01 > Subject: Re: 4.9+

Re: 4.9+ release

2016-06-14 Thread Wido den Hollander
> Op 14 juni 2016 om 10:55 schreef Rajani Karuturi : > > > 4.10 or 5.0? > I would say 4.10 > We are in the 4.* release cycle from a long time. > Just wanted to check if anyone is planning on major changes which warrants > 5.0 > 5.0 should imho be: - Java 8 - Ubuntu

4.9+ release

2016-06-14 Thread Rajani Karuturi
4.10 or 5.0? We are in the 4.* release cycle from a long time. Just wanted to check if anyone is planning on major changes which warrants 5.0 ~Rajani