The changes here are related to 1.x spark releases, right? So the idea here is that this becomes a dev stream for Spark 1.6 support and you guys can have 0.13, 0.14, 0.15, as required from this branch.
If you guys want to change, I don't have any objections, please go ahead and change. On Fri, Jan 13, 2017 at 1:55 PM, <dusenberr...@gmail.com> wrote: > Thanks, Luciano for creating the branch. Could we rename it to > "branch-0.12" to better reflect that any changes that are added would only > apply to future bug fix releases on the 0.12.x line? This would be more in > line with the naming scheme that Spark uses for its branches, and should > cause less confusion. > > -- > > Mike Dusenberry > GitHub: github.com/dusenberrymw > LinkedIn: linkedin.com/in/mikedusenberry > > Sent from my iPhone. > > > > On Jan 13, 2017, at 1:50 PM, Luciano Resende <luckbr1...@gmail.com> > wrote: > > > > We have created the following branch to track Spark 1.6 fixes : > > origin/branch-systemml-spark-1.6 > > > > Note that, fixes that go into master, and are also affecting 1.6, they > > should be cherry-picked to the 1.6 branch as well. > > > > As for checking out, you will need to do something like the steps below > > (your preference might change some steps) > > > > git checkout -b branch-systemml-spark-1.6 origin/branch-systemml-spark- > 1.6 > > git branch --set-upstream-to origin/branch-systemml-spark-1.6 > > branch-systemml-spark-1.6 > > > > this last one is like: > > > > git branch --set-upstream-to origin/my_remote_branch my_local_branch > > > > For creating dev branches for 1.6, first go to you local 1.6 branch and > > continue with your regular steps such as git branch -b JIRA-222 > > > > And good luck !!! > > > > -- > > Luciano Resende > > http://twitter.com/lresende1975 > > http://lresende.blogspot.com/ > -- Luciano Resende http://twitter.com/lresende1975 http://lresende.blogspot.com/
