Thanks Stig. I will look into it.

> On Jul 26, 2019, at 3:06 PM, Stig Rohde Døssing <[email protected]> 
> wrote:
> 
> I think ideally we've been trying for semver, but it's been pretty loose,
> e.g. there were breaking changes in one of the 1.2.x releases for
> storm-kafka-client. I don't know what rules we've actually been using, if
> any.
> 
> Semver for binary compatibility would probably be a good rule of thumb.
> 
> Den fre. 26. jul. 2019 kl. 20.01 skrev Ethan Li <[email protected]>:
> 
>> 
>> Stig,
>> 
>> Do you know what’s the versioning standard we have been following (to
>> determine a 2.0.1 release or 2.1.0 release) ?
>> 
>> 
>>> On Jul 26, 2019, at 12:26 PM, Stig Rohde Døssing <[email protected]>
>> wrote:
>>> 
>>> Sounds great, thanks Ethan.
>>> 
>>> Den fre. 26. jul. 2019 kl. 19.16 skrev Ethan Li <
>> [email protected]>:
>>> 
>>>> It’s good idea to do more frequent release. I can run the next release.
>>>> 
>>>> I will take a look at both PRs. Other than that, I think we should also
>>>> get https://github.com/apache/storm/pull/3093 <
>>>> https://github.com/apache/storm/pull/3093>  in the new release.
>>>> 
>>>> 
>>>>> On Jul 26, 2019, at 11:58 AM, Stig Rohde Døssing <
>> [email protected]>
>>>> wrote:
>>>>> 
>>>>> Hi,
>>>>> 
>>>>> I think we've talked about more frequent releases before. Releasing new
>>>>> versions every few months means people don't have to wait long for
>> fixes
>>>> to
>>>>> get out, and smaller releases are probably also easier for users to get
>>>> to
>>>>> grips with (the fix list for 2.0.0 is enormous).
>>>>> 
>>>>> With that in mind, I think we should start looking at the next 2.x
>>>> release
>>>>> (2.0.1 or 2.1.0?), since it's been a couple of months since 2.0.0
>>>> released.
>>>>> The fix list would be
>>>>> 
>>>> 
>> https://issues.apache.org/jira/issues/?jql=project%20%3D%20STORM%20AND%20fixVersion%20%3D%202.0.1
>>>>> .
>>>>> 
>>>>> Govind and Ethan have offered to run the next release, and help
>> validate
>>>>> our release process guidelines. Would one of you have time to work on a
>>>>> release in the near future?
>>>>> 
>>>>> It would be good to take a look at currently open PRs and decide which
>> we
>>>>> feel need to get merged before the next release.
>>>>> 
>>>>> I would like to see at least https://github.com/apache/storm/pull/2990
>>>>> merged
>>>>> 
>>>>> https://github.com/apache/storm/pull/2878 seems like it's close to be
>>>>> mergeable too?
>>>> 
>>>> 
>> 
>> 

Reply via email to