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? > >
