sijie commented on issue #6122: [pulsar-admin] allow tenant admin to manage subscription permission URL: https://github.com/apache/pulsar/pull/6122#issuecomment-580977815 @rdhabalia I understand that's a bug. However this behavior has been there from v1 to v3. If this "buggy" behavior was exposed publicly to the user, that means some existing tools might already rely on this behavior. Changing such an API is breaking the behavior that people saws before. Hence I think a better option is to introduce a newer API to amend this buggy behavior. For any behavior changes, it should be highlighted in a release note. I understand that we used t create release notes when cutting a release. But it has introduced many troubles to the release manager as well as for the users. Because it is hard for a release manager to grab all the changes at the time of cutting a release. Users are frustrated about the breaking changes that are not documented and have complained about the documentation here and there. Hence I would suggest we should adding a place to track breaking changes and behavior during developing a release. Adding a section for an under-developing release in release notes for accumulating breaking changes seems to be a good way to go. Because the release manager can find it when cutting a release and users can find potential breaking changes in the upcoming release. I think the conversation here should be brought to the mailing list for a discussion and a potential vote since it is related to behavior change and also release process/document change.
---------------------------------------------------------------- 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. For queries about this service, please contact Infrastructure at: [email protected] With regards, Apache Git Services
