GitHub user xuang7 added a comment to the discussion: Skipping release 1.2.1?

Thanks for starting this discussion. I agree that 1.3.0 should be the priority, 
and I'm not proposing to split effort between the two. I'd still like to keep 
1.2.1 as a low-cost fallback for a few reasons.

1.2.0 can't be deployed today because the MinIO images are no longer available, 
and 1.2.1 addresses that issue. Its scope is relatively small: since 1.2.0, 
release/v1.2 has 50 commits touching 120 files, mostly covering the switch to 
RustFS and the same licensing fixes that 1.3.0 needs. In comparison, 
release/v1.3 has 1,189 commits touching 2,047 files, including new services 
(Jupyter, notebook migration) and modules, so its first RC and audit may take 
longer and could surface additional issues.

The extra work for 1.2.1 is also limited. Fixes land on main and are 
automatically backported to both branches, so the remaining work on the 1.2 
side is mainly resolving a few backport conflicts and cutting the RC.

My suggestion is to focus on 1.3.0 and set a decision point. If 1.3.0 can go to 
a vote within a few weeks, we could skip 1.2.1 and add a note on the download 
page directing 1.2.0 users to 1.3.0, as @zyratlo suggested. If 1.3.0 needs 
longer, I'll cut 1.2.1 RC2 so users have a working release in the meantime.

As the 1.2 release manager, I'm happy to follow the community's consensus on 
how best to proceed.

GitHub link: 
https://github.com/apache/texera/discussions/9305#discussioncomment-19405056

----
This is an automatically sent email for [email protected].
To unsubscribe, please send an email to: [email protected]

Reply via email to