no rush here.. Andrew is busy till weekend, it looks like and Joe confirmed. the minimum.. I have the RC process for this release down to about 45 mins so can easily cut a new one any time anyways. ________________________________ From: Trevor Grant <trevor.d.gr...@gmail.com> Sent: Tuesday, January 21, 2020 5:54 AM To: Mahout Dev List <dev@mahout.apache.org> Subject: Re: [VOTE] MAHOUT-14.1 RC3 - call for [Volunteers] and vote
I think 72 hours is the _minimum_. I came back late last night so I could have today for laundry, cleaning, and other catch-up-on-life stuff, which would include testing the RC. Tg On Jan 21, 2020 12:17 AM, "Andrew Musselman" <andrew.mussel...@gmail.com> wrote: I think 72 hours is a guideline but can check; my apologies but I also got too busy with work and family to take a good look. If we have the right URL for artifacts we can shoot for a vote this weekend. Thanks for running the release Andy! On Mon, Jan 20, 2020 at 21:35 Andrew Palumbo <ap....@outlook.com> wrote: > As a reminder to all. I cut this RC at a bad point for most to test. > (Rawkintrevo had a vacation and others mentioned offline being very busy. > We discussed offline leaving the vote open for more than 72 hours. but I am > happy to close it and re open when it is not Announced bad timing. or in > voilation of Apache release rules (might be)... Please let me know. > > Maybe we can co-ordinate at next weekly meeting when Trevor's back? It > seemed like a good amount were ready to participate in weelky meetings last > week. > > (I also supplied incorrect artifact name in release.. My first time acting > as release manager.) > > Happy to coordinate a better time for testing and cut a new RC if need be. > > Whatever's good. > > --Andy > ------------------------------ > *From:* Andrew Palumbo <ap....@outlook.com> > *Sent:* Saturday, January 18, 2020 7:19 PM > > *To:* Andrew Musselman <andrew.mussel...@gmail.com>; dev@mahout.apache.org > <dev@mahout.apache.org> > *Subject:* Re: [VOTE] MAHOUT-14.1 RC3 - call for [Volunteers] and vote > > Resolved artifacts for a test application. Built and tested. There is a > duplicate source release however, I believe that this is trivial and can be > dealt with in a readme or not at all (it is a default artifact from the > maven release plugin). > > +1 (binding) > > On Jan 16, 2020 10:50 PM, Andrew Palumbo <ap....@outlook.com> wrote: > > I looked back over the release docs, and the link I was supposed to send > out out was this: > https://repository.apache.org/content/repositories/orgapachemahout-1060/ > < https://slack-redir.net/link?url=https%3A%2F%2Frepository.apache.org%2Fcontent%2Frepositories%2Forgapachemahout-1060%2F&v=3 > > > I was able to successfully resolve all artifacts with this link in a > spark application. > > please use this URL for to test the staged artifacts. > > Thank you, > > --andy > ------------------------------ > *From:* Andrew Palumbo <ap....@outlook.com> > *Sent:* Wednesday, January 15, 2020 5:01 PM > *To:* Andrew Musselman <andrew.mussel...@gmail.com>; dev@mahout.apache.org > <dev@mahout.apache.org> > *Subject:* Re: [VOTE] MAHOUT-14.1 RC3 - call for [Volunteers] and vote > > Apologies, I'd not closed the staging repository, and sent out the wrong > link In the initial email. the correct staging link is here: > > > https://repository.apache.org/content/repositories/orgapachemahout-1060/org/apache/mahout/ < https://slack-redir.net/link?url=https%3A%2F%2Frepository.apache.org%2Fcontent%2Frepositories%2Forgapachemahout-1060%2Forg%2Fapache%2Fmahout%2F&v=3 > < https://repository.apache.org/content/repositories/orgapachemahout-1060/org/apache/mahout/%3Chttps://slack-redir.net/link?url=https%3A%2F%2Frepository.apache.org%2Fcontent%2Frepositories%2Forgapachemahout-1060%2Forg%2Fapache%2Fmahout%2F&v=3 > > > > > --andy > ________________________________ > From: Andrew Palumbo <ap....@outlook.com> > Sent: Tuesday, January 14, 2020 4:18 PM > To: Andrew Musselman <andrew.mussel...@gmail.com>; dev@mahout.apache.org < > dev@mahout.apache.org> > Subject: Re: [VOTE] MAHOUT-14.1 RC3 - call for [Volunteers] and vote > > This is a call for volunteers as well. Anyone may test the Release > candidate; the more eyes the better. > > Changed subject Line. > > --Andy > > ________________________________ > From: Andrew Musselman <andrew.mussel...@gmail.com> > Sent: Tuesday, January 14, 2020 1:43 PM > To: dev@mahout.apache.org <dev@mahout.apache.org> > Subject: Re: [VOTE] MAHOUT-14.1 RC3 - call for testing and vote > > I will have time Thursday afternoon; thanks Andy > > On Tue, Jan 14, 2020 at 05:52 Trevor Grant <trevor.d.gr...@gmail.com> > wrote: > > > I can test tomorrow. > > > > On Tue, Jan 14, 2020 at 1:41 AM Andrew Palumbo <andrew_palu...@msn.com> > > wrote: > > > > > Hey all, > > > I've uploaded RC3 to nexus for scala 2.11 and scala 2.12. I already > have > > > seen a small issue while building the RC. All artifacts are available > in > > > staging: > > > > > > > > > > > > https://repository.apache.org/service/local/repositories/orgapachemahout-1060/content/org/apache/mahout/ > > > > > > We should test this release well, as it is a heavy refactor, We still > > have > > > not tested /bin/mahout. > > > > > > So we need three binding +1s for this release. > > > > > > For testing, lease do the following: > > > 1. Download build and test the src archive. > > > 2. Run a job CCO e.g which uses the CLI. > > > 3. run on a cluster/pseudo or otherwise. > > > 4. Verify Sigs and hashes. > > > > > > I noticed that many people are busy this week. I am wondering if we > > > can/should leave the Vote open longer than 72hrs. > > > > > > Or if we can work out all trivial issues, like naming and this extra > > > source distribution, and I'll build RC4. > > > > > > > > > Thank you, > > > > > > Andy > > > > > > > > > > >
