Thanks Bobby. I don’t mind doing the release prep and testing. It seems like i’ve been focused on that while you’ve had more time to forge ahead with the JStorm migration, which feels like a natural way for us to divide and conquer. So far that seems to be working out well.
-Taylor > On Feb 2, 2016, at 9:49 AM, Bobby Evans <ev...@yahoo-inc.com.INVALID> wrote: > > I agree that it has stabilized a lot recently. > > Taylor, in the past you have been the one that has done most of the release > work. I am fine with letting you continue that for the 1.x line if you like, > or I am happy to do some of that too if you would rather off load it. Please > let me know what you prefer. > Thanks, > Bobby > > On Tuesday, February 2, 2016 8:07 AM, P. Taylor Goetz <ptgo...@gmail.com> > wrote: > > > Done. Thanks for the suggestion. > > -Taylor > >> On Feb 2, 2016, at 5:11 AM, Abhishek Agarwal <abhishc...@gmail.com> wrote: >> >> Is it possible to make the type as Epic so that remaining filed issues can >> be directly linked? >> e.g. https://issues.apache.org/jira/browse/STORM-1455 >> >> On Tue, Feb 2, 2016 at 6:53 AM, P. Taylor Goetz <ptgo...@gmail.com> wrote: >> >>> I think the 1.x-branch has stabilized enough that it’s safe to allow the >>> master branch diverge in support of the JStorm merge. There’s a lot of >>> good work going on with the JStorm merge, and I’d like to unblock that. >>> >>> I created STORM-1491 <https://issues.apache.org/jira/browse/STORM-1491> for >>> tracking any remaining items for the 1.0 release, and would propose that >>> any remaining/new items for 1.0 be added as a subtask to that JIRA. When >>> all are complete/punted/etc. we move forward with a release. >>> >>> Any thoughts? >>> >>> -Taylor >>> >> >> >> >> -- >> Regards, >> Abhishek Agarwal > >
signature.asc
Description: Message signed with OpenPGP using GPGMail
