For some days now, the prometheus exporter & Docker modules have their own
CHANGES.md on master. I was about to add a CHANGES.md for the rest of the
contribs last week... but... instead ***I'm going to reverse this***; merge
the entries into solr/CHANGES.txt. I still think it's better than a
Absolutely.
What I was trying to say is that when it comes to implementation,
there may be a choice of strategies to do so within the same scope. A
strategy that aligns better with something that - with more work -
eventually becomes true structured data may have more long-term value
than a
I'd rather not scope-creep my proposal here further. Granted I ventured
into TXT -> Markdown.
~ David Smiley
Apache Lucene/Solr Search Developer
http://www.linkedin.com/in/davidwsmiley
On Tue, Nov 24, 2020 at 9:37 AM Alexandre Rafalovitch
wrote:
> And - afterthought - if there is an easily
And - afterthought - if there is an easily parsable format, the parser
could even run at the commit time on GitHub to make sure that issue
numbers are correct, names are included and formatting is not broken.
Regards,
Alex.
On Mon, 23 Nov 2020 at 19:38, Alexandre Rafalovitch wrote:
>
>
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
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:
+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
What of Docker changes? And beyond direct changes to Dockerfile + scripts,
it could feature particular notable changes to the server that are
particularly noteworthy... like hypothetical improvements to solr home /
core root dir etc. configuration.
Even if Contribs/Modules are not separated out
I think whatever we don't ship in the main tarball today should stay
separate. Going forward, when we stop shoving the extra modules (contribs)
into the main distro, we can separate out their changelogs. However, I feel
SolrJ changes should stay with Solr changes since it is also used heavily
in
I was about to merge a PR pertaining to Solr's new Docker module when it
occurred to me that I ought to add a CHANGES.txt entry. But, for Solr
users (which includes me and everyone reading this), it's annoying to have
to go to Solr's all-encompassing CHANGES.txt to find Docker upgrade
notes,
10 matches
Mail list logo
