very well, please get started by generating ur gpg keys and posting them to id.apache.org.
Setup ur RSA keys and add that to your apache profile on id.apache.org On Mon, Apr 18, 2016 at 9:17 PM, Andrew Palumbo <ap....@outlook.com> wrote: > I can be the Release Manager for this.. > > ________________________________________ > From: Suneel Marthi <smar...@apache.org> > Sent: Monday, April 18, 2016 9:15 PM > To: mahout > Subject: Re: [Discussion] Scope of the mahout 0.12.1 release. > > ...and work for 0.12.1 would be on master branch > > On Mon, Apr 18, 2016 at 9:14 PM, Suneel Marthi <suneel.mar...@gmail.com> > wrote: > > > For 0.12.1, the 2 issues below along with a Jira to polish the scaladocs > > for Flink backend that pretty much don't exist now. > > > > Also the Scaladocs for 0.12.1 to be published with the release, that > > should suffice as scope for 0.12.1. > > > > I agree Flink shell should be differed to 0.13.0 as its not stable yet, > > but we can start working on that in a separate branch. > > > > If someone from the PMC could volunteer to be the Release Manager for > > 0.12.1 that would be great. > > > > > > On Mon, Apr 18, 2016 at 8:57 PM, Andrew Palumbo <ap....@outlook.com> > > wrote: > > > >> Flink will soon be releasing 1.0.2, which includes a kryo fix that > should > >> help us with the following issues: > >> > >> > >> FlinkOpABt: > >> > >> https://issues.apache.org/jira/browse/MAHOUT-1750 > >> > >> > >> <https://issues.apache.org/jira/browse/MAHOUT-1750> > >> > >> Flink Dals error: > >> <https://issues.apache.org/jira/browse/MAHOUT-1818> > >> > >> https://issues.apache.org/jira/browse/MAHOUT-1818 > >> > >> > >> > >> As well we may be able to work the Flink Shell in along with these: > >> > >> > >> https://issues.apache.org/jira/browse/MAHOUT-1831 > >> > >> > >> Though that might be better to save for Mahout 0.13 as it is both a new > >> feature and I've noticed that Flink has some issues with this that may > not > >> be addressed until a later release. > >> > >> > >> Is there anything on the Spark side of things that needs to be > >> addressed? Or anything else in general? > >> > > > > >
