[GitHub] [beam] damccorm opened a new issue, #20393: Clean up Experimental usage and come up with a graduation policy

[GitBox <gi...@apache.org>]

damccorm opened a new issue, #20393:
URL: https://github.com/apache/beam/issues/20393

   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]
   
   Imported from Jira [BEAM-10237](https://issues.apache.org/jira/browse/BEAM-10237). Original Jira may contain additional context.
   Reported by: altay.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: github-unsubscribe@beam.apache.org.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org