I would like to see STORM-1190, STORM-1155, STORM-1198, STORM-1196, STORM-885,
STORM-876, STORM-1145, STORM-831, and STORM-874 added to the list.
Some of them are more important then others but they are all things I would
like to see in a 0.11.0 release.
On a side note I don't think the beta releases have been helpful. I would much
rather just have a 0.11.0 go to 0.11.1 ... instead of 0.11.0-beta1,
0.11.0-beta2. To me the beta label is not that helpful, but it is not that big
of a deal for me.
I also would like to see the 0.11 release tied to the plan for the JStorm
merger. If we don't tie them together there can be code that does not make it
into 0.11, but could make it into a 0.12 that will immediately be caught up in
the merger, that could take a long time to complete. I mostly want us to be
very transparent about what is likely to happen after 0.11 is released. So if
someone has a feature that is close to getting something in to 0.11 that they
speak up here instead of just deciding to wait for a 0.12 release.
- Bobby
On Wednesday, November 11, 2015 6:32 AM, John Fang
<[email protected]> wrote:
Totally agree， it's great to accelerate the release speed. it is better
release one official version within 3 months. The first month is for developing
new features , .If some features hasn't been finished in this month, it will be
put in the next release ticket. In the last two month, we just do test.
Storm may face the greatest challenge in a big cluster, so I am more
concerned about ZK Optimization as jstorm did. At last, it's great for the next
release to has a test report about the stability and performance , due to lots
of new features in the latest versions.
Regards
John Fang
-----邮件原件-----
发件人: P. Taylor Goetz [mailto:[email protected]]
发送时间: 2015年11月11日 6:16
收件人: [email protected]
主题: [DISCUSS] Initial 0.11.0 Release
I’d like to start discussing our next release (0.11.0).
First off, I’d like to create a list of issues/features that are in-progress
and not yet merged to master, so we can start tracking them for inclusion in
the release. If there are specific JIRAs you would like included, please reply,
and I will add them to the wiki page for the 0.11.0 release [1].
Second, I’d like to propose modifying the release cycle a bit. I’d like to
continue the beta release cycle we started with 0.10.0, but this time I’d like
to consider adding some sort of temporal constraint so we release new betas
more often — something like a new beta release every 3 weeks or so until we
feel confident in dropping the beta tag. IMHO, there was too long a gap between
0.10.0-beta1 and 0.10.0 and we should have had more interim releases during
that time.
Any thoughts?
-Taylor
[1] https://cwiki.apache.org/confluence/display/STORM/Release+0.11.0+Feature+Set
