+1

One other issue I'd add as a nice-to-have but not a blocker for the first 
release is SAMZA-6, the performance test suite. For the 2nd and subsequent 
releases it'd be really good to have a more systematic method of ensuring we 
haven't had performance regressions slip in along the way.

As the key shows this is a very old ticket -- if this is still outstanding and 
no one has half-completed work sitting in a branch somewhere I'll take it. 

Garry

-----Original Message-----
From: Chris Riccomini [mailto:[email protected]] 
Sent: 21 March 2014 03:36
To: [email protected]
Subject: Re: Stabilizing Samza 0.7.0

Hey Martin,

Good point. One other one I'd like to get done is SAMZA-199, which I just 
opened. We can't really call our release a release unless it's in Apache's 
Maven repo. :)

Cheers,
Chris

On 3/20/14 5:38 PM, "Martin Kleppmann" <[email protected]> wrote:

>+1. I would add to the list:
>
>SAMZA-7 (docs)
>SAMZA-33 (docs)
>SAMZA-35 (docs)
>SAMZA-165 (docs)
>SAMZA-193
>SAMZA-197
>
>I put the docs there because hopefully the release will get us some 
>wider attention, and I'd like us to be able to greet new people with 
>accurate docs :) I've assigned them to myself for now, but if anyone 
>else wants to take on some of the docs-editing, please feel free to grab a 
>ticket.
>
>Martin
>
>On 20 Mar 2014, at 21:25, Chris Riccomini <[email protected]> wrote:
>> Hey Guys,
>> 
>> I'd like to propose cutting an 0.7.0 release branch for Samza. The 
>>goal of cutting the branch is to get everything stable for an Apache 
>>Incubator release.
>> 
>> Stuff that I think needs to be done for 0.7.0:
>> 
>>  * SAMZA-174
>>  * SAMZA-178
>>  * SAMZA-179
>>  * SAMZA-180
>>  * SAMZA-185 (Yan's issue)
>> 
>> In addition, we've got some folks internally using trunk to run code, 
>>and they're still discovering bugs here and there. I'd like to move 
>>them over to the 0.7.0 branch. When I see their code running stable 
>>for a few weeks, I think we should be good to go.
>> 
>> Thoughts?
>> 
>> Cheers,
>> Chris
>


-----
No virus found in this message.
Checked by AVG - www.avg.com
Version: 2014.0.4259 / Virus Database: 3722/7236 - Release Date: 03/23/14

Reply via email to