You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@superset.apache.org by GitBox <gi...@apache.org> on 2021/01/21 23:05:22 UTC

[GitHub] [superset] garden-of-delete commented on issue #12566: [SIP-57] Proposal for Semantic Versioning

garden-of-delete commented on issue #12566:
URL: https://github.com/apache/superset/issues/12566#issuecomment-764997761


   Forgive me if I am interjecting a novice question here.
   
   Since breaking changes are critical to the proposed semantic versioning scheme, does it make sense to add some additional structure / formalization around how breaking changes are identified and documented? 
   
   As I understand it, the current process relies on individual contributors adding information to UPDATING.md when merging code that results in a breaking change, and that information lives nowhere else outside the results of existing regression testing.


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

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



---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org