You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@samza.apache.org by Chris Riccomini <cr...@linkedin.com.INVALID> on 2014/10/20 18:01:28 UTC
[DISCUSS] Cutting an 0.8 branch
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
Re: [DISCUSS] Cutting an 0.8 branch
Posted by Chris Riccomini <cr...@linkedin.com.INVALID>.
Hey Martin,
Sounds good to me. We should update hello-samza/latest if we do this, too.
Cheers,
Chris
On 11/4/14 2:25 AM, "Martin Kleppmann" <ma...@kleppmann.com> wrote:
>Now that we have the branch, should we update gradle.properties on the
>master branch and set the version number to 0.9.0-SNAPSHOT? That way,
>people who are developing against both the 0.8.0 branch and the master
>branch can keep both versions of Samza in their local Maven repos.
>
>Martin
>
>On 23 Oct 2014, at 02:16, Chris Riccomini
><cr...@linkedin.com.INVALID> wrote:
>
>> Hey Guys,
>>
>> I've cut an 0.8.0 branch:
>>
>>
>>
>>https://git-wip-us.apache.org/repos/asf?p=incubator-samza.git;a=shortlog;
>>h=
>> refs/heads/0.8.0
>>
>>
>> Here are the current open tickets:
>>
>>
>>
>>https://issues.apache.org/jira/issues/?jql=project%20%3D%20SAMZA%20AND%20
>>re
>>
>>solution%20%3D%20Unresolved%20AND%20fixVersion%20%3D%200.8.0%20ORDER%20BY
>>%2
>> 0priority%20DESC
>>
>>
>> I opened up one other issue (SAMZA-443), which I think is worth fixing
>>in
>> 0.8.0 as well.
>>
>> Cheers,
>> Chris
>>
>> On 10/21/14 4:03 AM, "Martin Kleppmann" <ma...@kleppmann.com> wrote:
>>
>>> +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 <ro...@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 <ya...@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
>>>>>>
>>>>>
>>>
>>
>
Re: [DISCUSS] Cutting an 0.8 branch
Posted by Martin Kleppmann <ma...@kleppmann.com>.
Now that we have the branch, should we update gradle.properties on the master branch and set the version number to 0.9.0-SNAPSHOT? That way, people who are developing against both the 0.8.0 branch and the master branch can keep both versions of Samza in their local Maven repos.
Martin
On 23 Oct 2014, at 02:16, Chris Riccomini <cr...@linkedin.com.INVALID> wrote:
> Hey Guys,
>
> I've cut an 0.8.0 branch:
>
>
> https://git-wip-us.apache.org/repos/asf?p=incubator-samza.git;a=shortlog;h=
> refs/heads/0.8.0
>
>
> Here are the current open tickets:
>
>
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20SAMZA%20AND%20re
> solution%20%3D%20Unresolved%20AND%20fixVersion%20%3D%200.8.0%20ORDER%20BY%2
> 0priority%20DESC
>
>
> I opened up one other issue (SAMZA-443), which I think is worth fixing in
> 0.8.0 as well.
>
> Cheers,
> Chris
>
> On 10/21/14 4:03 AM, "Martin Kleppmann" <ma...@kleppmann.com> wrote:
>
>> +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 <ro...@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 <ya...@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
>>>>>
>>>>
>>
>
Re: [DISCUSS] Cutting an 0.8 branch
Posted by Chris Riccomini <cr...@linkedin.com.INVALID>.
Hey Guys,
I've cut an 0.8.0 branch:
https://git-wip-us.apache.org/repos/asf?p=incubator-samza.git;a=shortlog;h=
refs/heads/0.8.0
Here are the current open tickets:
https://issues.apache.org/jira/issues/?jql=project%20%3D%20SAMZA%20AND%20re
solution%20%3D%20Unresolved%20AND%20fixVersion%20%3D%200.8.0%20ORDER%20BY%2
0priority%20DESC
I opened up one other issue (SAMZA-443), which I think is worth fixing in
0.8.0 as well.
Cheers,
Chris
On 10/21/14 4:03 AM, "Martin Kleppmann" <ma...@kleppmann.com> wrote:
>+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 <ro...@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 <ya...@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
>>>>
>>>
>
Re: [DISCUSS] Cutting an 0.8 branch
Posted by Martin Kleppmann <ma...@kleppmann.com>.
+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 <ro...@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 <ya...@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
>>>
>>
Re: [DISCUSS] Cutting an 0.8 branch
Posted by Roger Hoover <ro...@gmail.com>.
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 <ya...@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
> >
>
Re: [DISCUSS] Cutting an 0.8 branch
Posted by Yan Fang <ya...@gmail.com>.
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
>