samza-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Martin Kleppmann <mar...@kleppmann.com>
Subject Re: [DISCUSS] Cutting an 0.8 branch
Date Tue, 21 Oct 2014 11:03:50 GMT
+1 on making a branch. IMHO SAMZA-354 is a must-have for the 0.8 release, SAMZA-310 and SAMZA-226
are nice-to-haves. If they don't make it into 0.8, we can still do a 0.8.1 release soon afterwards.
I think it would be good to get in a habit of making frequent incremental releases anyway.

Martin

On 20 Oct 2014, at 17:27, Roger Hoover <roger.hoover@gmail.com> wrote:

> Yan,
> 
> I think SAMZA-226 would be a really nice usability improvement if you can
> get it in.  Thanks for taking it on.
> 
> Cheers,
> 
> Roger
> 
> On Mon, Oct 20, 2014 at 9:23 AM, Yan Fang <yanfang724@gmail.com> wrote:
> 
>> SAMZA-310 will be done in 1~2 days depending on my time availability.
>> 
>> also think of solving SAMZA-226 before release 0.8 because it's related to
>> the kv store, which is a big improvement in the coming release.
>> 
>> I am fine with cutting an 0.8 branch as we can back port.
>> 
>> Cheers,
>> 
>> Fang, Yan
>> yanfang724@gmail.com
>> +1 (206) 849-4108
>> 
>> On Mon, Oct 20, 2014 at 9:01 AM, Chris Riccomini <
>> criccomini@linkedin.com.invalid> wrote:
>> 
>>> Hey Guys,
>>> 
>>> With the RocksDB commit from Naveen, I think we're closing in on an 0.8
>>> release.
>>> 
>>> The last remaining JIRA that I'd like to resolve is SAMZA-354. SAMZA-310
>>> would be nice to get in as well, but I don't think it's a blocker.
>>> 
>>> Does anyone have any other JIRAs that they think should be resolved
>> before
>>> we release 0.8? If not, I'll cut an 0.8 branch, and we can back port
>>> SAMZA-354 (and SAMZA-310 if it is done) when they're committed. The
>>> motivation for cutting the branch now is that I'm starting work on the
>>> ConfigStream stuff, and I don't want to destabilize 0.8 with the rather
>>> large changes that will come.
>>> 
>>> Cheers,
>>> Chris
>>> 
>> 


Mime
View raw message