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


Trevor said -1 to git flow.

I agree this is a good example of one nice feature. Master is always
pristine.
From: Andrew Palumbo <[EMAIL PROTECTED]> <[EMAIL PROTECTED]>
Reply: [EMAIL PROTECTED] <[EMAIL PROTECTED]> <[EMAIL PROTECTED]>
Date: March 2, 2018 at 12:30:09 PM
To: [EMAIL PROTECTED] <[EMAIL PROTECTED]> <[EMAIL PROTECTED]>
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 <[EMAIL PROTECTED]>
Sent: Friday, March 2, 2018 3:00:15 PM
To: Trevor Grant; [EMAIL PROTECTED]
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 <[EMAIL PROTECTED]> <[EMAIL PROTECTED]>
Reply: [EMAIL PROTECTED] <[EMAIL PROTECTED]> <[EMAIL PROTECTED]>

Date: March 2, 2018 at 11:36:52 AM
To: Mahout Dev List <[EMAIL PROTECTED]> <[EMAIL PROTECTED]>
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 <[EMAIL PROTECTED]> wrote:
release
or
Any