Github user karuturi commented on the pull request:
https://github.com/apache/cloudstack/pull/1091#issuecomment-158326799
I am ok with merging the fix to 4.5+. I am not against that. But, missing
one release is not acceptable. Given that its already merged on 4.7, merging in
4.5 now is not an option. I am ok with merging css/js improvements in 4.5+
releases.
Yes, we have been backporting fixes since a long time and thats what we are
trying to change. We fix forward now.
If the upgrades are proper with minimal set of features and code change,
users will upgrade. Right now they dont because its broken. They dont know if
the issues fixed in the current release will be regressed in the next release.
There can be hesitation for 5.0 release but 4.7 should be smooth if we fwd
merge. Anyone following the release process closely will be able to figure that
out (and we are doing quick releases)
Lets not change the semantics of version number (MAJOR.MINOR.PATCH)
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
