Spark 2.x/scala 2.11.x release

[Andrew Palumbo <ap...@outlook.com>]

Sounds Good.  I'll put out a proposal for the release, and we can go Over it and vote if we want to on releasing or on the scope.  I'm +1 on it.


Broad strokes of what I'm thinking:


- Checkout a new branch "features/multi-artifact-build-22xx" from master @ the `mahout-0.13.0` release tag.


- Revert master back to release tag.


- Checkout a new `develop` branch from master @the `mahout-0.13.0` release tag.


- Cherrypick any commits that we'd like to release (E.g.: SparseSpeedup) onto `develop` (along with a PR ad a ticket).


- Merge `develop` to `master`, run through Smoke tests, tag master @ `mahout-0.13.1`(automatically), and release.


This will also get us to more of a git-flow workflow, as we've discussed moving towards.


Thoughts @all?


--andy






________________________________
From: Pat Ferrel <pa...@gmail.com>
Sent: Wednesday, February 28, 2018 2:53:58 PM
To: Andrew Palumbo; dev@mahout.apache.org
Subject: Re: Spark 2.x/scala 2.11.x release

big +1

If you are planning to branch off the 0.13.0 tag let me know, I have a speedup that is in my scala 2.11 fork of 0.13.0 that needs to be released


From: Andrew Palumbo <ap...@outlook.com>
Reply: dev@mahout.apache.org<ma...@mahout.apache.org> <de...@mahout.apache.org>
Date: February 28, 2018 at 11:16:12 AM
To: dev@mahout.apache.org<ma...@mahout.apache.org> <de...@mahout.apache.org>
Subject:  Spark 2.x/scala 2.11.x release

After some offline discussion regarding people's needs for Spark and 2.x and Scala 2.11.x, I am wondering If we should just consider a release for 2.x and 2.11.x as the default. We could release from the current master, or branch back off of the 0.13.0 tag, and release that with the upgraded defaults, and branch our current multi-artifact build off as a feature. Any thoughts on this?


--andy

Re: Spark 2.x/scala 2.11.x release

[Trevor Grant <tr...@gmail.com>]

In addition to numerous other problems- its not 'just that simple'

Git has to be setup and replumbed to close PRs based on merge to develop,
as well as making that the default for new PRs.

IIRC we tried doing this last year- it was a mess, we went back.

We're not doing _that_ much work on master to necessitate it, its a lot of
work to change over, it does increase the learning curve to coming on board
with the project.

Spark, Flink, Zeppelin, other TLPs- use master for the so called- "develop"
branch and latest release branch as stable.  I am in favor of this method.
You use develop branch/stable master for projects when you are trying to
push new features out daily.  We have been trying to solve the "stuck on
scala-2.10" riddle since last release.  IIRC, the issue was around the
scopt being somehow stuck to pulling in scala-2.10.  I don't think we've
added a serious feature since then.  All current users for prod-deployments
should be buildling from mahout-0.13 branch anyway, and then applying their
own tricks to get the build to work for scala-2.11 (e.g. delete the drivers
or build with maven).

my .02



On Fri, Mar 2, 2018 at 2:32 PM, Pat Ferrel <pa...@gmail.com> wrote:

> Trevor said -1 to git flow.
>
> I agree this is a good example of one nice feature. Master is always
> pristine.
>
>
> From: Andrew Palumbo <ap...@outlook.com> <ap...@outlook.com>
> Reply: dev@mahout.apache.org <de...@mahout.apache.org> <
> dev@mahout.apache.org>
> Date: March 2, 2018 at 12:30:09 PM
> To: dev@mahout.apache.org <de...@mahout.apache.org> <de...@mahout.apache.org>
> Subject:  Re: Spark 2.x/scala 2.11.x release
>
> Pat - Not sure if you thought I meant -1 or you're saying -1 to `git-flow`.
> I'm +1 on it, and this is a perfect time to make the transition, since we
> don't have a `develop` branch, now we can revert `master` to its state at
> the 0.13.0 release, create a `develop` at the same time, branched from the
> `mahout-0.13.0` tag, cherrypick commits that we want from post -
> `mahout-0.13.0` and keep the rest of the work, currently on `master` e.g.:
> all of the work that Trevor did on the multi-artifact release on a feature
> branch, which we can hopefully release soon as 0.13.2.
>
>
> So I'm essentially suggesting that we take this as an opportunity to move
> to this `git-flow` style of managing our repo.
>
>
>
>
> ________________________________
> From: Pat Ferrel <pa...@occamsmachete.com>
> Sent: Friday, March 2, 2018 3:00:15 PM
> To: Trevor Grant; dev@mahout.apache.org
> Subject: Re: Spark 2.x/scala 2.11.x release
>
> -1 on git flow?
>
> What are your reasons? I use it in 3-4 project, one of which is Apache PIO.
> I’d think this would be a good example of why it’s nice. right now our
> master is screwed up, with git flow it would still have 0.13.0, which is
> what we are talking about releasing with minor mods.
>
>
> From: Trevor Grant <tr...@gmail.com> <tr...@gmail.com>
> Reply: dev@mahout.apache.org <de...@mahout.apache.org> <
> dev@mahout.apache.org>
>
> Date: March 2, 2018 at 11:36:52 AM
> To: Mahout Dev List <de...@mahout.apache.org> <de...@mahout.apache.org>
> Subject: Re: Spark 2.x/scala 2.11.x release
>
> I'm +1 for a working scala-2.11, spark-2.x build.
>
> I'm -1 for previously stated reasons on git-flow.
>
> tg
>
>
> On Fri, Mar 2, 2018 at 1:24 PM, Andrew Palumbo <ap...@outlook.com> wrote:
>
> >
> > Sounds Good. I'll put out a proposal for the release, and we can go Over
> > it and vote if we want to on releasing or on the scope. I'm +1 on it.
> >
> >
> > Broad strokes of what I'm thinking:
> >
> >
> > - Checkout a new branch "features/multi-artifact-build-22xx" from master
> > @ the `mahout-0.13.0` release tag.
> >
> >
> > - Revert master back to release tag.
> >
> >
> > - Checkout a new `develop` branch from master @the `mahout-0.13.0`
> release
> > tag.
> >
> >
> > - Cherrypick any commits that we'd like to release (E.g.: SparseSpeedup)
> > onto `develop` (along with a PR ad a ticket).
> >
> >
> > - Merge `develop` to `master`, run through Smoke tests, tag master @
> > `mahout-0.13.1`(automatically), and release.
> >
> >
> > This will also get us to more of a git-flow workflow, as we've discussed
> > moving towards.
> >
> >
> > Thoughts @all?
> >
> >
> > --andy
> >
> >
> >
> >
> >
> >
> > ________________________________
> > From: Pat Ferrel <pa...@gmail.com>
> > Sent: Wednesday, February 28, 2018 2:53:58 PM
> > To: Andrew Palumbo; dev@mahout.apache.org
> > Subject: Re: Spark 2.x/scala 2.11.x release
> >
> > big +1
> >
> > If you are planning to branch off the 0.13.0 tag let me know, I have a
> > speedup that is in my scala 2.11 fork of 0.13.0 that needs to be released
> >
> >
> > From: Andrew Palumbo <ap...@outlook.com>
> > Reply: dev@mahout.apache.org<ma...@mahout.apache.org> <
> > dev@mahout.apache.org><ma...@mahout.apache.org>
> > Date: February 28, 2018 at 11:16:12 AM
> > To: dev@mahout.apache.org<ma...@mahout.apache.org> <
> > dev@mahout.apache.org><ma...@mahout.apache.org>
> > Subject: Spark 2.x/scala 2.11.x release
> >
> > After some offline discussion regarding people's needs for Spark and 2.x
> > and Scala 2.11.x, I am wondering If we should just consider a release for
> > 2.x and 2.11.x as the default. We could release from the current master,
> or
> > branch back off of the 0.13.0 tag, and release that with the upgraded
> > defaults, and branch our current multi-artifact build off as a feature.
> Any
> > thoughts on this?
> >
> >
> > --andy
> >
>

Re: Spark 2.x/scala 2.11.x release

[Pat Ferrel <pa...@gmail.com>]

Trevor said -1 to git flow.

I agree this is a good example of one nice feature. Master is always
pristine.


From: Andrew Palumbo <ap...@outlook.com> <ap...@outlook.com>
Reply: dev@mahout.apache.org <de...@mahout.apache.org> <de...@mahout.apache.org>
Date: March 2, 2018 at 12:30:09 PM
To: dev@mahout.apache.org <de...@mahout.apache.org> <de...@mahout.apache.org>
Subject:  Re: Spark 2.x/scala 2.11.x release

Pat - Not sure if you thought I meant -1 or you're saying -1 to `git-flow`.
I'm +1 on it, and this is a perfect time to make the transition, since we
don't have a `develop` branch, now we can revert `master` to its state at
the 0.13.0 release, create a `develop` at the same time, branched from the
`mahout-0.13.0` tag, cherrypick commits that we want from post -
`mahout-0.13.0` and keep the rest of the work, currently on `master` e.g.:
all of the work that Trevor did on the multi-artifact release on a feature
branch, which we can hopefully release soon as 0.13.2.


So I'm essentially suggesting that we take this as an opportunity to move
to this `git-flow` style of managing our repo.




________________________________
From: Pat Ferrel <pa...@occamsmachete.com>
Sent: Friday, March 2, 2018 3:00:15 PM
To: Trevor Grant; dev@mahout.apache.org
Subject: Re: Spark 2.x/scala 2.11.x release

-1 on git flow?

What are your reasons? I use it in 3-4 project, one of which is Apache PIO.
I’d think this would be a good example of why it’s nice. right now our
master is screwed up, with git flow it would still have 0.13.0, which is
what we are talking about releasing with minor mods.


From: Trevor Grant <tr...@gmail.com> <tr...@gmail.com>
Reply: dev@mahout.apache.org <de...@mahout.apache.org> <de...@mahout.apache.org>

Date: March 2, 2018 at 11:36:52 AM
To: Mahout Dev List <de...@mahout.apache.org> <de...@mahout.apache.org>
Subject: Re: Spark 2.x/scala 2.11.x release

I'm +1 for a working scala-2.11, spark-2.x build.

I'm -1 for previously stated reasons on git-flow.

tg


On Fri, Mar 2, 2018 at 1:24 PM, Andrew Palumbo <ap...@outlook.com> wrote:

>
> Sounds Good. I'll put out a proposal for the release, and we can go Over
> it and vote if we want to on releasing or on the scope. I'm +1 on it.
>
>
> Broad strokes of what I'm thinking:
>
>
> - Checkout a new branch "features/multi-artifact-build-22xx" from master
> @ the `mahout-0.13.0` release tag.
>
>
> - Revert master back to release tag.
>
>
> - Checkout a new `develop` branch from master @the `mahout-0.13.0`
release
> tag.
>
>
> - Cherrypick any commits that we'd like to release (E.g.: SparseSpeedup)
> onto `develop` (along with a PR ad a ticket).
>
>
> - Merge `develop` to `master`, run through Smoke tests, tag master @
> `mahout-0.13.1`(automatically), and release.
>
>
> This will also get us to more of a git-flow workflow, as we've discussed
> moving towards.
>
>
> Thoughts @all?
>
>
> --andy
>
>
>
>
>
>
> ________________________________
> From: Pat Ferrel <pa...@gmail.com>
> Sent: Wednesday, February 28, 2018 2:53:58 PM
> To: Andrew Palumbo; dev@mahout.apache.org
> Subject: Re: Spark 2.x/scala 2.11.x release
>
> big +1
>
> If you are planning to branch off the 0.13.0 tag let me know, I have a
> speedup that is in my scala 2.11 fork of 0.13.0 that needs to be released
>
>
> From: Andrew Palumbo <ap...@outlook.com>
> Reply: dev@mahout.apache.org<ma...@mahout.apache.org> <
> dev@mahout.apache.org><ma...@mahout.apache.org>
> Date: February 28, 2018 at 11:16:12 AM
> To: dev@mahout.apache.org<ma...@mahout.apache.org> <
> dev@mahout.apache.org><ma...@mahout.apache.org>
> Subject: Spark 2.x/scala 2.11.x release
>
> After some offline discussion regarding people's needs for Spark and 2.x
> and Scala 2.11.x, I am wondering If we should just consider a release for
> 2.x and 2.11.x as the default. We could release from the current master,
or
> branch back off of the 0.13.0 tag, and release that with the upgraded
> defaults, and branch our current multi-artifact build off as a feature.
Any
> thoughts on this?
>
>
> --andy
>

Re: Spark 2.x/scala 2.11.x release

[Andrew Palumbo <ap...@outlook.com>]

oh I see that I missed Trevor's -1 on git-flow.

________________________________
From: Andrew Palumbo <ap...@outlook.com>
Sent: Friday, March 2, 2018 3:29:54 PM
To: dev@mahout.apache.org
Subject: Re: Spark 2.x/scala 2.11.x release


Pat - Not sure if you thought I meant -1 or you're saying -1 to `git-flow`. I'm +1 on it, and this is a perfect time to make the transition, since we don't have a `develop` branch, now we can revert `master` to its state at the 0.13.0 release, create a `develop` at the same time, branched from the `mahout-0.13.0` tag, cherrypick commits that we want from post - `mahout-0.13.0` and keep the rest of the work, currently on `master` e.g.: all of the work that Trevor did on the multi-artifact release on a feature branch, which we can hopefully release soon as 0.13.2.


So I'm essentially suggesting that we take this as an opportunity to move to this `git-flow` style of managing our repo.




________________________________
From: Pat Ferrel <pa...@occamsmachete.com>
Sent: Friday, March 2, 2018 3:00:15 PM
To: Trevor Grant; dev@mahout.apache.org
Subject: Re: Spark 2.x/scala 2.11.x release

-1 on git flow?

What are your reasons? I use it in 3-4 project, one of which is Apache PIO.
I’d think this would be a good example of why it’s nice. right now our
master is screwed up, with git flow it would still have 0.13.0, which is
what we are talking about releasing with minor mods.


From: Trevor Grant <tr...@gmail.com> <tr...@gmail.com>
Reply: dev@mahout.apache.org <de...@mahout.apache.org> <de...@mahout.apache.org>
Date: March 2, 2018 at 11:36:52 AM
To: Mahout Dev List <de...@mahout.apache.org> <de...@mahout.apache.org>
Subject:  Re: Spark 2.x/scala 2.11.x release

I'm +1 for a working scala-2.11, spark-2.x build.

I'm -1 for previously stated reasons on git-flow.

tg


On Fri, Mar 2, 2018 at 1:24 PM, Andrew Palumbo <ap...@outlook.com> wrote:

>
> Sounds Good. I'll put out a proposal for the release, and we can go Over
> it and vote if we want to on releasing or on the scope. I'm +1 on it.
>
>
> Broad strokes of what I'm thinking:
>
>
> - Checkout a new branch "features/multi-artifact-build-22xx" from master
> @ the `mahout-0.13.0` release tag.
>
>
> - Revert master back to release tag.
>
>
> - Checkout a new `develop` branch from master @the `mahout-0.13.0`
release
> tag.
>
>
> - Cherrypick any commits that we'd like to release (E.g.: SparseSpeedup)
> onto `develop` (along with a PR ad a ticket).
>
>
> - Merge `develop` to `master`, run through Smoke tests, tag master @
> `mahout-0.13.1`(automatically), and release.
>
>
> This will also get us to more of a git-flow workflow, as we've discussed
> moving towards.
>
>
> Thoughts @all?
>
>
> --andy
>
>
>
>
>
>
> ________________________________
> From: Pat Ferrel <pa...@gmail.com>
> Sent: Wednesday, February 28, 2018 2:53:58 PM
> To: Andrew Palumbo; dev@mahout.apache.org
> Subject: Re: Spark 2.x/scala 2.11.x release
>
> big +1
>
> If you are planning to branch off the 0.13.0 tag let me know, I have a
> speedup that is in my scala 2.11 fork of 0.13.0 that needs to be released
>
>
> From: Andrew Palumbo <ap...@outlook.com>
> Reply: dev@mahout.apache.org<ma...@mahout.apache.org> <
> dev@mahout.apache.org><ma...@mahout.apache.org>
> Date: February 28, 2018 at 11:16:12 AM
> To: dev@mahout.apache.org<ma...@mahout.apache.org> <
> dev@mahout.apache.org><ma...@mahout.apache.org>
> Subject: Spark 2.x/scala 2.11.x release
>
> After some offline discussion regarding people's needs for Spark and 2.x
> and Scala 2.11.x, I am wondering If we should just consider a release for
> 2.x and 2.11.x as the default. We could release from the current master,
or
> branch back off of the 0.13.0 tag, and release that with the upgraded
> defaults, and branch our current multi-artifact build off as a feature.
Any
> thoughts on this?
>
>
> --andy
>

Re: Spark 2.x/scala 2.11.x release

[Andrew Palumbo <ap...@outlook.com>]

Pat - Not sure if you thought I meant -1 or you're saying -1 to `git-flow`. I'm +1 on it, and this is a perfect time to make the transition, since we don't have a `develop` branch, now we can revert `master` to its state at the 0.13.0 release, create a `develop` at the same time, branched from the `mahout-0.13.0` tag, cherrypick commits that we want from post - `mahout-0.13.0` and keep the rest of the work, currently on `master` e.g.: all of the work that Trevor did on the multi-artifact release on a feature branch, which we can hopefully release soon as 0.13.2.


So I'm essentially suggesting that we take this as an opportunity to move to this `git-flow` style of managing our repo.




________________________________
From: Pat Ferrel <pa...@occamsmachete.com>
Sent: Friday, March 2, 2018 3:00:15 PM
To: Trevor Grant; dev@mahout.apache.org
Subject: Re: Spark 2.x/scala 2.11.x release

-1 on git flow?

What are your reasons? I use it in 3-4 project, one of which is Apache PIO.
I’d think this would be a good example of why it’s nice. right now our
master is screwed up, with git flow it would still have 0.13.0, which is
what we are talking about releasing with minor mods.


From: Trevor Grant <tr...@gmail.com> <tr...@gmail.com>
Reply: dev@mahout.apache.org <de...@mahout.apache.org> <de...@mahout.apache.org>
Date: March 2, 2018 at 11:36:52 AM
To: Mahout Dev List <de...@mahout.apache.org> <de...@mahout.apache.org>
Subject:  Re: Spark 2.x/scala 2.11.x release

I'm +1 for a working scala-2.11, spark-2.x build.

I'm -1 for previously stated reasons on git-flow.

tg


On Fri, Mar 2, 2018 at 1:24 PM, Andrew Palumbo <ap...@outlook.com> wrote:

>
> Sounds Good. I'll put out a proposal for the release, and we can go Over
> it and vote if we want to on releasing or on the scope. I'm +1 on it.
>
>
> Broad strokes of what I'm thinking:
>
>
> - Checkout a new branch "features/multi-artifact-build-22xx" from master
> @ the `mahout-0.13.0` release tag.
>
>
> - Revert master back to release tag.
>
>
> - Checkout a new `develop` branch from master @the `mahout-0.13.0`
release
> tag.
>
>
> - Cherrypick any commits that we'd like to release (E.g.: SparseSpeedup)
> onto `develop` (along with a PR ad a ticket).
>
>
> - Merge `develop` to `master`, run through Smoke tests, tag master @
> `mahout-0.13.1`(automatically), and release.
>
>
> This will also get us to more of a git-flow workflow, as we've discussed
> moving towards.
>
>
> Thoughts @all?
>
>
> --andy
>
>
>
>
>
>
> ________________________________
> From: Pat Ferrel <pa...@gmail.com>
> Sent: Wednesday, February 28, 2018 2:53:58 PM
> To: Andrew Palumbo; dev@mahout.apache.org
> Subject: Re: Spark 2.x/scala 2.11.x release
>
> big +1
>
> If you are planning to branch off the 0.13.0 tag let me know, I have a
> speedup that is in my scala 2.11 fork of 0.13.0 that needs to be released
>
>
> From: Andrew Palumbo <ap...@outlook.com>
> Reply: dev@mahout.apache.org<ma...@mahout.apache.org> <
> dev@mahout.apache.org><ma...@mahout.apache.org>
> Date: February 28, 2018 at 11:16:12 AM
> To: dev@mahout.apache.org<ma...@mahout.apache.org> <
> dev@mahout.apache.org><ma...@mahout.apache.org>
> Subject: Spark 2.x/scala 2.11.x release
>
> After some offline discussion regarding people's needs for Spark and 2.x
> and Scala 2.11.x, I am wondering If we should just consider a release for
> 2.x and 2.11.x as the default. We could release from the current master,
or
> branch back off of the 0.13.0 tag, and release that with the upgraded
> defaults, and branch our current multi-artifact build off as a feature.
Any
> thoughts on this?
>
>
> --andy
>

Re: Spark 2.x/scala 2.11.x release

[Pat Ferrel <pa...@occamsmachete.com>]

-1 on git flow?

What are your reasons? I use it in 3-4 project, one of which is Apache PIO.
I’d think this would be a good example of why it’s nice. right now our
master is screwed up, with git flow it would still have 0.13.0, which is
what we are talking about releasing with minor mods.


From: Trevor Grant <tr...@gmail.com> <tr...@gmail.com>
Reply: dev@mahout.apache.org <de...@mahout.apache.org> <de...@mahout.apache.org>
Date: March 2, 2018 at 11:36:52 AM
To: Mahout Dev List <de...@mahout.apache.org> <de...@mahout.apache.org>
Subject:  Re: Spark 2.x/scala 2.11.x release

I'm +1 for a working scala-2.11, spark-2.x build.

I'm -1 for previously stated reasons on git-flow.

tg


On Fri, Mar 2, 2018 at 1:24 PM, Andrew Palumbo <ap...@outlook.com> wrote:

>
> Sounds Good. I'll put out a proposal for the release, and we can go Over
> it and vote if we want to on releasing or on the scope. I'm +1 on it.
>
>
> Broad strokes of what I'm thinking:
>
>
> - Checkout a new branch "features/multi-artifact-build-22xx" from master
> @ the `mahout-0.13.0` release tag.
>
>
> - Revert master back to release tag.
>
>
> - Checkout a new `develop` branch from master @the `mahout-0.13.0`
release
> tag.
>
>
> - Cherrypick any commits that we'd like to release (E.g.: SparseSpeedup)
> onto `develop` (along with a PR ad a ticket).
>
>
> - Merge `develop` to `master`, run through Smoke tests, tag master @
> `mahout-0.13.1`(automatically), and release.
>
>
> This will also get us to more of a git-flow workflow, as we've discussed
> moving towards.
>
>
> Thoughts @all?
>
>
> --andy
>
>
>
>
>
>
> ________________________________
> From: Pat Ferrel <pa...@gmail.com>
> Sent: Wednesday, February 28, 2018 2:53:58 PM
> To: Andrew Palumbo; dev@mahout.apache.org
> Subject: Re: Spark 2.x/scala 2.11.x release
>
> big +1
>
> If you are planning to branch off the 0.13.0 tag let me know, I have a
> speedup that is in my scala 2.11 fork of 0.13.0 that needs to be released
>
>
> From: Andrew Palumbo <ap...@outlook.com>
> Reply: dev@mahout.apache.org<ma...@mahout.apache.org> <
> dev@mahout.apache.org><ma...@mahout.apache.org>
> Date: February 28, 2018 at 11:16:12 AM
> To: dev@mahout.apache.org<ma...@mahout.apache.org> <
> dev@mahout.apache.org><ma...@mahout.apache.org>
> Subject: Spark 2.x/scala 2.11.x release
>
> After some offline discussion regarding people's needs for Spark and 2.x
> and Scala 2.11.x, I am wondering If we should just consider a release for
> 2.x and 2.11.x as the default. We could release from the current master,
or
> branch back off of the 0.13.0 tag, and release that with the upgraded
> defaults, and branch our current multi-artifact build off as a feature.
Any
> thoughts on this?
>
>
> --andy
>

Re: Spark 2.x/scala 2.11.x release

[Trevor Grant <tr...@gmail.com>]

I'm +1 for a working scala-2.11, spark-2.x build.

I'm -1 for previously stated reasons on git-flow.

tg


On Fri, Mar 2, 2018 at 1:24 PM, Andrew Palumbo <ap...@outlook.com> wrote:

>
> Sounds Good.  I'll put out a proposal for the release, and we can go Over
> it and vote if we want to on releasing or on the scope.  I'm +1 on it.
>
>
> Broad strokes of what I'm thinking:
>
>
> - Checkout a new branch "features/multi-artifact-build-22xx" from master
> @ the `mahout-0.13.0` release tag.
>
>
> - Revert master back to release tag.
>
>
> - Checkout a new `develop` branch from master @the `mahout-0.13.0` release
> tag.
>
>
> - Cherrypick any commits that we'd like to release (E.g.: SparseSpeedup)
> onto `develop` (along with a PR ad a ticket).
>
>
> - Merge `develop` to `master`, run through Smoke tests, tag master @
> `mahout-0.13.1`(automatically), and release.
>
>
> This will also get us to more of a git-flow workflow, as we've discussed
> moving towards.
>
>
> Thoughts @all?
>
>
> --andy
>
>
>
>
>
>
> ________________________________
> From: Pat Ferrel <pa...@gmail.com>
> Sent: Wednesday, February 28, 2018 2:53:58 PM
> To: Andrew Palumbo; dev@mahout.apache.org
> Subject: Re: Spark 2.x/scala 2.11.x release
>
> big +1
>
> If you are planning to branch off the 0.13.0 tag let me know, I have a
> speedup that is in my scala 2.11 fork of 0.13.0 that needs to be released
>
>
> From: Andrew Palumbo <ap...@outlook.com>
> Reply: dev@mahout.apache.org<ma...@mahout.apache.org> <
> dev@mahout.apache.org><ma...@mahout.apache.org>
> Date: February 28, 2018 at 11:16:12 AM
> To: dev@mahout.apache.org<ma...@mahout.apache.org> <
> dev@mahout.apache.org><ma...@mahout.apache.org>
> Subject:  Spark 2.x/scala 2.11.x release
>
> After some offline discussion regarding people's needs for Spark and 2.x
> and Scala 2.11.x, I am wondering If we should just consider a release for
> 2.x and 2.11.x as the default. We could release from the current master, or
> branch back off of the 0.13.0 tag, and release that with the upgraded
> defaults, and branch our current multi-artifact build off as a feature. Any
> thoughts on this?
>
>
> --andy
>

proposal for a Spark 2.x/scala 2.11.x release. was: [Spark 2.x/scala 2.11.x release]

[Andrew Palumbo <ap...@outlook.com>]

wrote this up very quickly last Fri as a proposal.  Forgot to add it to the title.  Have updated it a bit.

________________________________
From: Pat Ferrel <pa...@occamsmachete.com>
Sent: Saturday, March 3, 2018 11:51 AM
To: dev@mahout.apache.org
Subject: Re: Spark 2.x/scala 2.11.x release

LGTM


From: Andrew Palumbo <ap...@outlook.com> <ap...@outlook.com>
Reply: dev@mahout.apache.org <de...@mahout.apache.org> <de...@mahout.apache.org>
Date: March 2, 2018 at 3:38:38 PM
To: dev@mahout.apache.org <de...@mahout.apache.org> <de...@mahout.apache.org>
Subject:  Re: Spark 2.x/scala 2.11.x release

I've started a gdoc for a plan.


https://docs.google.com/document/d/1A8aqUORPp83vWa6fSqhC2jxUKEbDWWQ2lzqZ1V0xHS0/edit?usp=sharing


Please add comments, criticision, and alternate plans on on the doc.


--andy

________________________________
From: Andrew Palumbo <ap...@outlook.com>
Sent: Friday, March 2, 2018 6:11:53 PM
To: dev@mahout.apache.org
Subject: Re: Spark 2.x/scala 2.11.x release

Pat, could you explain what you mean by the "Real Problem"? I know that we
have a lot of problems, but in terms of this release, what is the major
blocker?
________________________________
From: Pat Ferrel <pa...@occamsmachete.com>
Sent: Friday, March 2, 2018 5:32:58 PM
To: Trevor Grant; dev@mahout.apache.org
Subject: Re: Spark 2.x/scala 2.11.x release

Scopt is so not an issue. None whatsoever. The problem is that drivers have
unmet runtime needs that are different than libs. Scopt has absolutely
nothing to do with this. It was from a false theory that there was no 2.11
version but it actually has 2.11, 2.12, 2.09, and according to D a native
version too.

Get on to the real problems and drop this non-problem. Anything that driver
needs but is not on the classpath will stop them at runtime.

Better to say that we would be closer to release if we dropped drivers.


From: Trevor Grant <tr...@gmail.com> <tr...@gmail.com>
Reply: dev@mahout.apache.org <de...@mahout.apache.org> <de...@mahout.apache.org>

Date: March 2, 2018 at 2:26:13 PM
To: Mahout Dev List <de...@mahout.apache.org> <de...@mahout.apache.org>
Subject: Re: Spark 2.x/scala 2.11.x release

Supposedly. I hard coded all of the poms to Scala 2.11 (closed PR unmerged)
Pat was still having issues w sbt- but the only dependency that was on 2.10
according to maven was scopt. /shrug



On Mar 2, 2018 4:20 PM, "Andrew Palumbo" <ap...@outlook.com> wrote:

> So We could release as is if we can get the scopt issue out? Thats our
> final blocker?
>
> ________________________________
> From: Trevor Grant <tr...@gmail.com>
> Sent: Friday, March 2, 2018 5:15:35 PM
> To: Mahout Dev List
> Subject: Re: Spark 2.x/scala 2.11.x release
>
> The only "mess" is in the cli spark drivers, namely scopt.
>
> Get rid of the drivers/fix the scopt issue- we have no mess.
>
>
>
> On Mar 2, 2018 4:09 PM, "Pat Ferrel" <pa...@occamsmachete.com> wrote:
>
> > BTW the mess master is in is why git flow was invented and why I asked
> that
> > the site be in a new repo so it could be on a separate release cycle.
We
> > perpetuate the mess because it’s always to hard to fix.
> >
> >
> > From: Andrew Palumbo <ap...@outlook.com> <ap...@outlook.com>
> > Reply: dev@mahout.apache.org <de...@mahout.apache.org> <
> > dev@mahout.apache.org>
> > Date: March 2, 2018 at 1:54:51 PM
> > To: dev@mahout.apache.org <de...@mahout.apache.org> <dev@mahout.apache.org
> >
> > Subject: Re: Spark 2.x/scala 2.11.x release
> >
> > re: reverting master, shit. I forgot that the website is not on
> `asf-site`
> > anymore. Well we could just re-jigger it, and check out `website` from
> > features/multi-artifact-build-MAHOUT-20xx after we revert the rest of
> > master.
> >
> >
> > You're right, Trevor- I 'm just going through the commits, and there
are
> > things like
> > https://github.com/apache/mahout/commit/c17bee3c2705495b638d81ae2ad374
> > bf7494c3f3
> >
> >
> >
> > [https://avatars3.githubusercontent.com/u/5852441?s=200&v=4]<
> > https://github.com/apache/mahout/commit/c17bee3c2705495b638d81ae2ad374
> > bf7494c3f3>
> >
> >
> > MAHOUT-1988 Make Native Solvers Scala 2.11 Complient closes apache/ma…
·
> > apache/mahout@c17bee3<
> > https://github.com/apache/mahout/commit/c17bee3c2705495b638d81ae2ad374
> > bf7494c3f3>
> >
> > github.com
> > …hout#326
> >
> >
> >
> > (make Native Solvers Scala 2.11 compliant) and others peppered in, Post
> > 0.13.0. It still may be possible and not that hard, to cherrypick
> > everything after 0.13.0 that we want. But I see what you're saying
about
> it
> > not being completely simple.
> >
> >
> > As for Git-Flow. I dont really care. I use it in some projects and in
> > others i use GitHub-flow. (basically what we've been doing with merging
> > everything to master).
> >
> >
> > Though this exact problem that we have right now is why git-flow is
nice.
> > Lets separate the question of how we go forward, with what commit/repo
> > style, and First figure out how to back out what we have now, without
> > loosing all of the work that you did on the multi artifact build.
> >
> >
> > What do you think about reverting to 0.13.0, and cherry picking commits
> > like Sparse Speedup:
> > https://github.com/apache/mahout/commit/800a9ed6d7e015aa82b9eb7624bb44
> > 1b71a8f397
> > or checking out entire folders like `website`?
> >
> > [https://avatars3.githubusercontent.com/u/326731?s=200&v=4]<
> > https://github.com/apache/mahout/commit/800a9ed6d7e015aa82b9eb7624bb44
[https://avatars3.githubusercontent.com/u/326731?s=200&v=4]<https://github.com/apache/mahout/commit/800a9ed6d7e015aa82b9eb7624bb44>

MAHOUT-2019 SparkRow Matrix Speedup and fixing change to scala 2.11 m… · apache/mahout@800a9ed<https://github.com/apache/mahout/commit/800a9ed6d7e015aa82b9eb7624bb44>
github.com
…ade by build script



> > 1b71a8f397>
> >
> >
> > MAHOUT-2019 SparkRow Matrix Speedup and fixing change to scala 2.11 m…
·
> > apache/mahout@800a9ed<
> > https://github.com/apache/mahout/commit/800a9ed6d7e015aa82b9eb7624bb44
[https://avatars3.githubusercontent.com/u/326731?s=200&v=4]<https://github.com/apache/mahout/commit/800a9ed6d7e015aa82b9eb7624bb44>

MAHOUT-2019 SparkRow Matrix Speedup and fixing change to scala 2.11 m… · apache/mahout@800a9ed<https://github.com/apache/mahout/commit/800a9ed6d7e015aa82b9eb7624bb44>
github.com
…ade by build script



> > 1b71a8f397>
> >
> > github.com
> > …ade by build script
> >
> >
> >
> > ________________________________
> > From: Trevor Grant <tr...@gmail.com>
> > Sent: Friday, March 2, 2018 3:58:07 PM
> > To: Mahout Dev List
> > Subject: Re: Spark 2.x/scala 2.11.x release
> >
> > If you revert master to the release tag you're going to destroy the
> > website.
> >
> > The website pulls and rebuilds from mater whenever Jenkins detects a
> > change.
> >
> > mahout-0.13.0 has no website. So it will pull nothing and there will be
> no
> > site.
> >
> > tg
> >
> >
> > On Fri, Mar 2, 2018 at 1:24 PM, Andrew Palumbo <ap...@outlook.com>
> wrote:
> >
> > >
> > > Sounds Good. I'll put out a proposal for the release, and we can go
> Over
> > > it and vote if we want to on releasing or on the scope. I'm +1 on it.
> > >
> > >
> > > Broad strokes of what I'm thinking:
> > >
> > >
> > > - Checkout a new branch "features/multi-artifact-build-22xx" from
> master
> > > @ the `mahout-0.13.0` release tag.
> > >
> > >
> > > - Revert master back to release tag.
> > >
> > >
> > > - Checkout a new `develop` branch from master @the `mahout-0.13.0`
> > release
> > > tag.
> > >
> > >
> > > - Cherrypick any commits that we'd like to release (E.g.:
> SparseSpeedup)
> > > onto `develop` (along with a PR ad a ticket).
> > >
> > >
> > > - Merge `develop` to `master`, run through Smoke tests, tag master @
> > > `mahout-0.13.1`(automatically), and release.
> > >
> > >
> > > This will also get us to more of a git-flow workflow, as we've
> discussed
> > > moving towards.
> > >
> > >
> > > Thoughts @all?
> > >
> > >
> > > --andy
> > >
> > >
> > >
> > >
> > >
> > >
> > > ________________________________
> > > From: Pat Ferrel <pa...@gmail.com>
> > > Sent: Wednesday, February 28, 2018 2:53:58 PM
> > > To: Andrew Palumbo; dev@mahout.apache.org
> > > Subject: Re: Spark 2.x/scala 2.11.x release
> > >
> > > big +1
> > >
> > > If you are planning to branch off the 0.13.0 tag let me know, I have
a
> > > speedup that is in my scala 2.11 fork of 0.13.0 that needs to be
> released
> > >
> > >
> > > From: Andrew Palumbo <ap...@outlook.com>
> > > Reply: dev@mahout.apache.org<ma...@mahout.apache.org> <
> > > dev@mahout.apache.org><ma...@mahout.apache.org>
> > > Date: February 28, 2018 at 11:16:12 AM
> > > To: dev@mahout.apache.org<ma...@mahout.apache.org> <
> > > dev@mahout.apache.org><ma...@mahout.apache.org>
> > > Subject: Spark 2.x/scala 2.11.x release
> > >
> > > After some offline discussion regarding people's needs for Spark and
> 2.x
> > > and Scala 2.11.x, I am wondering If we should just consider a release
> for
> > > 2.x and 2.11.x as the default. We could release from the current
> master,
> > or
> > > branch back off of the 0.13.0 tag, and release that with the upgraded
> > > defaults, and branch our current multi-artifact build off as a
feature.
> > Any
> > > thoughts on this?
> > >
> > >
> > > --andy
> > >
> >
>

Re: Spark 2.x/scala 2.11.x release

[Pat Ferrel <pa...@occamsmachete.com>]

LGTM


From: Andrew Palumbo <ap...@outlook.com> <ap...@outlook.com>
Reply: dev@mahout.apache.org <de...@mahout.apache.org> <de...@mahout.apache.org>
Date: March 2, 2018 at 3:38:38 PM
To: dev@mahout.apache.org <de...@mahout.apache.org> <de...@mahout.apache.org>
Subject:  Re: Spark 2.x/scala 2.11.x release

I've started a gdoc for a plan.


https://docs.google.com/document/d/1A8aqUORPp83vWa6fSqhC2jxUKEbDWWQ2lzqZ1V0xHS0/edit?usp=sharing


Please add comments, criticision, and alternate plans on on the doc.


--andy

________________________________
From: Andrew Palumbo <ap...@outlook.com>
Sent: Friday, March 2, 2018 6:11:53 PM
To: dev@mahout.apache.org
Subject: Re: Spark 2.x/scala 2.11.x release

Pat, could you explain what you mean by the "Real Problem"? I know that we
have a lot of problems, but in terms of this release, what is the major
blocker?
________________________________
From: Pat Ferrel <pa...@occamsmachete.com>
Sent: Friday, March 2, 2018 5:32:58 PM
To: Trevor Grant; dev@mahout.apache.org
Subject: Re: Spark 2.x/scala 2.11.x release

Scopt is so not an issue. None whatsoever. The problem is that drivers have
unmet runtime needs that are different than libs. Scopt has absolutely
nothing to do with this. It was from a false theory that there was no 2.11
version but it actually has 2.11, 2.12, 2.09, and according to D a native
version too.

Get on to the real problems and drop this non-problem. Anything that driver
needs but is not on the classpath will stop them at runtime.

Better to say that we would be closer to release if we dropped drivers.


From: Trevor Grant <tr...@gmail.com> <tr...@gmail.com>
Reply: dev@mahout.apache.org <de...@mahout.apache.org> <de...@mahout.apache.org>

Date: March 2, 2018 at 2:26:13 PM
To: Mahout Dev List <de...@mahout.apache.org> <de...@mahout.apache.org>
Subject: Re: Spark 2.x/scala 2.11.x release

Supposedly. I hard coded all of the poms to Scala 2.11 (closed PR unmerged)
Pat was still having issues w sbt- but the only dependency that was on 2.10
according to maven was scopt. /shrug



On Mar 2, 2018 4:20 PM, "Andrew Palumbo" <ap...@outlook.com> wrote:

> So We could release as is if we can get the scopt issue out? Thats our
> final blocker?
>
> ________________________________
> From: Trevor Grant <tr...@gmail.com>
> Sent: Friday, March 2, 2018 5:15:35 PM
> To: Mahout Dev List
> Subject: Re: Spark 2.x/scala 2.11.x release
>
> The only "mess" is in the cli spark drivers, namely scopt.
>
> Get rid of the drivers/fix the scopt issue- we have no mess.
>
>
>
> On Mar 2, 2018 4:09 PM, "Pat Ferrel" <pa...@occamsmachete.com> wrote:
>
> > BTW the mess master is in is why git flow was invented and why I asked
> that
> > the site be in a new repo so it could be on a separate release cycle.
We
> > perpetuate the mess because it’s always to hard to fix.
> >
> >
> > From: Andrew Palumbo <ap...@outlook.com> <ap...@outlook.com>
> > Reply: dev@mahout.apache.org <de...@mahout.apache.org> <
> > dev@mahout.apache.org>
> > Date: March 2, 2018 at 1:54:51 PM
> > To: dev@mahout.apache.org <de...@mahout.apache.org> <dev@mahout.apache.org
> >
> > Subject: Re: Spark 2.x/scala 2.11.x release
> >
> > re: reverting master, shit. I forgot that the website is not on
> `asf-site`
> > anymore. Well we could just re-jigger it, and check out `website` from
> > features/multi-artifact-build-MAHOUT-20xx after we revert the rest of
> > master.
> >
> >
> > You're right, Trevor- I 'm just going through the commits, and there
are
> > things like
> > https://github.com/apache/mahout/commit/c17bee3c2705495b638d81ae2ad374
> > bf7494c3f3
> >
> >
> >
> > [https://avatars3.githubusercontent.com/u/5852441?s=200&v=4]<
> > https://github.com/apache/mahout/commit/c17bee3c2705495b638d81ae2ad374
> > bf7494c3f3>
> >
> >
> > MAHOUT-1988 Make Native Solvers Scala 2.11 Complient closes apache/ma…
·
> > apache/mahout@c17bee3<
> > https://github.com/apache/mahout/commit/c17bee3c2705495b638d81ae2ad374
> > bf7494c3f3>
> >
> > github.com
> > …hout#326
> >
> >
> >
> > (make Native Solvers Scala 2.11 compliant) and others peppered in, Post
> > 0.13.0. It still may be possible and not that hard, to cherrypick
> > everything after 0.13.0 that we want. But I see what you're saying
about
> it
> > not being completely simple.
> >
> >
> > As for Git-Flow. I dont really care. I use it in some projects and in
> > others i use GitHub-flow. (basically what we've been doing with merging
> > everything to master).
> >
> >
> > Though this exact problem that we have right now is why git-flow is
nice.
> > Lets separate the question of how we go forward, with what commit/repo
> > style, and First figure out how to back out what we have now, without
> > loosing all of the work that you did on the multi artifact build.
> >
> >
> > What do you think about reverting to 0.13.0, and cherry picking commits
> > like Sparse Speedup:
> > https://github.com/apache/mahout/commit/800a9ed6d7e015aa82b9eb7624bb44
> > 1b71a8f397
> > or checking out entire folders like `website`?
> >
> > [https://avatars3.githubusercontent.com/u/326731?s=200&v=4]<
> > https://github.com/apache/mahout/commit/800a9ed6d7e015aa82b9eb7624bb44
> > 1b71a8f397>
> >
> >
> > MAHOUT-2019 SparkRow Matrix Speedup and fixing change to scala 2.11 m…
·
> > apache/mahout@800a9ed<
> > https://github.com/apache/mahout/commit/800a9ed6d7e015aa82b9eb7624bb44
> > 1b71a8f397>
> >
> > github.com
> > …ade by build script
> >
> >
> >
> > ________________________________
> > From: Trevor Grant <tr...@gmail.com>
> > Sent: Friday, March 2, 2018 3:58:07 PM
> > To: Mahout Dev List
> > Subject: Re: Spark 2.x/scala 2.11.x release
> >
> > If you revert master to the release tag you're going to destroy the
> > website.
> >
> > The website pulls and rebuilds from mater whenever Jenkins detects a
> > change.
> >
> > mahout-0.13.0 has no website. So it will pull nothing and there will be
> no
> > site.
> >
> > tg
> >
> >
> > On Fri, Mar 2, 2018 at 1:24 PM, Andrew Palumbo <ap...@outlook.com>
> wrote:
> >
> > >
> > > Sounds Good. I'll put out a proposal for the release, and we can go
> Over
> > > it and vote if we want to on releasing or on the scope. I'm +1 on it.
> > >
> > >
> > > Broad strokes of what I'm thinking:
> > >
> > >
> > > - Checkout a new branch "features/multi-artifact-build-22xx" from
> master
> > > @ the `mahout-0.13.0` release tag.
> > >
> > >
> > > - Revert master back to release tag.
> > >
> > >
> > > - Checkout a new `develop` branch from master @the `mahout-0.13.0`
> > release
> > > tag.
> > >
> > >
> > > - Cherrypick any commits that we'd like to release (E.g.:
> SparseSpeedup)
> > > onto `develop` (along with a PR ad a ticket).
> > >
> > >
> > > - Merge `develop` to `master`, run through Smoke tests, tag master @
> > > `mahout-0.13.1`(automatically), and release.
> > >
> > >
> > > This will also get us to more of a git-flow workflow, as we've
> discussed
> > > moving towards.
> > >
> > >
> > > Thoughts @all?
> > >
> > >
> > > --andy
> > >
> > >
> > >
> > >
> > >
> > >
> > > ________________________________
> > > From: Pat Ferrel <pa...@gmail.com>
> > > Sent: Wednesday, February 28, 2018 2:53:58 PM
> > > To: Andrew Palumbo; dev@mahout.apache.org
> > > Subject: Re: Spark 2.x/scala 2.11.x release
> > >
> > > big +1
> > >
> > > If you are planning to branch off the 0.13.0 tag let me know, I have
a
> > > speedup that is in my scala 2.11 fork of 0.13.0 that needs to be
> released
> > >
> > >
> > > From: Andrew Palumbo <ap...@outlook.com>
> > > Reply: dev@mahout.apache.org<ma...@mahout.apache.org> <
> > > dev@mahout.apache.org><ma...@mahout.apache.org>
> > > Date: February 28, 2018 at 11:16:12 AM
> > > To: dev@mahout.apache.org<ma...@mahout.apache.org> <
> > > dev@mahout.apache.org><ma...@mahout.apache.org>
> > > Subject: Spark 2.x/scala 2.11.x release
> > >
> > > After some offline discussion regarding people's needs for Spark and
> 2.x
> > > and Scala 2.11.x, I am wondering If we should just consider a release
> for
> > > 2.x and 2.11.x as the default. We could release from the current
> master,
> > or
> > > branch back off of the 0.13.0 tag, and release that with the upgraded
> > > defaults, and branch our current multi-artifact build off as a
feature.
> > Any
> > > thoughts on this?
> > >
> > >
> > > --andy
> > >
> >
>

Re: Spark 2.x/scala 2.11.x release

[Andrew Palumbo <ap...@outlook.com>]

I've started a gdoc for a plan.


https://docs.google.com/document/d/1A8aqUORPp83vWa6fSqhC2jxUKEbDWWQ2lzqZ1V0xHS0/edit?usp=sharing


Please add comments, criticision, and alternate plans on on the doc.


--andy

________________________________
From: Andrew Palumbo <ap...@outlook.com>
Sent: Friday, March 2, 2018 6:11:53 PM
To: dev@mahout.apache.org
Subject: Re: Spark 2.x/scala 2.11.x release

Pat, could you explain what you mean by the "Real Problem"?  I know that we have a lot of problems, but in terms of this release, what is the major blocker?
________________________________
From: Pat Ferrel <pa...@occamsmachete.com>
Sent: Friday, March 2, 2018 5:32:58 PM
To: Trevor Grant; dev@mahout.apache.org
Subject: Re: Spark 2.x/scala 2.11.x release

Scopt is so not an issue. None whatsoever. The problem is that drivers have
unmet runtime needs that are different than libs. Scopt has absolutely
nothing to do with this. It was from a false theory that there was no 2.11
version but it actually has 2.11, 2.12, 2.09, and according to D a native
version too.

Get on to the real problems and drop this non-problem. Anything that driver
needs but is not on the classpath will stop them at runtime.

Better to say that we would be closer to release if we dropped drivers.


From: Trevor Grant <tr...@gmail.com> <tr...@gmail.com>
Reply: dev@mahout.apache.org <de...@mahout.apache.org> <de...@mahout.apache.org>
Date: March 2, 2018 at 2:26:13 PM
To: Mahout Dev List <de...@mahout.apache.org> <de...@mahout.apache.org>
Subject:  Re: Spark 2.x/scala 2.11.x release

Supposedly. I hard coded all of the poms to Scala 2.11 (closed PR unmerged)
Pat was still having issues w sbt- but the only dependency that was on 2.10
according to maven was scopt. /shrug



On Mar 2, 2018 4:20 PM, "Andrew Palumbo" <ap...@outlook.com> wrote:

> So We could release as is if we can get the scopt issue out? Thats our
> final blocker?
>
> ________________________________
> From: Trevor Grant <tr...@gmail.com>
> Sent: Friday, March 2, 2018 5:15:35 PM
> To: Mahout Dev List
> Subject: Re: Spark 2.x/scala 2.11.x release
>
> The only "mess" is in the cli spark drivers, namely scopt.
>
> Get rid of the drivers/fix the scopt issue- we have no mess.
>
>
>
> On Mar 2, 2018 4:09 PM, "Pat Ferrel" <pa...@occamsmachete.com> wrote:
>
> > BTW the mess master is in is why git flow was invented and why I asked
> that
> > the site be in a new repo so it could be on a separate release cycle.
We
> > perpetuate the mess because it’s always to hard to fix.
> >
> >
> > From: Andrew Palumbo <ap...@outlook.com> <ap...@outlook.com>
> > Reply: dev@mahout.apache.org <de...@mahout.apache.org> <
> > dev@mahout.apache.org>
> > Date: March 2, 2018 at 1:54:51 PM
> > To: dev@mahout.apache.org <de...@mahout.apache.org> <dev@mahout.apache.org
> >
> > Subject: Re: Spark 2.x/scala 2.11.x release
> >
> > re: reverting master, shit. I forgot that the website is not on
> `asf-site`
> > anymore. Well we could just re-jigger it, and check out `website` from
> > features/multi-artifact-build-MAHOUT-20xx after we revert the rest of
> > master.
> >
> >
> > You're right, Trevor- I 'm just going through the commits, and there
are
> > things like
> > https://github.com/apache/mahout/commit/c17bee3c2705495b638d81ae2ad374
> > bf7494c3f3
> >
> >
> >
> > [https://avatars3.githubusercontent.com/u/5852441?s=200&v=4]<
> > https://github.com/apache/mahout/commit/c17bee3c2705495b638d81ae2ad374
> > bf7494c3f3>
> >
> >
> > MAHOUT-1988 Make Native Solvers Scala 2.11 Complient closes apache/ma…
·
> > apache/mahout@c17bee3<
> > https://github.com/apache/mahout/commit/c17bee3c2705495b638d81ae2ad374
> > bf7494c3f3>
> >
> > github.com
> > …hout#326
> >
> >
> >
> > (make Native Solvers Scala 2.11 compliant) and others peppered in, Post
> > 0.13.0. It still may be possible and not that hard, to cherrypick
> > everything after 0.13.0 that we want. But I see what you're saying
about
> it
> > not being completely simple.
> >
> >
> > As for Git-Flow. I dont really care. I use it in some projects and in
> > others i use GitHub-flow. (basically what we've been doing with merging
> > everything to master).
> >
> >
> > Though this exact problem that we have right now is why git-flow is
nice.
> > Lets separate the question of how we go forward, with what commit/repo
> > style, and First figure out how to back out what we have now, without
> > loosing all of the work that you did on the multi artifact build.
> >
> >
> > What do you think about reverting to 0.13.0, and cherry picking commits
> > like Sparse Speedup:
> > https://github.com/apache/mahout/commit/800a9ed6d7e015aa82b9eb7624bb44
> > 1b71a8f397
> > or checking out entire folders like `website`?
> >
> > [https://avatars3.githubusercontent.com/u/326731?s=200&v=4]<
> > https://github.com/apache/mahout/commit/800a9ed6d7e015aa82b9eb7624bb44
> > 1b71a8f397>
> >
> >
> > MAHOUT-2019 SparkRow Matrix Speedup and fixing change to scala 2.11 m…
·
> > apache/mahout@800a9ed<
> > https://github.com/apache/mahout/commit/800a9ed6d7e015aa82b9eb7624bb44
> > 1b71a8f397>
> >
> > github.com
> > …ade by build script
> >
> >
> >
> > ________________________________
> > From: Trevor Grant <tr...@gmail.com>
> > Sent: Friday, March 2, 2018 3:58:07 PM
> > To: Mahout Dev List
> > Subject: Re: Spark 2.x/scala 2.11.x release
> >
> > If you revert master to the release tag you're going to destroy the
> > website.
> >
> > The website pulls and rebuilds from mater whenever Jenkins detects a
> > change.
> >
> > mahout-0.13.0 has no website. So it will pull nothing and there will be
> no
> > site.
> >
> > tg
> >
> >
> > On Fri, Mar 2, 2018 at 1:24 PM, Andrew Palumbo <ap...@outlook.com>
> wrote:
> >
> > >
> > > Sounds Good. I'll put out a proposal for the release, and we can go
> Over
> > > it and vote if we want to on releasing or on the scope. I'm +1 on it.
> > >
> > >
> > > Broad strokes of what I'm thinking:
> > >
> > >
> > > - Checkout a new branch "features/multi-artifact-build-22xx" from
> master
> > > @ the `mahout-0.13.0` release tag.
> > >
> > >
> > > - Revert master back to release tag.
> > >
> > >
> > > - Checkout a new `develop` branch from master @the `mahout-0.13.0`
> > release
> > > tag.
> > >
> > >
> > > - Cherrypick any commits that we'd like to release (E.g.:
> SparseSpeedup)
> > > onto `develop` (along with a PR ad a ticket).
> > >
> > >
> > > - Merge `develop` to `master`, run through Smoke tests, tag master @
> > > `mahout-0.13.1`(automatically), and release.
> > >
> > >
> > > This will also get us to more of a git-flow workflow, as we've
> discussed
> > > moving towards.
> > >
> > >
> > > Thoughts @all?
> > >
> > >
> > > --andy
> > >
> > >
> > >
> > >
> > >
> > >
> > > ________________________________
> > > From: Pat Ferrel <pa...@gmail.com>
> > > Sent: Wednesday, February 28, 2018 2:53:58 PM
> > > To: Andrew Palumbo; dev@mahout.apache.org
> > > Subject: Re: Spark 2.x/scala 2.11.x release
> > >
> > > big +1
> > >
> > > If you are planning to branch off the 0.13.0 tag let me know, I have
a
> > > speedup that is in my scala 2.11 fork of 0.13.0 that needs to be
> released
> > >
> > >
> > > From: Andrew Palumbo <ap...@outlook.com>
> > > Reply: dev@mahout.apache.org<ma...@mahout.apache.org> <
> > > dev@mahout.apache.org><ma...@mahout.apache.org>
> > > Date: February 28, 2018 at 11:16:12 AM
> > > To: dev@mahout.apache.org<ma...@mahout.apache.org> <
> > > dev@mahout.apache.org><ma...@mahout.apache.org>
> > > Subject: Spark 2.x/scala 2.11.x release
> > >
> > > After some offline discussion regarding people's needs for Spark and
> 2.x
> > > and Scala 2.11.x, I am wondering If we should just consider a release
> for
> > > 2.x and 2.11.x as the default. We could release from the current
> master,
> > or
> > > branch back off of the 0.13.0 tag, and release that with the upgraded
> > > defaults, and branch our current multi-artifact build off as a
feature.
> > Any
> > > thoughts on this?
> > >
> > >
> > > --andy
> > >
> >
>

Re: Spark 2.x/scala 2.11.x release

[Andrew Palumbo <ap...@outlook.com>]

Pat, could you explain what you mean by the "Real Problem"?  I know that we have a lot of problems, but in terms of this release, what is the major blocker?
________________________________
From: Pat Ferrel <pa...@occamsmachete.com>
Sent: Friday, March 2, 2018 5:32:58 PM
To: Trevor Grant; dev@mahout.apache.org
Subject: Re: Spark 2.x/scala 2.11.x release

Scopt is so not an issue. None whatsoever. The problem is that drivers have
unmet runtime needs that are different than libs. Scopt has absolutely
nothing to do with this. It was from a false theory that there was no 2.11
version but it actually has 2.11, 2.12, 2.09, and according to D a native
version too.

Get on to the real problems and drop this non-problem. Anything that driver
needs but is not on the classpath will stop them at runtime.

Better to say that we would be closer to release if we dropped drivers.


From: Trevor Grant <tr...@gmail.com> <tr...@gmail.com>
Reply: dev@mahout.apache.org <de...@mahout.apache.org> <de...@mahout.apache.org>
Date: March 2, 2018 at 2:26:13 PM
To: Mahout Dev List <de...@mahout.apache.org> <de...@mahout.apache.org>
Subject:  Re: Spark 2.x/scala 2.11.x release

Supposedly. I hard coded all of the poms to Scala 2.11 (closed PR unmerged)
Pat was still having issues w sbt- but the only dependency that was on 2.10
according to maven was scopt. /shrug



On Mar 2, 2018 4:20 PM, "Andrew Palumbo" <ap...@outlook.com> wrote:

> So We could release as is if we can get the scopt issue out? Thats our
> final blocker?
>
> ________________________________
> From: Trevor Grant <tr...@gmail.com>
> Sent: Friday, March 2, 2018 5:15:35 PM
> To: Mahout Dev List
> Subject: Re: Spark 2.x/scala 2.11.x release
>
> The only "mess" is in the cli spark drivers, namely scopt.
>
> Get rid of the drivers/fix the scopt issue- we have no mess.
>
>
>
> On Mar 2, 2018 4:09 PM, "Pat Ferrel" <pa...@occamsmachete.com> wrote:
>
> > BTW the mess master is in is why git flow was invented and why I asked
> that
> > the site be in a new repo so it could be on a separate release cycle.
We
> > perpetuate the mess because it’s always to hard to fix.
> >
> >
> > From: Andrew Palumbo <ap...@outlook.com> <ap...@outlook.com>
> > Reply: dev@mahout.apache.org <de...@mahout.apache.org> <
> > dev@mahout.apache.org>
> > Date: March 2, 2018 at 1:54:51 PM
> > To: dev@mahout.apache.org <de...@mahout.apache.org> <dev@mahout.apache.org
> >
> > Subject: Re: Spark 2.x/scala 2.11.x release
> >
> > re: reverting master, shit. I forgot that the website is not on
> `asf-site`
> > anymore. Well we could just re-jigger it, and check out `website` from
> > features/multi-artifact-build-MAHOUT-20xx after we revert the rest of
> > master.
> >
> >
> > You're right, Trevor- I 'm just going through the commits, and there
are
> > things like
> > https://github.com/apache/mahout/commit/c17bee3c2705495b638d81ae2ad374
> > bf7494c3f3
> >
> >
> >
> > [https://avatars3.githubusercontent.com/u/5852441?s=200&v=4]<
> > https://github.com/apache/mahout/commit/c17bee3c2705495b638d81ae2ad374
> > bf7494c3f3>
> >
> >
> > MAHOUT-1988 Make Native Solvers Scala 2.11 Complient closes apache/ma…
·
> > apache/mahout@c17bee3<
> > https://github.com/apache/mahout/commit/c17bee3c2705495b638d81ae2ad374
> > bf7494c3f3>
> >
> > github.com
> > …hout#326
> >
> >
> >
> > (make Native Solvers Scala 2.11 compliant) and others peppered in, Post
> > 0.13.0. It still may be possible and not that hard, to cherrypick
> > everything after 0.13.0 that we want. But I see what you're saying
about
> it
> > not being completely simple.
> >
> >
> > As for Git-Flow. I dont really care. I use it in some projects and in
> > others i use GitHub-flow. (basically what we've been doing with merging
> > everything to master).
> >
> >
> > Though this exact problem that we have right now is why git-flow is
nice.
> > Lets separate the question of how we go forward, with what commit/repo
> > style, and First figure out how to back out what we have now, without
> > loosing all of the work that you did on the multi artifact build.
> >
> >
> > What do you think about reverting to 0.13.0, and cherry picking commits
> > like Sparse Speedup:
> > https://github.com/apache/mahout/commit/800a9ed6d7e015aa82b9eb7624bb44
> > 1b71a8f397
> > or checking out entire folders like `website`?
> >
> > [https://avatars3.githubusercontent.com/u/326731?s=200&v=4]<
> > https://github.com/apache/mahout/commit/800a9ed6d7e015aa82b9eb7624bb44
> > 1b71a8f397>
> >
> >
> > MAHOUT-2019 SparkRow Matrix Speedup and fixing change to scala 2.11 m…
·
> > apache/mahout@800a9ed<
> > https://github.com/apache/mahout/commit/800a9ed6d7e015aa82b9eb7624bb44
> > 1b71a8f397>
> >
> > github.com
> > …ade by build script
> >
> >
> >
> > ________________________________
> > From: Trevor Grant <tr...@gmail.com>
> > Sent: Friday, March 2, 2018 3:58:07 PM
> > To: Mahout Dev List
> > Subject: Re: Spark 2.x/scala 2.11.x release
> >
> > If you revert master to the release tag you're going to destroy the
> > website.
> >
> > The website pulls and rebuilds from mater whenever Jenkins detects a
> > change.
> >
> > mahout-0.13.0 has no website. So it will pull nothing and there will be
> no
> > site.
> >
> > tg
> >
> >
> > On Fri, Mar 2, 2018 at 1:24 PM, Andrew Palumbo <ap...@outlook.com>
> wrote:
> >
> > >
> > > Sounds Good. I'll put out a proposal for the release, and we can go
> Over
> > > it and vote if we want to on releasing or on the scope. I'm +1 on it.
> > >
> > >
> > > Broad strokes of what I'm thinking:
> > >
> > >
> > > - Checkout a new branch "features/multi-artifact-build-22xx" from
> master
> > > @ the `mahout-0.13.0` release tag.
> > >
> > >
> > > - Revert master back to release tag.
> > >
> > >
> > > - Checkout a new `develop` branch from master @the `mahout-0.13.0`
> > release
> > > tag.
> > >
> > >
> > > - Cherrypick any commits that we'd like to release (E.g.:
> SparseSpeedup)
> > > onto `develop` (along with a PR ad a ticket).
> > >
> > >
> > > - Merge `develop` to `master`, run through Smoke tests, tag master @
> > > `mahout-0.13.1`(automatically), and release.
> > >
> > >
> > > This will also get us to more of a git-flow workflow, as we've
> discussed
> > > moving towards.
> > >
> > >
> > > Thoughts @all?
> > >
> > >
> > > --andy
> > >
> > >
> > >
> > >
> > >
> > >
> > > ________________________________
> > > From: Pat Ferrel <pa...@gmail.com>
> > > Sent: Wednesday, February 28, 2018 2:53:58 PM
> > > To: Andrew Palumbo; dev@mahout.apache.org
> > > Subject: Re: Spark 2.x/scala 2.11.x release
> > >
> > > big +1
> > >
> > > If you are planning to branch off the 0.13.0 tag let me know, I have
a
> > > speedup that is in my scala 2.11 fork of 0.13.0 that needs to be
> released
> > >
> > >
> > > From: Andrew Palumbo <ap...@outlook.com>
> > > Reply: dev@mahout.apache.org<ma...@mahout.apache.org> <
> > > dev@mahout.apache.org><ma...@mahout.apache.org>
> > > Date: February 28, 2018 at 11:16:12 AM
> > > To: dev@mahout.apache.org<ma...@mahout.apache.org> <
> > > dev@mahout.apache.org><ma...@mahout.apache.org>
> > > Subject: Spark 2.x/scala 2.11.x release
> > >
> > > After some offline discussion regarding people's needs for Spark and
> 2.x
> > > and Scala 2.11.x, I am wondering If we should just consider a release
> for
> > > 2.x and 2.11.x as the default. We could release from the current
> master,
> > or
> > > branch back off of the 0.13.0 tag, and release that with the upgraded
> > > defaults, and branch our current multi-artifact build off as a
feature.
> > Any
> > > thoughts on this?
> > >
> > >
> > > --andy
> > >
> >
>

Re: Spark 2.x/scala 2.11.x release

[Pat Ferrel <pa...@occamsmachete.com>]

Scopt is so not an issue. None whatsoever. The problem is that drivers have
unmet runtime needs that are different than libs. Scopt has absolutely
nothing to do with this. It was from a false theory that there was no 2.11
version but it actually has 2.11, 2.12, 2.09, and according to D a native
version too.

Get on to the real problems and drop this non-problem. Anything that driver
needs but is not on the classpath will stop them at runtime.

Better to say that we would be closer to release if we dropped drivers.


From: Trevor Grant <tr...@gmail.com> <tr...@gmail.com>
Reply: dev@mahout.apache.org <de...@mahout.apache.org> <de...@mahout.apache.org>
Date: March 2, 2018 at 2:26:13 PM
To: Mahout Dev List <de...@mahout.apache.org> <de...@mahout.apache.org>
Subject:  Re: Spark 2.x/scala 2.11.x release

Supposedly. I hard coded all of the poms to Scala 2.11 (closed PR unmerged)
Pat was still having issues w sbt- but the only dependency that was on 2.10
according to maven was scopt. /shrug



On Mar 2, 2018 4:20 PM, "Andrew Palumbo" <ap...@outlook.com> wrote:

> So We could release as is if we can get the scopt issue out? Thats our
> final blocker?
>
> ________________________________
> From: Trevor Grant <tr...@gmail.com>
> Sent: Friday, March 2, 2018 5:15:35 PM
> To: Mahout Dev List
> Subject: Re: Spark 2.x/scala 2.11.x release
>
> The only "mess" is in the cli spark drivers, namely scopt.
>
> Get rid of the drivers/fix the scopt issue- we have no mess.
>
>
>
> On Mar 2, 2018 4:09 PM, "Pat Ferrel" <pa...@occamsmachete.com> wrote:
>
> > BTW the mess master is in is why git flow was invented and why I asked
> that
> > the site be in a new repo so it could be on a separate release cycle.
We
> > perpetuate the mess because it’s always to hard to fix.
> >
> >
> > From: Andrew Palumbo <ap...@outlook.com> <ap...@outlook.com>
> > Reply: dev@mahout.apache.org <de...@mahout.apache.org> <
> > dev@mahout.apache.org>
> > Date: March 2, 2018 at 1:54:51 PM
> > To: dev@mahout.apache.org <de...@mahout.apache.org> <dev@mahout.apache.org
> >
> > Subject: Re: Spark 2.x/scala 2.11.x release
> >
> > re: reverting master, shit. I forgot that the website is not on
> `asf-site`
> > anymore. Well we could just re-jigger it, and check out `website` from
> > features/multi-artifact-build-MAHOUT-20xx after we revert the rest of
> > master.
> >
> >
> > You're right, Trevor- I 'm just going through the commits, and there
are
> > things like
> > https://github.com/apache/mahout/commit/c17bee3c2705495b638d81ae2ad374
> > bf7494c3f3
> >
> >
> >
> > [https://avatars3.githubusercontent.com/u/5852441?s=200&v=4]<
> > https://github.com/apache/mahout/commit/c17bee3c2705495b638d81ae2ad374
> > bf7494c3f3>
> >
> >
> > MAHOUT-1988 Make Native Solvers Scala 2.11 Complient closes apache/ma…
·
> > apache/mahout@c17bee3<
> > https://github.com/apache/mahout/commit/c17bee3c2705495b638d81ae2ad374
> > bf7494c3f3>
> >
> > github.com
> > …hout#326
> >
> >
> >
> > (make Native Solvers Scala 2.11 compliant) and others peppered in, Post
> > 0.13.0. It still may be possible and not that hard, to cherrypick
> > everything after 0.13.0 that we want. But I see what you're saying
about
> it
> > not being completely simple.
> >
> >
> > As for Git-Flow. I dont really care. I use it in some projects and in
> > others i use GitHub-flow. (basically what we've been doing with merging
> > everything to master).
> >
> >
> > Though this exact problem that we have right now is why git-flow is
nice.
> > Lets separate the question of how we go forward, with what commit/repo
> > style, and First figure out how to back out what we have now, without
> > loosing all of the work that you did on the multi artifact build.
> >
> >
> > What do you think about reverting to 0.13.0, and cherry picking commits
> > like Sparse Speedup:
> > https://github.com/apache/mahout/commit/800a9ed6d7e015aa82b9eb7624bb44
> > 1b71a8f397
> > or checking out entire folders like `website`?
> >
> > [https://avatars3.githubusercontent.com/u/326731?s=200&v=4]<
> > https://github.com/apache/mahout/commit/800a9ed6d7e015aa82b9eb7624bb44
> > 1b71a8f397>
> >
> >
> > MAHOUT-2019 SparkRow Matrix Speedup and fixing change to scala 2.11 m…
·
> > apache/mahout@800a9ed<
> > https://github.com/apache/mahout/commit/800a9ed6d7e015aa82b9eb7624bb44
> > 1b71a8f397>
> >
> > github.com
> > …ade by build script
> >
> >
> >
> > ________________________________
> > From: Trevor Grant <tr...@gmail.com>
> > Sent: Friday, March 2, 2018 3:58:07 PM
> > To: Mahout Dev List
> > Subject: Re: Spark 2.x/scala 2.11.x release
> >
> > If you revert master to the release tag you're going to destroy the
> > website.
> >
> > The website pulls and rebuilds from mater whenever Jenkins detects a
> > change.
> >
> > mahout-0.13.0 has no website. So it will pull nothing and there will be
> no
> > site.
> >
> > tg
> >
> >
> > On Fri, Mar 2, 2018 at 1:24 PM, Andrew Palumbo <ap...@outlook.com>
> wrote:
> >
> > >
> > > Sounds Good. I'll put out a proposal for the release, and we can go
> Over
> > > it and vote if we want to on releasing or on the scope. I'm +1 on it.
> > >
> > >
> > > Broad strokes of what I'm thinking:
> > >
> > >
> > > - Checkout a new branch "features/multi-artifact-build-22xx" from
> master
> > > @ the `mahout-0.13.0` release tag.
> > >
> > >
> > > - Revert master back to release tag.
> > >
> > >
> > > - Checkout a new `develop` branch from master @the `mahout-0.13.0`
> > release
> > > tag.
> > >
> > >
> > > - Cherrypick any commits that we'd like to release (E.g.:
> SparseSpeedup)
> > > onto `develop` (along with a PR ad a ticket).
> > >
> > >
> > > - Merge `develop` to `master`, run through Smoke tests, tag master @
> > > `mahout-0.13.1`(automatically), and release.
> > >
> > >
> > > This will also get us to more of a git-flow workflow, as we've
> discussed
> > > moving towards.
> > >
> > >
> > > Thoughts @all?
> > >
> > >
> > > --andy
> > >
> > >
> > >
> > >
> > >
> > >
> > > ________________________________
> > > From: Pat Ferrel <pa...@gmail.com>
> > > Sent: Wednesday, February 28, 2018 2:53:58 PM
> > > To: Andrew Palumbo; dev@mahout.apache.org
> > > Subject: Re: Spark 2.x/scala 2.11.x release
> > >
> > > big +1
> > >
> > > If you are planning to branch off the 0.13.0 tag let me know, I have
a
> > > speedup that is in my scala 2.11 fork of 0.13.0 that needs to be
> released
> > >
> > >
> > > From: Andrew Palumbo <ap...@outlook.com>
> > > Reply: dev@mahout.apache.org<ma...@mahout.apache.org> <
> > > dev@mahout.apache.org><ma...@mahout.apache.org>
> > > Date: February 28, 2018 at 11:16:12 AM
> > > To: dev@mahout.apache.org<ma...@mahout.apache.org> <
> > > dev@mahout.apache.org><ma...@mahout.apache.org>
> > > Subject: Spark 2.x/scala 2.11.x release
> > >
> > > After some offline discussion regarding people's needs for Spark and
> 2.x
> > > and Scala 2.11.x, I am wondering If we should just consider a release
> for
> > > 2.x and 2.11.x as the default. We could release from the current
> master,
> > or
> > > branch back off of the 0.13.0 tag, and release that with the upgraded
> > > defaults, and branch our current multi-artifact build off as a
feature.
> > Any
> > > thoughts on this?
> > >
> > >
> > > --andy
> > >
> >
>

Re: Spark 2.x/scala 2.11.x release

[Trevor Grant <tr...@gmail.com>]

Supposedly. I hard coded all of the poms to Scala 2.11 (closed PR unmerged)
Pat was still having issues w sbt- but the only dependency that was on 2.10
according to maven was scopt. /shrug



On Mar 2, 2018 4:20 PM, "Andrew Palumbo" <ap...@outlook.com> wrote:

> So We could release as is if we can get the scopt issue out?  Thats our
> final blocker?
>
> ________________________________
> From: Trevor Grant <tr...@gmail.com>
> Sent: Friday, March 2, 2018 5:15:35 PM
> To: Mahout Dev List
> Subject: Re: Spark 2.x/scala 2.11.x release
>
> The only "mess" is in the cli spark drivers, namely scopt.
>
> Get rid of the drivers/fix the scopt issue- we have no mess.
>
>
>
> On Mar 2, 2018 4:09 PM, "Pat Ferrel" <pa...@occamsmachete.com> wrote:
>
> > BTW the mess master is in is why git flow was invented and why I asked
> that
> > the site be in a new repo so it could be on a separate release cycle. We
> > perpetuate the mess because it’s always to hard to fix.
> >
> >
> > From: Andrew Palumbo <ap...@outlook.com> <ap...@outlook.com>
> > Reply: dev@mahout.apache.org <de...@mahout.apache.org> <
> > dev@mahout.apache.org>
> > Date: March 2, 2018 at 1:54:51 PM
> > To: dev@mahout.apache.org <de...@mahout.apache.org> <dev@mahout.apache.org
> >
> > Subject:  Re: Spark 2.x/scala 2.11.x release
> >
> > re: reverting master, shit. I forgot that the website is not on
> `asf-site`
> > anymore. Well we could just re-jigger it, and check out `website` from
> > features/multi-artifact-build-MAHOUT-20xx after we revert the rest of
> > master.
> >
> >
> > You're right, Trevor- I 'm just going through the commits, and there are
> > things like
> > https://github.com/apache/mahout/commit/c17bee3c2705495b638d81ae2ad374
> > bf7494c3f3
> >
> >
> >
> > [https://avatars3.githubusercontent.com/u/5852441?s=200&v=4]<
> > https://github.com/apache/mahout/commit/c17bee3c2705495b638d81ae2ad374
> > bf7494c3f3>
> >
> >
> > MAHOUT-1988 Make Native Solvers Scala 2.11 Complient closes apache/ma… ·
> > apache/mahout@c17bee3<
> > https://github.com/apache/mahout/commit/c17bee3c2705495b638d81ae2ad374
> > bf7494c3f3>
> >
> > github.com
> > …hout#326
> >
> >
> >
> > (make Native Solvers Scala 2.11 compliant) and others peppered in, Post
> > 0.13.0. It still may be possible and not that hard, to cherrypick
> > everything after 0.13.0 that we want. But I see what you're saying about
> it
> > not being completely simple.
> >
> >
> > As for Git-Flow. I dont really care. I use it in some projects and in
> > others i use GitHub-flow. (basically what we've been doing with merging
> > everything to master).
> >
> >
> > Though this exact problem that we have right now is why git-flow is nice.
> > Lets separate the question of how we go forward, with what commit/repo
> > style, and First figure out how to back out what we have now, without
> > loosing all of the work that you did on the multi artifact build.
> >
> >
> > What do you think about reverting to 0.13.0, and cherry picking commits
> > like Sparse Speedup:
> > https://github.com/apache/mahout/commit/800a9ed6d7e015aa82b9eb7624bb44
> > 1b71a8f397
> > or checking out entire folders like `website`?
> >
> > [https://avatars3.githubusercontent.com/u/326731?s=200&v=4]<
> > https://github.com/apache/mahout/commit/800a9ed6d7e015aa82b9eb7624bb44
> > 1b71a8f397>
> >
> >
> > MAHOUT-2019 SparkRow Matrix Speedup and fixing change to scala 2.11 m… ·
> > apache/mahout@800a9ed<
> > https://github.com/apache/mahout/commit/800a9ed6d7e015aa82b9eb7624bb44
> > 1b71a8f397>
> >
> > github.com
> > …ade by build script
> >
> >
> >
> > ________________________________
> > From: Trevor Grant <tr...@gmail.com>
> > Sent: Friday, March 2, 2018 3:58:07 PM
> > To: Mahout Dev List
> > Subject: Re: Spark 2.x/scala 2.11.x release
> >
> > If you revert master to the release tag you're going to destroy the
> > website.
> >
> > The website pulls and rebuilds from mater whenever Jenkins detects a
> > change.
> >
> > mahout-0.13.0 has no website. So it will pull nothing and there will be
> no
> > site.
> >
> > tg
> >
> >
> > On Fri, Mar 2, 2018 at 1:24 PM, Andrew Palumbo <ap...@outlook.com>
> wrote:
> >
> > >
> > > Sounds Good. I'll put out a proposal for the release, and we can go
> Over
> > > it and vote if we want to on releasing or on the scope. I'm +1 on it.
> > >
> > >
> > > Broad strokes of what I'm thinking:
> > >
> > >
> > > - Checkout a new branch "features/multi-artifact-build-22xx" from
> master
> > > @ the `mahout-0.13.0` release tag.
> > >
> > >
> > > - Revert master back to release tag.
> > >
> > >
> > > - Checkout a new `develop` branch from master @the `mahout-0.13.0`
> > release
> > > tag.
> > >
> > >
> > > - Cherrypick any commits that we'd like to release (E.g.:
> SparseSpeedup)
> > > onto `develop` (along with a PR ad a ticket).
> > >
> > >
> > > - Merge `develop` to `master`, run through Smoke tests, tag master @
> > > `mahout-0.13.1`(automatically), and release.
> > >
> > >
> > > This will also get us to more of a git-flow workflow, as we've
> discussed
> > > moving towards.
> > >
> > >
> > > Thoughts @all?
> > >
> > >
> > > --andy
> > >
> > >
> > >
> > >
> > >
> > >
> > > ________________________________
> > > From: Pat Ferrel <pa...@gmail.com>
> > > Sent: Wednesday, February 28, 2018 2:53:58 PM
> > > To: Andrew Palumbo; dev@mahout.apache.org
> > > Subject: Re: Spark 2.x/scala 2.11.x release
> > >
> > > big +1
> > >
> > > If you are planning to branch off the 0.13.0 tag let me know, I have a
> > > speedup that is in my scala 2.11 fork of 0.13.0 that needs to be
> released
> > >
> > >
> > > From: Andrew Palumbo <ap...@outlook.com>
> > > Reply: dev@mahout.apache.org<ma...@mahout.apache.org> <
> > > dev@mahout.apache.org><ma...@mahout.apache.org>
> > > Date: February 28, 2018 at 11:16:12 AM
> > > To: dev@mahout.apache.org<ma...@mahout.apache.org> <
> > > dev@mahout.apache.org><ma...@mahout.apache.org>
> > > Subject: Spark 2.x/scala 2.11.x release
> > >
> > > After some offline discussion regarding people's needs for Spark and
> 2.x
> > > and Scala 2.11.x, I am wondering If we should just consider a release
> for
> > > 2.x and 2.11.x as the default. We could release from the current
> master,
> > or
> > > branch back off of the 0.13.0 tag, and release that with the upgraded
> > > defaults, and branch our current multi-artifact build off as a feature.
> > Any
> > > thoughts on this?
> > >
> > >
> > > --andy
> > >
> >
>

Re: Spark 2.x/scala 2.11.x release

[Andrew Palumbo <ap...@outlook.com>]

So We could release as is if we can get the scopt issue out?  Thats our final blocker?

________________________________
From: Trevor Grant <tr...@gmail.com>
Sent: Friday, March 2, 2018 5:15:35 PM
To: Mahout Dev List
Subject: Re: Spark 2.x/scala 2.11.x release

The only "mess" is in the cli spark drivers, namely scopt.

Get rid of the drivers/fix the scopt issue- we have no mess.



On Mar 2, 2018 4:09 PM, "Pat Ferrel" <pa...@occamsmachete.com> wrote:

> BTW the mess master is in is why git flow was invented and why I asked that
> the site be in a new repo so it could be on a separate release cycle. We
> perpetuate the mess because it’s always to hard to fix.
>
>
> From: Andrew Palumbo <ap...@outlook.com> <ap...@outlook.com>
> Reply: dev@mahout.apache.org <de...@mahout.apache.org> <
> dev@mahout.apache.org>
> Date: March 2, 2018 at 1:54:51 PM
> To: dev@mahout.apache.org <de...@mahout.apache.org> <de...@mahout.apache.org>
> Subject:  Re: Spark 2.x/scala 2.11.x release
>
> re: reverting master, shit. I forgot that the website is not on `asf-site`
> anymore. Well we could just re-jigger it, and check out `website` from
> features/multi-artifact-build-MAHOUT-20xx after we revert the rest of
> master.
>
>
> You're right, Trevor- I 'm just going through the commits, and there are
> things like
> https://github.com/apache/mahout/commit/c17bee3c2705495b638d81ae2ad374
> bf7494c3f3
>
>
>
> [https://avatars3.githubusercontent.com/u/5852441?s=200&v=4]<
> https://github.com/apache/mahout/commit/c17bee3c2705495b638d81ae2ad374
> bf7494c3f3>
>
>
> MAHOUT-1988 Make Native Solvers Scala 2.11 Complient closes apache/ma… ·
> apache/mahout@c17bee3<
> https://github.com/apache/mahout/commit/c17bee3c2705495b638d81ae2ad374
> bf7494c3f3>
>
> github.com
> …hout#326
>
>
>
> (make Native Solvers Scala 2.11 compliant) and others peppered in, Post
> 0.13.0. It still may be possible and not that hard, to cherrypick
> everything after 0.13.0 that we want. But I see what you're saying about it
> not being completely simple.
>
>
> As for Git-Flow. I dont really care. I use it in some projects and in
> others i use GitHub-flow. (basically what we've been doing with merging
> everything to master).
>
>
> Though this exact problem that we have right now is why git-flow is nice.
> Lets separate the question of how we go forward, with what commit/repo
> style, and First figure out how to back out what we have now, without
> loosing all of the work that you did on the multi artifact build.
>
>
> What do you think about reverting to 0.13.0, and cherry picking commits
> like Sparse Speedup:
> https://github.com/apache/mahout/commit/800a9ed6d7e015aa82b9eb7624bb44
> 1b71a8f397
> or checking out entire folders like `website`?
>
> [https://avatars3.githubusercontent.com/u/326731?s=200&v=4]<
> https://github.com/apache/mahout/commit/800a9ed6d7e015aa82b9eb7624bb44
> 1b71a8f397>
>
>
> MAHOUT-2019 SparkRow Matrix Speedup and fixing change to scala 2.11 m… ·
> apache/mahout@800a9ed<
> https://github.com/apache/mahout/commit/800a9ed6d7e015aa82b9eb7624bb44
> 1b71a8f397>
>
> github.com
> …ade by build script
>
>
>
> ________________________________
> From: Trevor Grant <tr...@gmail.com>
> Sent: Friday, March 2, 2018 3:58:07 PM
> To: Mahout Dev List
> Subject: Re: Spark 2.x/scala 2.11.x release
>
> If you revert master to the release tag you're going to destroy the
> website.
>
> The website pulls and rebuilds from mater whenever Jenkins detects a
> change.
>
> mahout-0.13.0 has no website. So it will pull nothing and there will be no
> site.
>
> tg
>
>
> On Fri, Mar 2, 2018 at 1:24 PM, Andrew Palumbo <ap...@outlook.com> wrote:
>
> >
> > Sounds Good. I'll put out a proposal for the release, and we can go Over
> > it and vote if we want to on releasing or on the scope. I'm +1 on it.
> >
> >
> > Broad strokes of what I'm thinking:
> >
> >
> > - Checkout a new branch "features/multi-artifact-build-22xx" from master
> > @ the `mahout-0.13.0` release tag.
> >
> >
> > - Revert master back to release tag.
> >
> >
> > - Checkout a new `develop` branch from master @the `mahout-0.13.0`
> release
> > tag.
> >
> >
> > - Cherrypick any commits that we'd like to release (E.g.: SparseSpeedup)
> > onto `develop` (along with a PR ad a ticket).
> >
> >
> > - Merge `develop` to `master`, run through Smoke tests, tag master @
> > `mahout-0.13.1`(automatically), and release.
> >
> >
> > This will also get us to more of a git-flow workflow, as we've discussed
> > moving towards.
> >
> >
> > Thoughts @all?
> >
> >
> > --andy
> >
> >
> >
> >
> >
> >
> > ________________________________
> > From: Pat Ferrel <pa...@gmail.com>
> > Sent: Wednesday, February 28, 2018 2:53:58 PM
> > To: Andrew Palumbo; dev@mahout.apache.org
> > Subject: Re: Spark 2.x/scala 2.11.x release
> >
> > big +1
> >
> > If you are planning to branch off the 0.13.0 tag let me know, I have a
> > speedup that is in my scala 2.11 fork of 0.13.0 that needs to be released
> >
> >
> > From: Andrew Palumbo <ap...@outlook.com>
> > Reply: dev@mahout.apache.org<ma...@mahout.apache.org> <
> > dev@mahout.apache.org><ma...@mahout.apache.org>
> > Date: February 28, 2018 at 11:16:12 AM
> > To: dev@mahout.apache.org<ma...@mahout.apache.org> <
> > dev@mahout.apache.org><ma...@mahout.apache.org>
> > Subject: Spark 2.x/scala 2.11.x release
> >
> > After some offline discussion regarding people's needs for Spark and 2.x
> > and Scala 2.11.x, I am wondering If we should just consider a release for
> > 2.x and 2.11.x as the default. We could release from the current master,
> or
> > branch back off of the 0.13.0 tag, and release that with the upgraded
> > defaults, and branch our current multi-artifact build off as a feature.
> Any
> > thoughts on this?
> >
> >
> > --andy
> >
>

Re: Spark 2.x/scala 2.11.x release

[Trevor Grant <tr...@gmail.com>]

The only "mess" is in the cli spark drivers, namely scopt.

Get rid of the drivers/fix the scopt issue- we have no mess.



On Mar 2, 2018 4:09 PM, "Pat Ferrel" <pa...@occamsmachete.com> wrote:

> BTW the mess master is in is why git flow was invented and why I asked that
> the site be in a new repo so it could be on a separate release cycle. We
> perpetuate the mess because it’s always to hard to fix.
>
>
> From: Andrew Palumbo <ap...@outlook.com> <ap...@outlook.com>
> Reply: dev@mahout.apache.org <de...@mahout.apache.org> <
> dev@mahout.apache.org>
> Date: March 2, 2018 at 1:54:51 PM
> To: dev@mahout.apache.org <de...@mahout.apache.org> <de...@mahout.apache.org>
> Subject:  Re: Spark 2.x/scala 2.11.x release
>
> re: reverting master, shit. I forgot that the website is not on `asf-site`
> anymore. Well we could just re-jigger it, and check out `website` from
> features/multi-artifact-build-MAHOUT-20xx after we revert the rest of
> master.
>
>
> You're right, Trevor- I 'm just going through the commits, and there are
> things like
> https://github.com/apache/mahout/commit/c17bee3c2705495b638d81ae2ad374
> bf7494c3f3
>
>
>
> [https://avatars3.githubusercontent.com/u/5852441?s=200&v=4]<
> https://github.com/apache/mahout/commit/c17bee3c2705495b638d81ae2ad374
> bf7494c3f3>
>
>
> MAHOUT-1988 Make Native Solvers Scala 2.11 Complient closes apache/ma… ·
> apache/mahout@c17bee3<
> https://github.com/apache/mahout/commit/c17bee3c2705495b638d81ae2ad374
> bf7494c3f3>
>
> github.com
> …hout#326
>
>
>
> (make Native Solvers Scala 2.11 compliant) and others peppered in, Post
> 0.13.0. It still may be possible and not that hard, to cherrypick
> everything after 0.13.0 that we want. But I see what you're saying about it
> not being completely simple.
>
>
> As for Git-Flow. I dont really care. I use it in some projects and in
> others i use GitHub-flow. (basically what we've been doing with merging
> everything to master).
>
>
> Though this exact problem that we have right now is why git-flow is nice.
> Lets separate the question of how we go forward, with what commit/repo
> style, and First figure out how to back out what we have now, without
> loosing all of the work that you did on the multi artifact build.
>
>
> What do you think about reverting to 0.13.0, and cherry picking commits
> like Sparse Speedup:
> https://github.com/apache/mahout/commit/800a9ed6d7e015aa82b9eb7624bb44
> 1b71a8f397
> or checking out entire folders like `website`?
>
> [https://avatars3.githubusercontent.com/u/326731?s=200&v=4]<
> https://github.com/apache/mahout/commit/800a9ed6d7e015aa82b9eb7624bb44
> 1b71a8f397>
>
>
> MAHOUT-2019 SparkRow Matrix Speedup and fixing change to scala 2.11 m… ·
> apache/mahout@800a9ed<
> https://github.com/apache/mahout/commit/800a9ed6d7e015aa82b9eb7624bb44
> 1b71a8f397>
>
> github.com
> …ade by build script
>
>
>
> ________________________________
> From: Trevor Grant <tr...@gmail.com>
> Sent: Friday, March 2, 2018 3:58:07 PM
> To: Mahout Dev List
> Subject: Re: Spark 2.x/scala 2.11.x release
>
> If you revert master to the release tag you're going to destroy the
> website.
>
> The website pulls and rebuilds from mater whenever Jenkins detects a
> change.
>
> mahout-0.13.0 has no website. So it will pull nothing and there will be no
> site.
>
> tg
>
>
> On Fri, Mar 2, 2018 at 1:24 PM, Andrew Palumbo <ap...@outlook.com> wrote:
>
> >
> > Sounds Good. I'll put out a proposal for the release, and we can go Over
> > it and vote if we want to on releasing or on the scope. I'm +1 on it.
> >
> >
> > Broad strokes of what I'm thinking:
> >
> >
> > - Checkout a new branch "features/multi-artifact-build-22xx" from master
> > @ the `mahout-0.13.0` release tag.
> >
> >
> > - Revert master back to release tag.
> >
> >
> > - Checkout a new `develop` branch from master @the `mahout-0.13.0`
> release
> > tag.
> >
> >
> > - Cherrypick any commits that we'd like to release (E.g.: SparseSpeedup)
> > onto `develop` (along with a PR ad a ticket).
> >
> >
> > - Merge `develop` to `master`, run through Smoke tests, tag master @
> > `mahout-0.13.1`(automatically), and release.
> >
> >
> > This will also get us to more of a git-flow workflow, as we've discussed
> > moving towards.
> >
> >
> > Thoughts @all?
> >
> >
> > --andy
> >
> >
> >
> >
> >
> >
> > ________________________________
> > From: Pat Ferrel <pa...@gmail.com>
> > Sent: Wednesday, February 28, 2018 2:53:58 PM
> > To: Andrew Palumbo; dev@mahout.apache.org
> > Subject: Re: Spark 2.x/scala 2.11.x release
> >
> > big +1
> >
> > If you are planning to branch off the 0.13.0 tag let me know, I have a
> > speedup that is in my scala 2.11 fork of 0.13.0 that needs to be released
> >
> >
> > From: Andrew Palumbo <ap...@outlook.com>
> > Reply: dev@mahout.apache.org<ma...@mahout.apache.org> <
> > dev@mahout.apache.org><ma...@mahout.apache.org>
> > Date: February 28, 2018 at 11:16:12 AM
> > To: dev@mahout.apache.org<ma...@mahout.apache.org> <
> > dev@mahout.apache.org><ma...@mahout.apache.org>
> > Subject: Spark 2.x/scala 2.11.x release
> >
> > After some offline discussion regarding people's needs for Spark and 2.x
> > and Scala 2.11.x, I am wondering If we should just consider a release for
> > 2.x and 2.11.x as the default. We could release from the current master,
> or
> > branch back off of the 0.13.0 tag, and release that with the upgraded
> > defaults, and branch our current multi-artifact build off as a feature.
> Any
> > thoughts on this?
> >
> >
> > --andy
> >
>

Re: Spark 2.x/scala 2.11.x release

[Pat Ferrel <pa...@occamsmachete.com>]

BTW the mess master is in is why git flow was invented and why I asked that
the site be in a new repo so it could be on a separate release cycle. We
perpetuate the mess because it’s always to hard to fix.


From: Andrew Palumbo <ap...@outlook.com> <ap...@outlook.com>
Reply: dev@mahout.apache.org <de...@mahout.apache.org> <de...@mahout.apache.org>
Date: March 2, 2018 at 1:54:51 PM
To: dev@mahout.apache.org <de...@mahout.apache.org> <de...@mahout.apache.org>
Subject:  Re: Spark 2.x/scala 2.11.x release

re: reverting master, shit. I forgot that the website is not on `asf-site`
anymore. Well we could just re-jigger it, and check out `website` from
features/multi-artifact-build-MAHOUT-20xx after we revert the rest of
master.


You're right, Trevor- I 'm just going through the commits, and there are
things like
https://github.com/apache/mahout/commit/c17bee3c2705495b638d81ae2ad374bf7494c3f3



[https://avatars3.githubusercontent.com/u/5852441?s=200&v=4]<
https://github.com/apache/mahout/commit/c17bee3c2705495b638d81ae2ad374bf7494c3f3>


MAHOUT-1988 Make Native Solvers Scala 2.11 Complient closes apache/ma… ·
apache/mahout@c17bee3<
https://github.com/apache/mahout/commit/c17bee3c2705495b638d81ae2ad374bf7494c3f3>

github.com
…hout#326



(make Native Solvers Scala 2.11 compliant) and others peppered in, Post
0.13.0. It still may be possible and not that hard, to cherrypick
everything after 0.13.0 that we want. But I see what you're saying about it
not being completely simple.


As for Git-Flow. I dont really care. I use it in some projects and in
others i use GitHub-flow. (basically what we've been doing with merging
everything to master).


Though this exact problem that we have right now is why git-flow is nice.
Lets separate the question of how we go forward, with what commit/repo
style, and First figure out how to back out what we have now, without
loosing all of the work that you did on the multi artifact build.


What do you think about reverting to 0.13.0, and cherry picking commits
like Sparse Speedup:
https://github.com/apache/mahout/commit/800a9ed6d7e015aa82b9eb7624bb441b71a8f397
or checking out entire folders like `website`?

[https://avatars3.githubusercontent.com/u/326731?s=200&v=4]<
https://github.com/apache/mahout/commit/800a9ed6d7e015aa82b9eb7624bb441b71a8f397>


MAHOUT-2019 SparkRow Matrix Speedup and fixing change to scala 2.11 m… ·
apache/mahout@800a9ed<
https://github.com/apache/mahout/commit/800a9ed6d7e015aa82b9eb7624bb441b71a8f397>

github.com
…ade by build script



________________________________
From: Trevor Grant <tr...@gmail.com>
Sent: Friday, March 2, 2018 3:58:07 PM
To: Mahout Dev List
Subject: Re: Spark 2.x/scala 2.11.x release

If you revert master to the release tag you're going to destroy the
website.

The website pulls and rebuilds from mater whenever Jenkins detects a
change.

mahout-0.13.0 has no website. So it will pull nothing and there will be no
site.

tg


On Fri, Mar 2, 2018 at 1:24 PM, Andrew Palumbo <ap...@outlook.com> wrote:

>
> Sounds Good. I'll put out a proposal for the release, and we can go Over
> it and vote if we want to on releasing or on the scope. I'm +1 on it.
>
>
> Broad strokes of what I'm thinking:
>
>
> - Checkout a new branch "features/multi-artifact-build-22xx" from master
> @ the `mahout-0.13.0` release tag.
>
>
> - Revert master back to release tag.
>
>
> - Checkout a new `develop` branch from master @the `mahout-0.13.0`
release
> tag.
>
>
> - Cherrypick any commits that we'd like to release (E.g.: SparseSpeedup)
> onto `develop` (along with a PR ad a ticket).
>
>
> - Merge `develop` to `master`, run through Smoke tests, tag master @
> `mahout-0.13.1`(automatically), and release.
>
>
> This will also get us to more of a git-flow workflow, as we've discussed
> moving towards.
>
>
> Thoughts @all?
>
>
> --andy
>
>
>
>
>
>
> ________________________________
> From: Pat Ferrel <pa...@gmail.com>
> Sent: Wednesday, February 28, 2018 2:53:58 PM
> To: Andrew Palumbo; dev@mahout.apache.org
> Subject: Re: Spark 2.x/scala 2.11.x release
>
> big +1
>
> If you are planning to branch off the 0.13.0 tag let me know, I have a
> speedup that is in my scala 2.11 fork of 0.13.0 that needs to be released
>
>
> From: Andrew Palumbo <ap...@outlook.com>
> Reply: dev@mahout.apache.org<ma...@mahout.apache.org> <
> dev@mahout.apache.org><ma...@mahout.apache.org>
> Date: February 28, 2018 at 11:16:12 AM
> To: dev@mahout.apache.org<ma...@mahout.apache.org> <
> dev@mahout.apache.org><ma...@mahout.apache.org>
> Subject: Spark 2.x/scala 2.11.x release
>
> After some offline discussion regarding people's needs for Spark and 2.x
> and Scala 2.11.x, I am wondering If we should just consider a release for
> 2.x and 2.11.x as the default. We could release from the current master,
or
> branch back off of the 0.13.0 tag, and release that with the upgraded
> defaults, and branch our current multi-artifact build off as a feature.
Any
> thoughts on this?
>
>
> --andy
>

Re: Spark 2.x/scala 2.11.x release

[Andrew Palumbo <ap...@outlook.com>]

re: reverting master,  shit.   I forgot that the website is not on `asf-site` anymore.  Well we could just re-jigger it, and check out `website` from  features/multi-artifact-build-MAHOUT-20xx after we revert the rest of master.


You're right, Trevor- I 'm just going through the commits, and there are things like https://github.com/apache/mahout/commit/c17bee3c2705495b638d81ae2ad374bf7494c3f3



[https://avatars3.githubusercontent.com/u/5852441?s=200&v=4]<https://github.com/apache/mahout/commit/c17bee3c2705495b638d81ae2ad374bf7494c3f3>

MAHOUT-1988 Make Native Solvers Scala 2.11 Complient closes apache/ma… · apache/mahout@c17bee3<https://github.com/apache/mahout/commit/c17bee3c2705495b638d81ae2ad374bf7494c3f3>
github.com
…hout#326



 (make Native Solvers Scala 2.11 compliant) and others peppered in, Post 0.13.0.  It still may be possible and not that hard, to cherrypick everything after 0.13.0 that we want.  But I see what you're saying about it not being completely simple.


As for Git-Flow.  I dont really care.   I use it in some projects and in others i use GitHub-flow. (basically what we've been doing with merging everything to master).


Though this exact problem that we have right now is why git-flow is nice.  Lets separate the question of how we go forward, with what commit/repo style, and First figure out how to back out what we have now, without loosing all of the work that you did on the multi artifact build.


What do you think about reverting to 0.13.0, and cherry picking commits like Sparse Speedup: https://github.com/apache/mahout/commit/800a9ed6d7e015aa82b9eb7624bb441b71a8f397 or checking out entire folders like `website`?

[https://avatars3.githubusercontent.com/u/326731?s=200&v=4]<https://github.com/apache/mahout/commit/800a9ed6d7e015aa82b9eb7624bb441b71a8f397>

MAHOUT-2019 SparkRow Matrix Speedup and fixing change to scala 2.11 m… · apache/mahout@800a9ed<https://github.com/apache/mahout/commit/800a9ed6d7e015aa82b9eb7624bb441b71a8f397>
github.com
…ade by build script



________________________________
From: Trevor Grant <tr...@gmail.com>
Sent: Friday, March 2, 2018 3:58:07 PM
To: Mahout Dev List
Subject: Re: Spark 2.x/scala 2.11.x release

If you revert master to the release tag you're going to destroy the
website.

The website pulls and rebuilds from mater whenever Jenkins detects a
change.

mahout-0.13.0 has no website. So it will pull nothing and there will be no
site.

tg


On Fri, Mar 2, 2018 at 1:24 PM, Andrew Palumbo <ap...@outlook.com> wrote:

>
> Sounds Good.  I'll put out a proposal for the release, and we can go Over
> it and vote if we want to on releasing or on the scope.  I'm +1 on it.
>
>
> Broad strokes of what I'm thinking:
>
>
> - Checkout a new branch "features/multi-artifact-build-22xx" from master
> @ the `mahout-0.13.0` release tag.
>
>
> - Revert master back to release tag.
>
>
> - Checkout a new `develop` branch from master @the `mahout-0.13.0` release
> tag.
>
>
> - Cherrypick any commits that we'd like to release (E.g.: SparseSpeedup)
> onto `develop` (along with a PR ad a ticket).
>
>
> - Merge `develop` to `master`, run through Smoke tests, tag master @
> `mahout-0.13.1`(automatically), and release.
>
>
> This will also get us to more of a git-flow workflow, as we've discussed
> moving towards.
>
>
> Thoughts @all?
>
>
> --andy
>
>
>
>
>
>
> ________________________________
> From: Pat Ferrel <pa...@gmail.com>
> Sent: Wednesday, February 28, 2018 2:53:58 PM
> To: Andrew Palumbo; dev@mahout.apache.org
> Subject: Re: Spark 2.x/scala 2.11.x release
>
> big +1
>
> If you are planning to branch off the 0.13.0 tag let me know, I have a
> speedup that is in my scala 2.11 fork of 0.13.0 that needs to be released
>
>
> From: Andrew Palumbo <ap...@outlook.com>
> Reply: dev@mahout.apache.org<ma...@mahout.apache.org> <
> dev@mahout.apache.org><ma...@mahout.apache.org>
> Date: February 28, 2018 at 11:16:12 AM
> To: dev@mahout.apache.org<ma...@mahout.apache.org> <
> dev@mahout.apache.org><ma...@mahout.apache.org>
> Subject:  Spark 2.x/scala 2.11.x release
>
> After some offline discussion regarding people's needs for Spark and 2.x
> and Scala 2.11.x, I am wondering If we should just consider a release for
> 2.x and 2.11.x as the default. We could release from the current master, or
> branch back off of the 0.13.0 tag, and release that with the upgraded
> defaults, and branch our current multi-artifact build off as a feature. Any
> thoughts on this?
>
>
> --andy
>

Re: Spark 2.x/scala 2.11.x release

[Trevor Grant <tr...@gmail.com>]

If you revert master to the release tag you're going to destroy the
website.

The website pulls and rebuilds from mater whenever Jenkins detects a
change.

mahout-0.13.0 has no website. So it will pull nothing and there will be no
site.

tg


On Fri, Mar 2, 2018 at 1:24 PM, Andrew Palumbo <ap...@outlook.com> wrote:

>
> Sounds Good.  I'll put out a proposal for the release, and we can go Over
> it and vote if we want to on releasing or on the scope.  I'm +1 on it.
>
>
> Broad strokes of what I'm thinking:
>
>
> - Checkout a new branch "features/multi-artifact-build-22xx" from master
> @ the `mahout-0.13.0` release tag.
>
>
> - Revert master back to release tag.
>
>
> - Checkout a new `develop` branch from master @the `mahout-0.13.0` release
> tag.
>
>
> - Cherrypick any commits that we'd like to release (E.g.: SparseSpeedup)
> onto `develop` (along with a PR ad a ticket).
>
>
> - Merge `develop` to `master`, run through Smoke tests, tag master @
> `mahout-0.13.1`(automatically), and release.
>
>
> This will also get us to more of a git-flow workflow, as we've discussed
> moving towards.
>
>
> Thoughts @all?
>
>
> --andy
>
>
>
>
>
>
> ________________________________
> From: Pat Ferrel <pa...@gmail.com>
> Sent: Wednesday, February 28, 2018 2:53:58 PM
> To: Andrew Palumbo; dev@mahout.apache.org
> Subject: Re: Spark 2.x/scala 2.11.x release
>
> big +1
>
> If you are planning to branch off the 0.13.0 tag let me know, I have a
> speedup that is in my scala 2.11 fork of 0.13.0 that needs to be released
>
>
> From: Andrew Palumbo <ap...@outlook.com>
> Reply: dev@mahout.apache.org<ma...@mahout.apache.org> <
> dev@mahout.apache.org><ma...@mahout.apache.org>
> Date: February 28, 2018 at 11:16:12 AM
> To: dev@mahout.apache.org<ma...@mahout.apache.org> <
> dev@mahout.apache.org><ma...@mahout.apache.org>
> Subject:  Spark 2.x/scala 2.11.x release
>
> After some offline discussion regarding people's needs for Spark and 2.x
> and Scala 2.11.x, I am wondering If we should just consider a release for
> 2.x and 2.11.x as the default. We could release from the current master, or
> branch back off of the 0.13.0 tag, and release that with the upgraded
> defaults, and branch our current multi-artifact build off as a feature. Any
> thoughts on this?
>
>
> --andy
>