GitHub user Yicong-Huang added a comment to the discussion: Skipping release 1.2.1?
I also still suggest we keep doing for both. For a few reasons: 1. v1.2.1 and v1.3.0 are quite different, as @xuang7 mentioned, v1.3 branch has 1000+ commits with new features. The existing users of v1.2.0's ability to upgrade to future 1.3.0 is unknown, and that may have possible delays caused by the new features (to fix them). Even if v1.3.0 can be ready for vote soon, it does not mean it will be easier to deploy and migrate, compared to v1.2.1. 2. The effort to fix v1.2 branch is not too much IMO. The same PRs are targeting to both release branches, and some fixes if needed on v1.2 should be a direct change without too much conflicts. I hope I am not underestimating @xuang7 's work on v1.2 after 1.2.0 release. For the release cadency, that was [discussed](https://lists.apache.org/thread/yydt24r72vosbfbycnp43q3slkngvmsh?utm_source=chatgpt.com) and [voted](https://lists.apache.org/thread/5cphypqlzgyrc5s5bqyj1q0p7lvpxms0?utm_source=chatgpt.com) on dev list. We should put this on the website if that's the concern. One thing that is not clear from the current release cadency is the support length of a release line. We could start a discussion on that. However, until v1.3.0 is released, v1.2.0 is our latest release, and I think we have a responsibility to fix issues in that release line and publish v1.2.1 as soon as possible. Otherwise, we’re effectively abandoning users on v1.2.0 and forcing them to upgrade just to get bug fixes. GitHub link: https://github.com/apache/texera/discussions/9305#discussioncomment-19405569 ---- This is an automatically sent email for [email protected]. To unsubscribe, please send an email to: [email protected]
