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/10/14 03:54:00 UTC

[GitHub] [superset] rusackas commented on issue #17081: [SIP-74] Superset 2.0 Breaking Changes

rusackas commented on issue #17081:
URL: https://github.com/apache/superset/issues/17081#issuecomment-942921908


   Thanks for kicking this off! I, for one, am enamored with the idea of NOT adding any big projects or committing to any huge bodies of work to pull this off, but rather just removing deprecated code paths, reducing feature flag complexity, and just cleaning house. We need to get over the hump of 2.0, and use it as practice in order to better plan for new initiatives for 3.0+ with reduced risk.
   
   It may also be worth mentioning that 2.0 has a huge emotional weight to it, almost as much as 1.0. But if we follow semver practices, we shouldn't be so afraid of major version bumps, in my opinion. When we complete the monorepo migration (new SIP pending), for example, we may see major version bumps much more often due to things like plugin deprecations or similar migration efforts.
   
   As for the tasks on the board, I think each should indeed be discussed individually to gather consensus on each. This could happen by converting the notes to Issues and discussing there, or taking it to a discussion thread on the dev@ list in hope of reaching lazy consensus.
   
   If anyone here does not have committer access to add suggestions to the Project, please feel free to add them in a comment here for consideration, and we can add them if there's a reasonable degree of alignment/interest.


-- 
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: notifications-unsubscribe@superset.apache.org

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