Re: Change solr/lucene Readme file format

2020-01-22 Thread Houston Putman
Markdown is very standard at this point and I think the barrier to entry is very small, at least much smaller than asciidoc, which is used for the ref guide. +1 on this for me. On Wed, Jan 22, 2020 at 9:43 AM Doug Turnbull < dturnb...@opensourceconnections.com> wrote: > I think this got lost in

Re: Change solr/lucene Readme file format

2020-01-22 Thread Doug Turnbull
I think this got lost in the holidays. I wanted to bump this contribution, as I feel markdown is pretty standard format for readmes that devs are expecting these days. (And the files were close to markdown anyway.) Or if the project doesn't want this contribution, I feel we should at least let Pin

Re: [lucene-solr] branch master updated: Synchronizing 8.4.1 changes

2020-01-22 Thread Jan Høydahl
I just realized that since the 8.4.1 section wlll actually be part of the 8.5.0 CHANGES file, there should be no doubt wrt this. Thanks > 22. jan. 2020 kl. 10:15 skrev Adrien Grand : > > Given that 8.5.0 is not released yet, moving these entries from 8.5 to 8.4.1 > feels consistent with instru

Re: [lucene-solr] branch master updated: Synchronizing 8.4.1 changes

2020-01-22 Thread Adrien Grand
Given that 8.5.0 is not released yet, moving these entries from 8.5 to 8.4.1 feels consistent with instructions we have on the wiki: https://cwiki.apache.org/confluence/display/lucene/ReleaseTodo#ReleaseTodo-SynchronizeCHANGES.txt. Indeed we would have duplicated entries if we were releasing 8.4.2

Re: [lucene-solr] branch master updated: Synchronizing 8.4.1 changes

2020-01-22 Thread Jan Høydahl
Just a question about this commit. These bug fixes released in 8.4.1 are also part of 8.5.0. I thought we normally duplicated changes entries between a bugfix release and the next minor version to avoid having to look at release dates and guess whether the fixes are in the next minor or not. O