Re: Why CloudStack 5

2019-01-26 Thread Sven Vogel
Hi Guys, That what I say to version 5. I understand both people these they say version 5.0 is the right way or 4.XX. For a marketing men version 5 looks like a big deal but under the hood what’s really new? I know there are new features but what of them is a groundbreaking feature? For me its

Re: Why CloudStack 5

2019-01-25 Thread Ivan Kudryavtsev
Well, my intention is to prevent the community from doing revolutionary changes intending to deliver redesigned 5.0, to keep going the current road improving the codebase, removing the odd stuff like 'Citrix NetScaler', 'Juniper XYZ' if nobody supports them, improving current functionality and addi

Re: Why CloudStack 5

2019-01-25 Thread Rafael Weingärtner
I am 100% with @Rohit Yadav with respect to 4.12. I do diverge regarding the next LTS version though. As you all guys said, the community is small, and as such, if we have the requirement for multiple major changes, before upgrading the "X" bit in a release, we will never go there (that is a fact

Re: Why CloudStack 5

2019-01-24 Thread Suresh Kumar Anaparti
Sounds good. Altogether, the makeover should be a new user experience and leverage the latest hypervisor/storage tech and new/redesigned frameworks. -Suresh On Thu, Jan 24, 2019 at 10:13 AM Rohit Yadav wrote: > I'm in the favour of keeping the 4.x going because no API compatibility is > broken,

Re: Why CloudStack 5

2019-01-24 Thread Ivan Kudryavtsev
Well, I'm glad the topic raised the discussion. That's great. My point is very carefully explained by Rohit. It's not a new idea - CloudStack community is small. Some features are abandoned and broken because of no developers behind them. I bet certain features still not tested in 4.11.2 because no

Re: Why CloudStack 5

2019-01-23 Thread Rohit Yadav
I'm in the favour of keeping the 4.x going because no API compatibility is broken, and as long as we are following semver there is no need. Calling a 4.x a 5.x just for the sake of bumping versions may cause some perception issue. Removal of unsupported/poc/incomplete features, plugins including

Re: Why CloudStack 5

2019-01-23 Thread Tutkowski, Mike
That sounds reasonable to me. From: Rafael Weingärtner Sent: Wednesday, January 23, 2019 5:25 PM To: users Cc: dev@cloudstack.apache.org Subject: Re: Why CloudStack 5 NetApp Security WARNING: This is an external email. Do not click links or open attachments

Re: Why CloudStack 5

2019-01-23 Thread Rafael Weingärtner
Rafael Weingärtner > Sent: Wednesday, January 23, 2019 4:58 PM > To: dev > Cc: users > Subject: Re: Why CloudStack 5 > > NetApp Security WARNING: This is an external email. Do not click links or > open attachments unless you recognize the sender and know the content is > saf

Re: Why CloudStack 5

2019-01-23 Thread Tutkowski, Mike
Is 4.12 a decent candidate to be branded 5.0 or might we be waiting for some specific set of backwards-incompatible updates? From: Rafael Weingärtner Sent: Wednesday, January 23, 2019 4:58 PM To: dev Cc: users Subject: Re: Why CloudStack 5 NetApp Security

Re: Why CloudStack 5

2019-01-23 Thread Rafael Weingärtner
Hello Ivan, Can you provide reasons why not move to a version 5? To help you, I will provide why I think we should move to 5.0.0 after 4.12. Therefore, I would expect this 5.0.0 to be an LTS version as well. 1. To begin with, technically, we should already be in version 5 if we had been fol