beam-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Beam JIRA Bot (Jira)" <j...@apache.org>
Subject [jira] [Updated] (BEAM-10237) Clean up Experimental usage and come up with a graduation policy
Date Mon, 10 Aug 2020 17:07:08 GMT

     [ https://issues.apache.org/jira/browse/BEAM-10237?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Beam JIRA Bot updated BEAM-10237:
---------------------------------
    Labels: stale-P2  (was: )

> 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)

Mime
View raw message