Hello HIVE Dev, I would like to discuss/propose incremental and cadence predictable process for HIVE releases. https://hive.apache.org/general/downloads/
Currently, our releases have a very random span in between, and those have sometimes caused problems like- 1. All downstream and end users have unpredictable schedules because of upstream. 2. More chances of regression issues when there is an unplanned release date. As developers and release managers have to rush, this prevents us from focusing on having a proper regression-free release. I would like to propose a branch cut twice a year to have two strict releases yearly. It would make release cadence predictable for end users and bring some disciplinary schedules for all users, including downstream projects. Advantages of this approach- 1. If we pin a branch cut date, features can be prioritized better so that no half-baked stuff goes into release. 2. Such Incremental release will help in better regression and reduce the burden from release management activity( result is reduced issues and problems with quality). It will eventually help to streamline release management activity. Let me know your thoughts. Thanks, Kirti
