Rolled back trunk to 0.9-SNAPSHOT, please go ahead and commit any changes.
On Saturday, January 25, 2014 4:19 AM, Suneel Marthi <suneel_mar...@yahoo.com> wrote: I'll be rolling back the 0.9 Release today that's presently in staging in light of the issues that have been reported in the last 2 days and need to be fixed as part of the Release. Please hold off from committing any new code to trunk meanwhile. Thanks. On Friday, January 24, 2014 7:36 PM, Ted Dunning <ted.dunn...@gmail.com> wrote: My schedule has opened up a bit and I can review as well. On Fri, Jan 24, 2014 at 3:06 PM, Sebastian Schelter <ssc.o...@googlemail.com> wrote: I will try the next candidate agaim, so one vote is sure. >Am 24.01.2014 23:54 schrieb "Suneel Marthi" <suneel_mar...@yahoo.com>: > > >> I am open to having the conversation (and a part of me feels that the >> clusteringId fix should be in 0.9). >> >> If we decide to incorporate that into 0.9, I need to rollback the 0.9 >> Release that's presently out there in staging (for the 5th time in a row >> now). >> I am fine with doing that. >> >> What do you think we should do? >> >> a) Go ahead with 0.9 release without the fix for M-1410 . >> b) Rollback 0.9 and include the fix for M-1410 >> c) Go ahead with 0.9, have an interim 1.0 Release Candidate that includes >> M-1410 and any other issues/enhancements that are fixed. >> >> >> I am leaning towards (b), my only concern being that from my experience in >> the past few weeks; its become real hard to muster the minimum 3 +1 PMC >> votes required for a release to pass. >> >> >> >> >> >> >> >> >> On Friday, January 24, 2014 5:45 PM, Ted Dunning <ted.dunn...@gmail.com> >> wrote: >> >> >> >> Can we hold a separate discussion about whether the clustering id issue >> has to be in 0.9 while extending the vote deadline if necessary? >> >> If not, then all these votes are great and the release can go forward. >> >> If it is the sense that that fix has to be in, we should leave time for >> people for people to reverse their votes to -1. >> >> >> >> >> On Fri, Jan 24, 2014 at 2:22 PM, Suneel Marthi <suneel_mar...@yahoo.com> >> wrote: >> >> Thanks for all those that volunteered. The voting for 0.9 Release closes >> tomorrow. >> > >> > >> > >> > >> > >> > >> > >> > >> >On Friday, January 24, 2014 4:05 AM, Gokhan Capan <gkhn...@gmail.com> >> wrote: >> > >> >Using CentOS 6.5 and hadoop 1.2.1, all passed. >> > >> >+1 from me >> > >> >Gokhan >> > >> > >> > >> >On Thu, Jan 23, 2014 at 6:01 PM, Andrew Palumbo <ap....@outlook.com> >> wrote: >> > >> >> a),b),c),d) all passed on CentOS for me >> >> >> >> > Date: Thu, 23 Jan 2014 13:43:06 +0200 >> >> > Subject: Re: MAHOUT 0.9 Release - New URL >> >> > From: ssvinarc...@hortonworks.com >> >> > To: dev@mahout.apache.org >> >> > >> >> > I did a), b), c), d) and all steps pass. >> >> > +1 >> >> > >> >> > >> >> > On Thu, Jan 23, 2014 at 1:40 PM, Grant Ingersoll <gsing...@apache.org >> >> >wrote: >> >> > >> >> > > +1 from me. >> >> > > >> >> > > On Jan 22, 2014, at 5:55 PM, Suneel Marthi <suneel_mar...@yahoo.com >> > >> >> > > wrote: >> >> > > >> >> > > > Fixed the issues that were reported this week and restored FP >> mining >> >> > > into the codebase. >> >> > > > >> >> > > > Here's the URL for the final release in staging:- >> >> > > > >> >> > > >> >> >> https://repository.apache.org/content/repositories/orgapachemahout-1003/org/apache/mahout/mahout-distribution/0.9/ >> >> > > > >> >> > > > The artifacts have been signed with the >> > following key: >> >> > > > https://people.apache.org/keys/committer/smarthi.asc >> >> > > > >> >> > > > >> >> > > > a) Verify that u can unpack the release (tar or zip) >> >> > > > b) Verify u r able to compile the distro >> >> > > > c) Run through the unit tests: mvn clean test >> >> > > > d) Run the example scripts under >> > $MAHOUT_HOME/examples/bin. Please >> >> run >> >> > > through all the different options in each script. >> >> > > > >> >> > > > Committers and PMC, need a minimum of 3 '+1' votes for the release >> >> to be >> >> > > finalized. >> >> > > >> >> > > -------------------------------------------- >> >> > > Grant Ingersoll | @gsingers >> >> > > http://www.lucidworks.com >> >> > > >> >> > > >> >> > > >> >> > > >> >> > > >> >> > > >> >> > >> >> > -- >> >> >> > > CONFIDENTIALITY NOTICE >> >> > NOTICE: This message is intended for the use of the individual or >> entity >> >> to >> >> > which it is addressed and may contain information that is >> confidential, >> >> > privileged and exempt from disclosure under applicable law. If the >> reader >> >> > of this message is not the intended recipient, you are hereby notified >> >> that >> >> > any printing, copying, dissemination, distribution, disclosure or >> >> > forwarding of this communication is strictly prohibited. If you have >> >> > received this communication in error, please contact the sender >> >> immediately >> >> > and delete it from your system. Thank You. >> >> >> >> >
