Re: Solr: Separate CHANGES.txt for Docker, SolrJ, Contribs, ...

2020-11-23 Thread Alexandre Rafalovitch
Should we switch to a structured format, instead of current format that tools struggle to convert. Something that one could push into Solr would have been nice... Regards, Alex On Mon., Nov. 23, 2020, 4:47 p.m. David Smiley, wrote: > I pushed a commit to a PR for the prometheus exporter

Re: Solr: Separate CHANGES.txt for Docker, SolrJ, Contribs, ...

2020-11-23 Thread David Smiley
I pushed a commit to a PR for the prometheus exporter that includes a CHANGES.md https://github.com/apache/lucene-solr/pull/1972/commits/bec84ce2a1d60480ce0c54b78e83a70f83e7b058 and likewise for a commit to a PR for the docker module:

Re: Solr: Separate CHANGES.txt for Docker, SolrJ, Contribs, ...

2020-11-23 Thread Houston Putman
+1 I think that having separate CHANGES.txt files for the different parts of Solr would be great. If you are looking for certain changes you would generally know which module to go to. Some items that have a more sweeping impact would be listed in both I am ambivalent on having a separate

Re: Propose changing the "dist" layout

2020-11-23 Thread David Smiley
I'll proceed on this with lazy consensus. I suspect most of us don't care, unsurprisingly since I doubt anyone has any fondness for the "dist" folder. ~ David Smiley Apache Lucene/Solr Search Developer http://www.linkedin.com/in/davidwsmiley On Sun, Nov 15, 2020 at 7:31 AM Erick Erickson

BadApple report

2020-11-23 Thread Erick Erickson
Unfortunately, the reference impl is creating quite a bit of noise in Hoss’ rollups. That said, I have a mail filter for test failures that puts the reference impl tests in a different mail folder and my sense is that the regular branch is getting an increasing number of failures. If I have