[
https://issues.apache.org/jira/browse/BEAM-10237?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17133065#comment-17133065
]
Ismaël Mejía commented on BEAM-10237:
-------------------------------------
Yes we should start doing this (including Experimental into the changelog).
Automatic promotion out of Experimental may go against the interest of the
maintainers.
In most internal facing areas we should change things from Experimental to
Internal (I did a bunch of those)
In some areas removing Experimental bits could be relatively simple because we
can evolve incompatible ones via v2 versions like IOs and deprecate the
delicate ones are the ones in core until we have some maturity like Schemas,
and of course the ones that end up being contributors API like SDF
> Clean up Experimental usage and come up with a graduation policy
> ----------------------------------------------------------------
>
> Key: BEAM-10237
> URL: https://issues.apache.org/jira/browse/BEAM-10237
> Project: Beam
> Issue Type: Bug
> Components: beam-model
> Reporter: Ahmet Altay
> Priority: P2
>
> Beam, APIs use experimental features quite a lot. Experimental features are
> growing, but at some point we should consider either removing or graduating
> them.
> This is a proposal to:
> - Track: All experimental features will be continually tracked in the change
> log explicitly.
> - For features staying in experimental mode longer than 12 months,
> --> Graduate: we should review whether the feature meets the usage bar to be
> long term maintained,
> -- > Deprecate: or should be deprecated to reduce maintenance load.
> It would be good to add a github ci action to check new usage of experimental
> tags are added to the change log.
> /cc [~kenn] [~lcwik] [~robertwb]
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
