For now u can key off from the Snapshot release for ur POC until the next release happens (most likely October time frame).
But I must warn you that the code u r working with has long been designated as 'Do Not Maintain' and may well be purged in a future release. Just a word of caution here. It may be OK for a POC, but I would definitely not plan on putting that in production. All of that stuff is legacy code and we have purged a good chunk of that cake in the past 2 yrs and may not keep the remainder around for too long. regards On Thu, Aug 18, 2016 at 1:41 PM, Raviteja Lokineni < [email protected]> wrote: > I can use a branch though for the time being. > > I was actually trying to do a POC with text analytics and I found mahout + > lucene as a viable approach. > > So, from my organizational point of view. If I successfully do this POC > then I should also be convincing them of the versions of software in use. I > will not be able to convince them to use a snapshot release in production. > > On Thu, Aug 18, 2016 at 1:22 PM, Dmitriy Lyubimov <[email protected]> > wrote: > > > as a rule of thumb, we usually don't update dependencies in maintenance > > releases. I would say it should go with 0.13. > > Do you have sense of urgency to have release? can you use PR branch > > meanwhile? > > > > On Thu, Aug 18, 2016 at 10:19 AM, Raviteja Lokineni < > > [email protected]> wrote: > > > > > Can we call a vote for a maintenance release with the lucene > > compatibility > > > upgraded to 5.x from 4.x. > > > > > > I am assuming it should deserve it's own release. What do the other > devs > > > think about a maintenance release. > > > > > > On Thu, Aug 18, 2016 at 1:07 PM, Dmitriy Lyubimov <[email protected]> > > > wrote: > > > > > > > There's no consensus. There are a couple features coming that would > > > inspire > > > > 0.13 but it's hard to tell when they are going to be completed due to > > > > uncertainties in contributor's schedule. > > > > > > > > current estimate september-october for the 0.13. > > > > > > > > Maintenance releases could be cut pretty much at will (assuming there > > are > > > > compelling bugs found). > > > > > > > > On Wed, Aug 17, 2016 at 12:05 PM, Raviteja Lokineni < > > > > [email protected]> wrote: > > > > > > > > > Hi all, > > > > > > > > > > Just wanted to check if there is any ETA planned out for the next > > > Mahout > > > > > release. Either 0.12.3 or 0.13. > > > > > > > > > > Thanks, > > > > > -- > > > > > *Raviteja Lokineni* | Business Intelligence Developer > > > > > TD Ameritrade > > > > > > > > > > E: [email protected] > > > > > > > > > > [image: View Raviteja Lokineni's profile on LinkedIn] > > > > > <http://in.linkedin.com/in/ravitejalokineni> > > > > > > > > > > > > > > > > > > > > > -- > > > *Raviteja Lokineni* | Business Intelligence Developer > > > TD Ameritrade > > > > > > E: [email protected] > > > > > > [image: View Raviteja Lokineni's profile on LinkedIn] > > > <http://in.linkedin.com/in/ravitejalokineni> > > > > > > > > > -- > *Raviteja Lokineni* | Business Intelligence Developer > TD Ameritrade > > E: [email protected] > > [image: View Raviteja Lokineni's profile on LinkedIn] > <http://in.linkedin.com/in/ravitejalokineni> >
