Hi folks,
Hive-4.0 branch is a relative stable branch, so backport some fix
and releasing a stable minor version based on Hive-4.0 is more reasonable to
me. But as Stamatis said, `It's been already 4 months since the release of Hive
4.0.0`, I also think 4 months is a little long for waiting a minor release. The
reason for not releasing the version for a long time, is mainly what Denys said
`many major bug fixes are simply not being reviewed on time.`
IMHO, we need to encourage more committers/contributors to take
part in Hive project, including code review, doc/conf supplement, performance
test and so on. Meanwhile, the minor release cycle should be less 3 months, and
then we can attract more people to test the version and report issues as soon
as possible, and i think the real users test are more important.
Thanks,
Butao Zhang
---- Replied Message ----
| From | Zhihua Deng<[email protected]> |
| Date | 8/1/2024 11:47 |
| To | <[email protected]> |
| Subject | Re: [DISCUS] Plan the next Hive release |
Hi All,
Hive 4.0.1 Overview:
Now there are six Hive issues that tagged with hive-4.0.1-must left un-merged
to branch-4.0, most of them are resolved on the master. Regarding to TEZ-4557,
a workaround in Hive is to add the missing jars to the hive.aux.jars.path,
which is acceptable, from my perspective, I would like to skip including the
TEZ-4557 in this release.
I like the idea of cherry-picking only critical bugs and important improvements
based on one major release, it can introduce less surprises, stable updates and
learning cost savings. To reduce maintenance burden for the community, I think
we can take some rules. For instance, Any release branch would be freeze after
some time or some minors released(like
the branch-4.x could be expired two years latter or after three minor releases).
Regards,
Zhihua
On 2024/07/31 11:30:25 Denys Kuzmenko wrote:
Hi Stamatis,
`It's been already 4 months since the release of Hive 4.0.0`. That's true,
Zhihua can give a more detailed view of things, however, the main reason is
that it took a while to resolve the identified bugs.
ATM the only blocking item is TEZ-4557, which might not be available until
September, so we might decide to skip it or try to workaround in Hive if
possible.
Hive-4.0 branch was well-tested by the community and is in a much better shape
than the master.
For Hive-4.1 release plan was to migrate to JDK-17+ which might take more time.
`Commit and release always from master.` I don't think that's a good idea as it
won't solve the mentioned here reason for the change: increase release cadence
I feel the current problem is the lack of support from committers, as many
major bug fixes are simply not being reviewed on time.
Regards,
Denys
