I agree, and that was the original plan. However, the clojure to java migration stalled for a number of reasons (peoples’ $dayjob responsibilities can change often and affect the amount of time they have to contribute to the project — this is to be expected and not considered a problem.). Prior to “feature freezing” the 1.x line, I think we should get 1.1.0 released. In my opinion the only remaining issue for the release is a resolution to STORM-2006, particularly adding an interface for aggregated metrics.
I don’t have a good feel for how long it will take to get the master branch (aka “2.0”) in a releasable state (again it comes down to contributor $dayjobs, which are largely out of anyone’s control). So I think we should plan on supporting 1.x for a while. -Taylor > On Aug 16, 2016, at 10:40 PM, Harsha Chintalapani <st...@harsha.io> wrote: > > Hi All, > Currently we are undertaken JStorm merger and ongoing migration > of existing Clojure code. I am proposing that we should stop any feature > development for 1.x branch so that we can make progress on java migration > and get it done before adding any further features. If any one interested > adding features they can do so on master for 2.0. > This will give us time to complete the migration and keeps the > core code more or less the same . Adding more code to core makes the > migration that much harder. > We should be ok on adding any connectors or so as that can be independent > of core and can be easily added to master. > What you think? > > Thanks, > Harsha
signature.asc
Description: Message signed with OpenPGP using GPGMail
