[jira] [Commented] (BEAM-10237) Clean up Experimental usage and come up with a graduation policy

["Beam JIRA Bot (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/BEAM-10237?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17174483#comment-17174483 ] 

Beam JIRA Bot commented on BEAM-10237:
--------------------------------------

This issue is P2 but has been unassigned without any comment for 60 days so it has been labeled "stale-P2". If this issue is still affecting you, we care! Please comment and remove the label. Otherwise, in 14 days the issue will be moved to P3.

Please see https://beam.apache.org/contribute/jira-priorities/ for a detailed explanation of what these priorities mean.


> 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
>              Labels: stale-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)