Github user HeartSaVioR commented on the issue:

    https://github.com/apache/storm/pull/1790
  
    @ohadedel 
    I don't know the intention of 'equivalent' (implementation, or result), but 
if it means only the result, the result of twos would be similar if you think 
far. They provide uniform distribution.
    
    Regarding stable version, personally I had been thinking v1.0.2 is fairly 
stable since we fixed numerous issues on v1.0.1 and v1.0.2, and after v1.0.2 
there're no performance-affecting critical bugs reported before this one.
    
    Below links point the issues for next bugfix (v1.0.3) and next minor 
(v1.1.0):
    * v1.0.3: 
https://issues.apache.org/jira/issues/?jql=fixVersion%20%3D%201.0.3%20AND%20project%20%3D%20STORM%20order%20by%20priority
    
    * v1.1.0: 
https://issues.apache.org/jira/issues/?jql=fixVersion%20%3D%201.1.0%20AND%20fixVersion%20not%20in%20(1.0.0%2C%201.0.1%2C%201.0.2)%20AND%20project%20%3D%20STORM%20order%20by%20priority
    
    There's no 'completely stable' in every projects since we're adding the 
code anyway and no one ensure there's no bug on that version. If the critical 
bugs are reported well from the community and the community reacts it faster 
and release the new version timely, IMHO it is another kind of stable.


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Reply via email to