GutoVeronezi commented on PR #9177: URL: https://github.com/apache/cloudstack/pull/9177#issuecomment-2161243596
> @GutoVeronezi , I understand your point, but we do not have a simple usable procedure yet. The implicit procedure was "we don't introduce any backwards incompatability, .. unless we all agree". And so in this case you are right. That does not remove the need to decide on individual issues. Maybe @rohityadavcloud is a bit quick art the gun, but it makes sense to first introduce a setting and than later reverse the default. We have done it like that in the past. Maybe we can add this to #8970 (if it is not included yet). > > So how do you propose we take this forward? cc @JoaoJandre @sureshanaparti @weizhouapache As we already have a configuration to change the behavior, we should keep the current behavior and guide people through the release notes on how to change it. Then, we should continue the #8970 discussion. Once a process is defined and documented, we can look back to the configuration and change the default according to the policy we defined (or even remove the configuration if we decide so). Other systems do that way, like GitLab and OpenStack; the problem is that we do not have this defined and documented yet. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: commits-unsubscr...@cloudstack.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
