Re: SystemML Branch for any fixes related to Spark 1.6x
So the rename was to prevent confusion around what types of additions should be added to the branch. We want to apply any crucial bug fixes that affect our 0.12 release to the 0.12 branch in support of future 0.12.x releases, but we don't want to backport any brand new features to support Spark 1.6. Thus, maintaining a semantic name of `branch-0.12` should keep the confusion low, and keep it clear that only bug fixes will be added in support of future 0.12.x bug fix releases. This is the common practice in other similar projects. -Mike -- Mike Dusenberry GitHub: github.com/dusenberrymw LinkedIn: linkedin.com/in/mikedusenberry Sent from my iPhone. > On Jan 13, 2017, at 7:03 PM, Arvind Surve wrote: > > Though there is no new features will be added to SystemML But fixes specific > to Spark 1.6, will be added per need.In other words, SystemML will be > supported for Spark 1.6 as well. > I don't see there was need to change branch name. Name > branch-systemml-spark-1.6 was more appropriate for user/devloper's standpoint > to give clear distinction > Not sure if name consistency was mandatory here. --Arvind > SurveSpark Technology Centerhttp://www.spark.tc/ > > From: "dusenberr...@gmail.com" > To: dev@systemml.incubator.apache.org > Sent: Friday, January 13, 2017 3:57 PM > Subject: Re: SystemML Branch for any fixes related to Spark 1.6x > > Well, I think the final consensus in the community was that the 0.12 release > would be the final line that supports Spark 1.6.x. All future releases will > be on Spark 2.x. The idea of supporting both simultaneously was considered, > but ultimately it was agreed that it just wouldn't be sustainable. > > -Mike > > -- > > Mike Dusenberry > GitHub: github.com/dusenberrymw > LinkedIn: linkedin.com/in/mikedusenberry > > Sent from my iPhone. > > >> On Jan 13, 2017, at 3:46 PM, Luciano Resende wrote: >> >> 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, 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 >>> 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/ >
Re: SystemML Branch for any fixes related to Spark 1.6x
Though there is no new features will be added to SystemML But fixes specific to Spark 1.6, will be added per need.In other words, SystemML will be supported for Spark 1.6 as well. I don't see there was need to change branch name. Name branch-systemml-spark-1.6 was more appropriate for user/devloper's standpoint to give clear distinction Not sure if name consistency was mandatory here. --Arvind SurveSpark Technology Centerhttp://www.spark.tc/ From: "dusenberr...@gmail.com" To: dev@systemml.incubator.apache.org Sent: Friday, January 13, 2017 3:57 PM Subject: Re: SystemML Branch for any fixes related to Spark 1.6x Well, I think the final consensus in the community was that the 0.12 release would be the final line that supports Spark 1.6.x. All future releases will be on Spark 2.x. The idea of supporting both simultaneously was considered, but ultimately it was agreed that it just wouldn't be sustainable. -Mike -- Mike Dusenberry GitHub: github.com/dusenberrymw LinkedIn: linkedin.com/in/mikedusenberry Sent from my iPhone. > On Jan 13, 2017, at 3:46 PM, Luciano Resende wrote: > > 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, 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 >> 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/
Re: SystemML Branch for any fixes related to Spark 1.6x
Alright, I've updated the branch to `branch-0.12`, and cherry picked a few commits on top that looked necessary. We can use this branch to finish the 0.12 release, and to provide any bug fixes. For commits specifically related to the release, such as cutting a rc2 for 0.12, just push them to this branch. Otherwise, if a defect is found that needs to be fixed before releasing 0.12, fix it in the master first, and then cherry pick that commit to the `branch-0.12` branch. - Mike -- Michael W. Dusenberry GitHub: github.com/dusenberrymw LinkedIn: linkedin.com/in/mikedusenberry On Fri, Jan 13, 2017 at 3:57 PM, wrote: > Well, I think the final consensus in the community was that the 0.12 > release would be the final line that supports Spark 1.6.x. All future > releases will be on Spark 2.x. The idea of supporting both simultaneously > was considered, but ultimately it was agreed that it just wouldn't be > sustainable. > > -Mike > > -- > > Mike Dusenberry > GitHub: github.com/dusenberrymw > LinkedIn: linkedin.com/in/mikedusenberry > > Sent from my iPhone. > > > On Jan 13, 2017, at 3:46 PM, Luciano Resende wrote: > > 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, 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 > > 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/ > >
Re: SystemML Branch for any fixes related to Spark 1.6x
Well, I think the final consensus in the community was that the 0.12 release would be the final line that supports Spark 1.6.x. All future releases will be on Spark 2.x. The idea of supporting both simultaneously was considered, but ultimately it was agreed that it just wouldn't be sustainable. -Mike -- Mike Dusenberry GitHub: github.com/dusenberrymw LinkedIn: linkedin.com/in/mikedusenberry Sent from my iPhone. > On Jan 13, 2017, at 3:46 PM, Luciano Resende wrote: > > 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, 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 >> 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/
Re: SystemML Branch for any fixes related to Spark 1.6x
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, 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 > 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/
Re: SystemML Branch for any fixes related to Spark 1.6x
Thank you for creating the branch Luciano. I agree with Mike's suggestion that "branch-0.12" might be clearer. Deron On Fri, Jan 13, 2017 at 1:55 PM, 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 > 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/ > -- Deron Eriksson Spark Technology Center http://www.spark.tc/
Re: SystemML Branch for any fixes related to Spark 1.6x
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 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/
SystemML Branch for any fixes related to Spark 1.6x
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/
