Fair enough... I had no intention of getting into release planning. Please
disregard what I'd said about releases.

These were Just proposals and a vague direction that I'd had ideas for.
Also these are all things that we've talked about. I was looking at when I
could get possibly get to work on them.

Most important is the PR

On Sun, 10 Nov 2019 01:18:52 -0600, dev wrote:

Like, Im not doing enough atm to fight the do-acracy, but calling 3
releases out seems ambitious.

I think everything you're saying is cool for roadmap, but trying to pin to
specific releases atm is at best premature.

Again, nothing but respect for the awesome job you've done @apalumbo.

Just my .02, and don't mean to pee in the Cheerios,

Tg




On Sat, Nov 9, 2019, 10:42 PM GitBox <g...@apache.org wrote:

andrewpalumbo commented on issue #382: [MAHOUT-2071] Fix binary and source
releases URL:
https://github.com/apache/mahout/pull/382#issuecomment-552162406

As well if you guys are busy, i can assume lazy consensus after 72hr on a
large PR if you like.
1.

IMHO thw main goal for 14.1-release is to get binaries deployed as is. `
2.

14.2-release` maybe get zeppelin notebooks up and some provisioning
software/AMI/DockerImages up online as discussed. (ivve started
adrewpalumbo/mahout in Dockerhub btw.
3.

14.3-release, some demos and some GPU, multi-gpu for Viennacl openCL and
Finishout some simple tiling strategy for multiGPU on JCuda branch if this
is still the best Java/Cuda Blas overlap that we work on. Thats just of.
the top of my head a path I'm just throwing it out there... All that to
say. that if you guhys want to give me your proxyies for PRs, I'll het us
ip to a voteable RC for this release. (14.1-release).. LMK---I dont mind
either way. Just have a little more energy and time that i thought id have
this week.



This is an automated message from the Apache Git Service. To respond to the
message, please log on to GitHub and use the URL above to go to the
specific comment.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

With regards, Apache Git Services

Reply via email to