hive-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Sergey Shelukhin <>
Subject Re: [DISCUSS] Making a stable release from branch 2
Date Tue, 29 Nov 2016 22:00:54 GMT
We need to figure out the versioning strategy for this that is not
hopelessly confusing.
Also, having too many fixes in master as described is a different problem,
of not releasing off master often enough.
What is to be done with master in this model?

On 16/11/29, 12:37, "Sergio Pena" <> wrote:

>Good, thanks Owen for volunteering.
>I see we have too many bugfixes, features, and improvements on the master
>A few questions:
>- How or what would be the process for cherry picking those fixes? How
>you detect which ones are stable and which not?
>- What if others contributors want some patches to be added to the next
>release? How can we prove they're stable enough to be included?
>- How can the community help on making this new branch stable? Should we
>help on triaging, cherry-picking, testing, others ideas?
>I really agree we should be careful on doing the next feature release
>Having hundred of new bugfixes and improvements on a branch makes
>to validate its quality.
>- Sergio
>On Tue, Nov 29, 2016 at 12:31 PM, Owen O'Malley <>
>> Hi all,
>>    I'd like to volunteer as a Release Manager for making a stable
>> release from branch 2. However, rather than starting with master, I'll
>> the 2.1 release and cherry pick fixes and features with a focus on a
>> release and picking features that have been tested at scale. Testing a
>> release at scale is hard, time consuming, and resource intensive, but I
>> think that having a stable release with some of the great features that
>> we've put into Hive 2 will help drive adoption of the new branch.
>> Thanks,
>>    Owen

View raw message