Mark Payne created YETUS-416:
--------------------------------
Summary: Provide ability to differentiate between stability for
implementation vs. stability for use
Key: YETUS-416
URL: https://issues.apache.org/jira/browse/YETUS-416
Project: Yetus
Issue Type: Improvement
Components: Audience Annotations
Reporter: Mark Payne
I would like to have the ability to specify in an annotation that users can be
confident that they can use an API from one minor version to the next, but that
the interface should not be implemented by others, as new methods may be added
between minor versions.
This was discussed briefly on NIFI-1373. [~busbey] provided the following
commentary there:
You could do that with an audience annotation. normally I don't care for the
"LimitedPrivate" audience level, but you could use it on such interfaces with a
detail that indicates it's for downstream consumption but not implementation.
One way to avoid using LimitedPrivate for this would be to open a feature
request against Yetus to have the Public interface audience add a similar
"detail" field.
I think the use of java interfaces in apis where downstream users aren't
expected to implement the interfaces themselves should be pretty common, so
maybe this is worth a specific solution (either on the InterfaceStability as
you mention or on the InterfaceAudience). Mind opening a jira in the YETUS
tracker, or just emailing the dev@yetus list?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
