garydgregory commented on PR #450: URL: https://github.com/apache/commons-text/pull/450#issuecomment-1712802790
> Guava has `@Beta` for APIs they want to push but not commit to yet. Perhaps we can add something similar? This feels unwise to me and I would discourage it. Based on what I've seen in Commons, once something is public or protected, it will be used and complained about when changed. This would also make JApiCmp more complex to configure: How do you tell it to ignore classes, methods, and fields annotated with \@Foo?. I certainly would not want to individually list each in-flux element. Same issue with using a ".beta." package name. If you put an Alpha, Beta or M label on the whole release then you make it obvious from the onset that you are offering an unstable platform, which is the approach Commons has already taken with Commons FileUpload and Commons Imaging. Using a Beta release requires buy-in from the user that there are unstable elements, as opposed to using a normal full release that happens to have unstable parts in it. Commons has been very good at maintaining binary compatibility in normal releases, so I think it wise to keep maintaining this expectation. -- 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: issues-unsubscr...@commons.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
