Who is managing 1.3 release ? You might want to coordinate with them before porting changes to branch.
Regards Mridul On Friday, March 13, 2015, Sean Owen <so...@cloudera.com> wrote: > Yeah, I'm guessing that is all happening quite literally as we speak. > The Apache git tag is the one of reference: > > https://git-wip-us.apache.org/repos/asf?p=spark.git;a=commit;h=4aaf48d46d13129f0f9bdafd771dd80fe568a7dc > > Open season on 1.3 branch then... > > On Fri, Mar 13, 2015 at 4:20 PM, Nicholas Chammas > <nicholas.cham...@gmail.com <javascript:;>> wrote: > > Looks like the release is out: > > http://spark.apache.org/releases/spark-release-1-3-0.html > > > > Though, interestingly, I think we are missing the appropriate v1.3.0 tag: > > https://github.com/apache/spark/releases > > > > Nick > > > > On Fri, Mar 13, 2015 at 6:07 AM Sean Owen <so...@cloudera.com > <javascript:;>> wrote: > >> > >> Is the release certain enough that we can resume merging into > >> branch-1.3 at this point? I have a number of back-ports queued up and > >> didn't want to merge in case another last RC was needed. I see a few > >> commits to the branch though. > >> > >> --------------------------------------------------------------------- > >> To unsubscribe, e-mail: dev-unsubscr...@spark.apache.org <javascript:;> > >> For additional commands, e-mail: dev-h...@spark.apache.org > <javascript:;> > >> > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@spark.apache.org <javascript:;> > For additional commands, e-mail: dev-h...@spark.apache.org <javascript:;> > >
