Sorry for the delay due to traveling...
The branch has been cut. At this point anything that we want to go into
Spark 1.6 will need to be cherry-picked. Please be cautious when doing so,
and contact me if you are uncertain.
Michael
On Sun, Nov 1, 2015 at 4:16 AM, Sean Owen wrote:
> I like th
I like the idea, but I think there's already a lot of triage backlog. Can
we more concretely address this now and during the next two weeks?
1.6.0 stats from JIRA:
344 issues targeted at 1.6.0, of which
253 are from committers, of which
215 are improvements/other, of which
5 are bloc
Hi Michael,
thanks for the reminder and update. I have some PR in progress, but no
rush to be included in 1.6.
Regards
JB
On 10/31/2015 12:25 PM, Michael Armbrust wrote:
Hey All,
Just a friendly reminder that today (October 31st) is the scheduled code
freeze for Spark 1.6. Since a lot of d
Hey All,
Just a friendly reminder that today (October 31st) is the scheduled code
freeze for Spark 1.6. Since a lot of developers were busy with the Spark
Summit last week I'm going to delay cutting the branch until Monday,
November 2nd. After that point, we'll package a release for testing and
