Yes, using @Unstable the way we do in XWiki Standard (so for each new API) does not make sense for a contrib extension (unless the contrib extension has the clear release and stabilization cycle, which is not the case here).
The only way it makes sense is when you know some API is not finished, you are still working on it and have a clear deadline (or at least a set of criteria) to decide when you plan to remove that annotation (and document that in the extension page for example). But maybe it's the case here ?
Thomas Mortagne on 28/Mar/25 09:16
Yes, using @Unstable the way we do in XWiki Standard (so for each new API) does not make sense for a contrib extension (unless the contrib extension has the a clear release and stabilization cycle, which is not the case here).
The only way it makes sense is when you know some API is not finished, you are still working on it and have a clear deadline (or at least a set of criteria) to decide when you plan to remove that annotation (and document that in the extension page for example). But maybe it's the case here ?
This message was sent by Atlassian Jira (v9.3.0#930000-sha1:287aeb6)
If image attachments aren't displayed, see this article.
