[
https://issues.apache.org/jira/browse/LUCENE-9890?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17310232#comment-17310232
]
Tomoko Uchida commented on LUCENE-9890:
---------------------------------------
Renaming it to "unstable" could make sense. Meanwhile, the question I'd like to
pose here is - there are too many "experimental" (or "unstable") APIs; we do
not have any clear policy about which APIs should be remained in experimental
or unstable status (it's completely up to the author's sense), and once a class
is marked "experimental" it seem to be remain experimental feature for long. I
do not see any difference between experimental APIs and non-experimental
(unmarked) ones...
> Retire @lucene.experimental tag and enforce @since tag for public classes
> -------------------------------------------------------------------------
>
> Key: LUCENE-9890
> URL: https://issues.apache.org/jira/browse/LUCENE-9890
> Project: Lucene - Core
> Issue Type: Improvement
> Components: general/javadocs
> Reporter: Tomoko Uchida
> Priority: Minor
>
> We have 800+ {{@lucene.experimental}} annotations in the main branch. Many of
> those classes were created years ago and have been time-tested on various
> setups, so may be able to be cleaned up.
> {code:java}
> lucene $ git grep lucene.experimental | wc -l
> 804
> {code}
> BTW, do we really need this annotation...?
> The description of it says nothing about when we should remove it from the
> javadocs: "lucene.experimental:a:WARNING: This API is experimental and might
> change in incompatible ways in the next release."
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
