I agree with the version bump and also with the strategy to have a beta 
release. 




Thanks

Parth
—
Sent from Mailbox

On Thu, Aug 28, 2014 at 2:59 PM, Derek Dagit <der...@yahoo-inc.com> wrote:

> I am supportive.
> I think it makes sense to move to 0.10.0 because of the significance of the 
> changes.
> -- 
> Derek
> On 8/28/14, 15:34, P.Taylor Goetz wrote:
>> I’d like to gather community feedback for the next two releases of Apache 
>> Storm.
>>
>> 0.9.3-incubating will be our next release. Please indicate (by JIRA ticket 
>> ID) which bug fixes and/or new features you would like to be considered for 
>> inclusion in the next release. If there is not an existing for a particular 
>> issue or feature, please consider adding one.
>>
>> For the next and subsequent releases, we will be using a slightly different 
>> approach than what we did in the past. Instead of voting right away on a 
>> build, we will make one or more “unofficial” release candidate builds 
>> available prior to voting on an official release. This will give the Apache 
>> Storm community more time to discuss, evaluate, identify and fix potential 
>> issues before the official release. This should enable us to ensure the 
>> final release is as bug free as possible.
>>
>> Apache Storm 0.10.0 (STORM-216)
>> As some of you are aware, the engineering team at Yahoo! has done a lot of 
>> work to bring security and multi-tenancy to Storm, and has contributed that 
>> work back to the community. Over the past few months we have been in the 
>> process of enhancing and syncing that work  with the master branch in a 
>> separate branch labeled “security.” That work is now nearing completion, and 
>> I would like us to consider merging it into master after the 0.9.3 release. 
>> Since the security work includes a large number of changes and enhancements, 
>> I propose we bump the version number to 0.10.0 for the first release to 
>> include those features.
>>
>> More information about the security branch can be found in this pull request 
>> [1], as well as the SECURITY.md file in the security branch [2]. I also 
>> discussed it in a blog post [3] on the Hortonworks website. Please feel free 
>> to direct any comments or questions about the security branch to the mailing 
>> list.
>>
>> Similar to the process we’ll follow for 0.9.3, we plan to make several 
>> unofficial “development” builds available for those who would like to help 
>> with testing the new security features.
>>
>>
>> -Taylor
>>
>> [1] https://github.com/apache/incubator-storm/pull/121
>> [2] https://github.com/apache/incubator-storm/blob/security/SECURITY.md
>> [3] http://hortonworks.com/blog/the-future-of-apache-storm/
>>
-- 
CONFIDENTIALITY NOTICE
NOTICE: This message is intended for the use of the individual or entity to 
which it is addressed and may contain information that is confidential, 
privileged and exempt from disclosure under applicable law. If the reader 
of this message is not the intended recipient, you are hereby notified that 
any printing, copying, dissemination, distribution, disclosure or 
forwarding of this communication is strictly prohibited. If you have 
received this communication in error, please contact the sender immediately 
and delete it from your system. Thank You.

Reply via email to