Re: Why storm have so many version lines

[沈光辉]

Got it, Thank you all~

> 在 2019年7月23日，13:49，Stig Rohde Døssing  写道：
> 
> 2.0.0 is the latest version, 1.2.3 is a maintenance release for the 1.x line. 
> All fixes in 1.2.3 are also in 2.0.0.
> 
> I think the comparison to Python is fine, but the intent is not that there 
> are benefits to using 1.x over 2.x, as this would mean that we introduced 
> regressions. It's more a question of migration effort for existing 
> code/clusters.
> 
> Storm's release strategy is not actually that different from Kafka's. If you 
> look at Kafka's release history https://kafka.apache.org/downloads 
> , you can see that 0.11.0.3 released 
> after 1.0.0, so at one point they also had multiple active release lines. 
> 
> The reason for us to release new versions in 1.x while also releasing 2.x 
> versions is that migrating 1.x clusters to 2.x may require some extra work 
> compared to a minor version upgrade. We don't want to leave 1.x users without 
> support while they figure out how to migrate to 2.x, so we release new 1.x 
> versions for a while.  
> 
> If you're writing new code, the best choice is likely to target the latest 
> version, unless you know of a good reason (e.g. some critical regression in 
> the new releases) to use the older version. If you are being forced into 
> using the older version by a regression, I think we'd be happy to hear about 
> it so it can be fixed.
> 
> Den tir. 23. jul. 2019 kl. 03.53 skrev Andrew Xor 
> mailto:andreas.gramme...@gmail.com>>:
> Hi,
> 
> I think you are missing the point here - Storm 1.2.x is fundamentally 
> different than Storm 2.x; to see why please see the documents Stig suggested 
> above. You can think of Storm 1.2.x as Python 2 and Storm 2.x as Python 3 - 
> both are supported but are fundamentally different and using either needs 
> understanding of their prons and cons. Although, if it's a new deployment I'd 
> highly recommend using Storm 2.0 but depending on your libraries, existing 
> code, and experience I cannot provide a definite answer.
> 
> Hope this helps...
> 
> A.
> 
> On Tue, Jul 23, 2019 at 4:19 AM 沈光辉  > wrote:
> Thanks for your reply. Then another question comes, for now which is the 
> ‘latest’ version, storm-2.0.0 or storm-1.2.3? 2.0.0 seems the largest number 
> which always means latest version in other open source mid-ware, but 1.2.3 
> was just released serval days ago?  
> 
> What I meant may be to some extend a blind alley, but I am really confused is 
> 1.2.3 or 2.0.0  suggested for a new production?  Comparing with apache kafka, 
> it’s much easier to choose because it has only one version line, see 
> https://kafka.apache.org/downloads#2.3.0 
>  which means it’s easy to choose a 
> suitable one
> 
> 
>> 在 2019年7月22日，22:13，Stig Rohde Døssing > > 写道：
>> 
>> Hi,
>> 
>> Most of these version lines aren't active. The currently maintained lines 
>> are 1.2.x and 2.0.0. 
>> 
>> Regarding the difference between 1.x and 2.x, please see 
>> https://storm.apache.org/2019/05/30/storm200-released.html 
>> . You can also 
>> go look at the release notes here 
>> https://www.apache.org/dist/storm/apache-storm-2.0.0/RELEASE_NOTES.html 
>>  
>> (note that these contain some changes that were also in later 1.2.x releases)
>> 
>> I think unless you hear otherwise, the suggested version is the latest 
>> version. We don't release Storm unless we think it's production ready.
>> 
>> Den man. 22. jul. 2019 kl. 13.52 skrev 沈光辉 > >:
>> Hi，
>> 
>> I’m wonder what is the diff between storm-1.2.x and storm 2.0.0? I know the 
>> several important features of storm-2.0.0.
>> However, if I now need to choose a version to apply into production, which 
>> version is suggested? I’m wondering why storm-1.2.x and storm-0.x even 
>> storm-2.x all kept in upgrading? 
>> 
>> Thanks~
> 

Re: Why storm have so many version lines

[Stig Rohde Døssing]

2.0.0 is the latest version, 1.2.3 is a maintenance release for the 1.x
line. All fixes in 1.2.3 are also in 2.0.0.

I think the comparison to Python is fine, but the intent is not that there
are benefits to using 1.x over 2.x, as this would mean that we introduced
regressions. It's more a question of migration effort for existing
code/clusters.

Storm's release strategy is not actually that different from Kafka's. If
you look at Kafka's release history https://kafka.apache.org/downloads, you
can see that 0.11.0.3 released after 1.0.0, so at one point they also had
multiple active release lines.

The reason for us to release new versions in 1.x while also releasing 2.x
versions is that migrating 1.x clusters to 2.x may require some extra work
compared to a minor version upgrade. We don't want to leave 1.x users
without support while they figure out how to migrate to 2.x, so we release
new 1.x versions for a while.

If you're writing new code, the best choice is likely to target the latest
version, unless you know of a good reason (e.g. some critical regression in
the new releases) to use the older version. If you are being forced into
using the older version by a regression, I think we'd be happy to hear
about it so it can be fixed.

Den tir. 23. jul. 2019 kl. 03.53 skrev Andrew Xor <
andreas.gramme...@gmail.com>:

> Hi,
>
> I think you are missing the point here - Storm 1.2.x is fundamentally
> different than Storm 2.x; to see why please see the documents Stig
> suggested above. You can think of Storm 1.2.x as Python 2 and Storm 2.x as
> Python 3 - both are supported but are fundamentally different and using
> either needs understanding of their prons and cons. Although, if it's a new
> deployment I'd highly recommend using Storm 2.0 but depending on your
> libraries, existing code, and experience I cannot provide a definite answer.
>
> Hope this helps...
>
> A.
>
> On Tue, Jul 23, 2019 at 4:19 AM 沈光辉  wrote:
>
>> Thanks for your reply. Then another question comes, for now which is the
>> ‘latest’ version, storm-2.0.0 or storm-1.2.3? 2.0.0 seems the largest
>> number which always means latest version in other open source mid-ware, but
>> 1.2.3 was just released serval days ago?
>>
>> What I meant may be to some extend a blind alley, but I am really
>> confused is 1.2.3 or 2.0.0  suggested for a new production?  Comparing with
>> apache kafka, it’s much easier to choose because it has only one version
>> line, see https://kafka.apache.org/downloads#2.3.0 which means it’s easy
>> to choose a suitable one
>>
>>
>> 在 2019年7月22日，22:13，Stig Rohde Døssing  写道：
>>
>> Hi,
>>
>> Most of these version lines aren't active. The currently maintained lines
>> are 1.2.x and 2.0.0.
>>
>> Regarding the difference between 1.x and 2.x, please see
>> https://storm.apache.org/2019/05/30/storm200-released.html. You can also
>> go look at the release notes here
>> https://www.apache.org/dist/storm/apache-storm-2.0.0/RELEASE_NOTES.html
>> (note that these contain some changes that were also in later 1.2.x
>> releases)
>>
>> I think unless you hear otherwise, the suggested version is the latest
>> version. We don't release Storm unless we think it's production ready.
>>
>> Den man. 22. jul. 2019 kl. 13.52 skrev 沈光辉 :
>>
>>> Hi，
>>>
>>> I’m wonder what is the diff between storm-1.2.x and storm 2.0.0? I know
>>> the several important features of storm-2.0.0.
>>> However, if I now need to choose a version to apply into production,
>>> which version is suggested? I’m wondering why storm-1.2.x and storm-0.x
>>> even storm-2.x all kept in upgrading?
>>>
>>> Thanks~
>>>
>>
>>

Re: Why storm have so many version lines

[Andrew Xor]

Hi,

I think you are missing the point here - Storm 1.2.x is fundamentally
different than Storm 2.x; to see why please see the documents Stig
suggested above. You can think of Storm 1.2.x as Python 2 and Storm 2.x as
Python 3 - both are supported but are fundamentally different and using
either needs understanding of their prons and cons. Although, if it's a new
deployment I'd highly recommend using Storm 2.0 but depending on your
libraries, existing code, and experience I cannot provide a definite answer.

Hope this helps...

A.

On Tue, Jul 23, 2019 at 4:19 AM 沈光辉  wrote:

> Thanks for your reply. Then another question comes, for now which is the
> ‘latest’ version, storm-2.0.0 or storm-1.2.3? 2.0.0 seems the largest
> number which always means latest version in other open source mid-ware, but
> 1.2.3 was just released serval days ago?
>
> What I meant may be to some extend a blind alley, but I am really confused
> is 1.2.3 or 2.0.0  suggested for a new production?  Comparing with apache
> kafka, it’s much easier to choose because it has only one version line, see
> https://kafka.apache.org/downloads#2.3.0 which means it’s easy to choose
> a suitable one
>
>
> 在 2019年7月22日，22:13，Stig Rohde Døssing  写道：
>
> Hi,
>
> Most of these version lines aren't active. The currently maintained lines
> are 1.2.x and 2.0.0.
>
> Regarding the difference between 1.x and 2.x, please see
> https://storm.apache.org/2019/05/30/storm200-released.html. You can also
> go look at the release notes here
> https://www.apache.org/dist/storm/apache-storm-2.0.0/RELEASE_NOTES.html
> (note that these contain some changes that were also in later 1.2.x
> releases)
>
> I think unless you hear otherwise, the suggested version is the latest
> version. We don't release Storm unless we think it's production ready.
>
> Den man. 22. jul. 2019 kl. 13.52 skrev 沈光辉 :
>
>> Hi，
>>
>> I’m wonder what is the diff between storm-1.2.x and storm 2.0.0? I know
>> the several important features of storm-2.0.0.
>> However, if I now need to choose a version to apply into production,
>> which version is suggested? I’m wondering why storm-1.2.x and storm-0.x
>> even storm-2.x all kept in upgrading?
>>
>> Thanks~
>>
>
>

Re: Why storm have so many version lines

[沈光辉]

Thanks for your reply. Then another question comes, for now which is the 
‘latest’ version, storm-2.0.0 or storm-1.2.3? 2.0.0 seems the largest number 
which always means latest version in other open source mid-ware, but 1.2.3 was 
just released serval days ago?  

What I meant may be to some extend a blind alley, but I am really confused is 
1.2.3 or 2.0.0  suggested for a new production?  Comparing with apache kafka, 
it’s much easier to choose because it has only one version line, see 
https://kafka.apache.org/downloads#2.3.0 
 which means it’s easy to choose a 
suitable one


> 在 2019年7月22日，22:13，Stig Rohde Døssing  写道：
> 
> Hi,
> 
> Most of these version lines aren't active. The currently maintained lines are 
> 1.2.x and 2.0.0. 
> 
> Regarding the difference between 1.x and 2.x, please see 
> https://storm.apache.org/2019/05/30/storm200-released.html 
> . You can also go 
> look at the release notes here 
> https://www.apache.org/dist/storm/apache-storm-2.0.0/RELEASE_NOTES.html 
>  
> (note that these contain some changes that were also in later 1.2.x releases)
> 
> I think unless you hear otherwise, the suggested version is the latest 
> version. We don't release Storm unless we think it's production ready.
> 
> Den man. 22. jul. 2019 kl. 13.52 skrev 沈光辉  >:
> Hi，
> 
> I’m wonder what is the diff between storm-1.2.x and storm 2.0.0? I know the 
> several important features of storm-2.0.0.
> However, if I now need to choose a version to apply into production, which 
> version is suggested? I’m wondering why storm-1.2.x and storm-0.x even 
> storm-2.x all kept in upgrading? 
> 
> Thanks~

Re: Why storm have so many version lines

[Stig Rohde Døssing]

Hi,

Most of these version lines aren't active. The currently maintained lines
are 1.2.x and 2.0.0.

Regarding the difference between 1.x and 2.x, please see
https://storm.apache.org/2019/05/30/storm200-released.html. You can also go
look at the release notes here
https://www.apache.org/dist/storm/apache-storm-2.0.0/RELEASE_NOTES.html
(note that these contain some changes that were also in later 1.2.x
releases)

I think unless you hear otherwise, the suggested version is the latest
version. We don't release Storm unless we think it's production ready.

Den man. 22. jul. 2019 kl. 13.52 skrev 沈光辉 :

> Hi，
>
> I’m wonder what is the diff between storm-1.2.x and storm 2.0.0? I know
> the several important features of storm-2.0.0.
> However, if I now need to choose a version to apply into production, which
> version is suggested? I’m wondering why storm-1.2.x and storm-0.x even
> storm-2.x all kept in upgrading?
>
> Thanks~
>