Supported Version Life Cycle #24813
Replies: 3 comments 3 replies
-
Hi @sebastianliebscher. We were just discussing this internally! We have a meeting scheduled for after 3.0 to review our release process and one topic is to establish a clear definition of supported releases, release cadence, documentation, etc. Thank you for this table, it will definitely help with discussions and it may help others while we wait for these definitions. I think it's fair to say we are currently only supporting 3.0 and 2.1 and there's no concept of Limited Support. A more accurate table would be:
CVEs for each of the releases above. Pinging some folks who might be interested in this discussion: @rusackas @eschutho @john-bodley @dpgaspar |
Beta Was this translation helpful? Give feedback.
-
Indeed! As @michael-s-molina we're definitely looking forward to formalizing this, via the Release Strategy meetings (which you're welcome to join if you'd like), and probably Town Hall (which you can also join). These are both available on the community calendar. Once we get it all ironed out, it should be on the docs and/or wiki, and probably on that calendar if we go with time-driven releases. |
Beta Was this translation helpful? Give feedback.
-
Have there been any updates on this? I don't see a formal end of support listed in the docs as was discussed in this thread. Thanks! |
Beta Was this translation helpful? Give feedback.
-
Hi Superset Community, the Version Life Cycle from Airflow inspired me to put this together, as I couldn't find any relevant info in this compressed format so far. If I missed any relevant info, please post them here. Maybe this can be further fed with information (as I assumed a lot here after reading the dev mailing list and GitHub comments) and even added to the official documentation or the GitHub Wiki.
Beta Was this translation helpful? Give feedback.
All reactions