Of the three blockers: STORM-1141 looks invalid now that 0.10.0 has been released. STORM-930 also looks invalid, and there aren’t many details to diagnose. STORM-617 doesn’t seem like a blocker, since there is a workaround for the issue.
I will look through JIRA and open pull requests to see if there are any other issues we should be tracking for the 1.0 release. For me, STORM-1406 would be nice to have, but I don’t see it in any way a blocker for the 1.0 release. The only thing I have to complete before opening a pull request is documentation and sample usage. Again, I’m fine if it doesn’t make it into 1.0. -Taylor > On Jan 4, 2016, at 12:33 PM, Bobby Evans <[email protected]> wrote: > > I feel we are about ready to do a 1.0 release. > The only JIRA left on the list > (https://cwiki.apache.org/confluence/display/STORM/Storm+Release+1.0) is > STORM-1371. I would also like to see STORM-1202 go in. > https://issues.apache.org/jira/issues/?jql=project%20%3D%20STORM%20and%20resolution%20%3D%20Unresolved%20and%20priority%20%3E%3D%20Blocker > only shows 3 blockers. we should review them, but they don't look like real > blockers to me. > Are we missing anything? If not as soon as STORM-1371 and STORM-1202 I will > create a 1.0 branch and we can start work on stabilizing 1.0 enough to > release, and in parallel start the JStorm migration work. > - Bobby
signature.asc
Description: Message signed with OpenPGP using GPGMail
