Yes, please. -Taylor
> On Feb 2, 2016, at 2:51 PM, Aaron.Dossett <aaron.doss...@target.com> wrote: > > Should back porting fixes from master to 1.0 be included as tasks under that > epic? > > From: "P. Taylor Goetz" <ptgo...@gmail.com<mailto:ptgo...@gmail.com>> > Reply-To: <dev@storm.apache.org<mailto:dev@storm.apache.org>> > Date: Monday, February 1, 2016 at 7:23 PM > To: <dev@storm.apache.org<mailto:dev@storm.apache.org>> > Subject: [DISCUSS] 1.0 Release/Clojure-Java Migration > > 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
signature.asc
Description: Message signed with OpenPGP using GPGMail
