Re: Communicating the future of DIH?

tories or to do a similar process with our own multiple > repositories. > > On Tue, Nov 3, 2020 at 2:43 PM Gézapeti wrote: > >> I'm not that close with Apache Commons either, but I think the >> solr-operator is a perfect candidate to figure out how things should wo

Re: Communicating the future of DIH?

/www.linkedin.com/in/davidwsmiley > > > On Wed, Oct 28, 2020 at 2:12 PM Gézapeti Cseh wrote: > >> Hey everyone, >> >> Solr could keep some plugins with separate git repositories under the >> Apache umbrella if it adapts the Apache Commons model >> <h

Re: Communicating the future of DIH?

Hey everyone, Solr could keep some plugins with separate git repositories under the Apache umbrella if it adapts the Apache Commons model where plugins can have their own release schedule and community without the risk of being abandoned completely without notice.

Re: [DISCUSS] Lucene-Solr split (Solr promoted to TLP)

I think separating the git repository and even the release schedules could be done under the same TLP. It would solve most of the technical issues reflected in the first mail and there would be more time and data to see if creating Apache Solr again is something the PMC would want to do gp On

Re: [VOTE] Release Lucene/Solr 8.4.1 RC1

I wanted to do this for a while now. Having this smoke tester script is neat! :) SUCCESS! [1:35:44.613132] +1 (non-binding) On Fri, Jan 10, 2020 at 10:12 AM Ishan Chattopadhyaya < ichattopadhy...@gmail.com> wrote: > Please vote for release candidate 1 for Lucene/Solr 8.4.1 > > The artifacts

Re: Rethinking how we publish the Solr Ref Guide

Thanks for the help! The link was an internal documentation I assumed it was correct. I've updated it in our wiki page. On Mon, Oct 28, 2019 at 7:57 PM Cassandra Targett wrote: > Yes, it does need to be updated. I was waiting to do that until I informed > the user list about the change to not

Re: Rethinking how we publish the Solr Ref Guide

Hi everyone, I was trying to access https://lucene.apache.org/solr/guide/latest/field-types-included-with-solr.html and it got redirected to https://lucene.apache.org/solr/guide/8_1/latest/field-types-included-with-solr.html which is a 404. I've tested https://lucene.apache.org/solr/guide/latest/

Re: The Lucene Solr Gradle Build Game plan

Hi Cassandra and Dawid, I don't really understand how the ref guide build works, but I managed to make the solr-ref-guide project compile on calling gradle build I've pushed my small changes to https://github.com/gezapeti/lucene-solr/tree/jira/SOLR-13452_gradle_7_refguide Dawid, you can find

Re: Call for help: moving from ant build to gradle

I'd be happy to help with the gradle migration. I could not find a jira that covers it, only LUCENE-5755, which was closed a long time ago. Where can I join the discussion about this? Thanks for the pointers, gp On Thu, Feb 7, 2019 at 8:23 PM Vladimir Kroz wrote: > +1 for moving to gradle.