[
https://issues.apache.org/jira/browse/LUCENE-9890?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17311056#comment-17311056
]
Greg Miller commented on LUCENE-9890:
-------------------------------------
[~tomoko] I wonder if a slightly different cleanup approach might work here.
Instead of trying to go through and assess what of these could be "promoted" to
non-"experimental" (and then building consensus across the entire community), a
more tractable approach might be to propose things on a case-by-case basis as
you (or others) build dependencies on "experimental" APIs and want more of a
formal guarantee that they won't change out from under you. If you've got some
in mind that you want to propose removing the tag on, maybe start there? Just a
thought.
> 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]
