You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@spark.apache.org by Patrick Wendell <pw...@gmail.com> on 2014/07/27 20:31:17 UTC
branch-1.1 will be cut on Friday
Hey All,
Just a heads up, we'll cut branch-1.1 on this Friday, August 1st. Once
the release branch is cut we'll start community QA and go into the
normal triage process for merging patches into that branch.
For Spark core, we'll be conservative in merging things past the
freeze date (e.g. high priority fixes) to ensure a healthy amount of
time for testing. A key focus of this release in core is improving
overall stability and resilience of Spark core.
As always, I'll encourage of committers/contributors to help review
patches this week to so we can get as many things in as possible.
People have been quite active recently, which is great!
Good luck!
- Patrick
Re: branch-1.1 will be cut on Friday
Posted by Nan Zhu <zh...@gmail.com>.
Good news, we will see the official version containing JDBC in very soon!
Also, I have several pending PRs, can anyone continue the review process in this week?
Avoid overwriting already-set SPARK_HOME in spark-submit: https://github.com/apache/spark/pull/1331
fix locality inversion bug in TaskSetManager: https://github.com/apache/spark/pull/1313 (Matei and Mridulm are working on it)
Allow multiple executor per worker in Standalone mode: https://github.com/apache/spark/pull/731
Ensure actor is self-contained in DAGScheduler: https://github.com/apache/spark/pull/637
Best,
--
Nan Zhu
On Sunday, July 27, 2014 at 2:31 PM, Patrick Wendell wrote:
> Hey All,
>
> Just a heads up, we'll cut branch-1.1 on this Friday, August 1st. Once
> the release branch is cut we'll start community QA and go into the
> normal triage process for merging patches into that branch.
>
> For Spark core, we'll be conservative in merging things past the
> freeze date (e.g. high priority fixes) to ensure a healthy amount of
> time for testing. A key focus of this release in core is improving
> overall stability and resilience of Spark core.
>
> As always, I'll encourage of committers/contributors to help review
> patches this week to so we can get as many things in as possible.
> People have been quite active recently, which is great!
>
> Good luck!
> - Patrick
>
>