Given that there are currently only a few relatively minor fixes, I think it would be appropriate to set a specific branch-cutting date.
How about June 25, 2025, at UTC+8 (East Eighth Zone Time)? After this date, if there are still any code that needs to be fixed on version 4.1.0, we can solve it through cherry-pick. Thanks, Butao Zhang ---- Replied Message ---- | From | Ayush Saxena<ayush...@gmail.com> | | Date | 6/23/2025 14:09 | | To | <dev@hive.apache.org> | | Subject | Re: [DISCUSS] Hive 4.1.x release | Do we consider the two REST catalog issues as blockers? To me, they seem more like improvements that we could potentially defer, especially if the other item gets addressed. Denys — is HIVE-28744 a regression, or was it present in earlier releases too? The other two do appear to be blockers. Personally, I still feel we should move ahead with branching for Hive 4.1.0 and treat this as a code freeze point. We can cherry-pick these, or any other relevant fixes, into the branch afterward — otherwise, code will continue to evolve and drift. Just my 2 cents. – Ayush On Mon, 23 Jun 2025 at 10:50, Denys Kuzmenko <dkuzme...@apache.org> wrote: Currently, at least three items remain incomplete: https://issues.apache.org/jira/issues/?jql=project%20%3D%20HIVE%20AND%20resolution%20%3D%20Unresolved%20AND%20labels%20%3D%20hive-4.1.0-must%20ORDER%20BY%20updated%20DESC%2C%20priority%20DESC
