I think the answer is: "Or perhaps drive the 2.1 branch forward and only send bug fixes to the 1.6 branch for another year or so?"
Since there isn't a large block of "in production" usage yet we can expect a good percentage of new deployments to be on totally new clusters or clusters where a package upgrade wouldn't be to hard. Lagging to far behind a major release is a dangerous path. Maybe I should bring up the elephant in the room that ipython support for 2.x just got dropped. On Fri, Apr 21, 2017 at 3:40 PM Segerlind, Nathan L < [email protected]> wrote: > Hi everybody. > > There's been some talk about upgrading to Spark 2.1. > > Do people think this is worthwhile? > > Would others like to see continued support for 1.6? For how long and it > what capacity? > > Should we maintain two branches? > > Or perhaps drive the 2.1 branch forward and only send bug fixes to the 1.6 > branch for another year or so? > > >
