lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Uwe Schindler (JIRA)" <>
Subject [jira] [Commented] (LUCENE-5822) Create a markdown formatted README file for Lucene/Solr
Date Sun, 02 Jul 2017 10:20:01 GMT


Uwe Schindler commented on LUCENE-5822:

there was another problem on Jenkins: Because the ASF Jenkins version was quite old (LTS release)
in the past, we added the README.txt as a dummy artifact to be archived. Why?

We generally archive all test and heapdump files for test-only builds because they help with
debgging test failures. If the build was successful, of course nothing was there to be archived.
Older Jenkins versions did not have the option to *not* fail the build if there were no artifacts,
so the README.txt was always archived as a dummy (small file less hassle) :-)

As ASF Jenkins updated recently to newer version, I was able to remove the README.txt file
and check the new option to *not* fail the build if no artifacts are there.

> Create a markdown formatted README file for Lucene/Solr
> -------------------------------------------------------
>                 Key: LUCENE-5822
>                 URL:
>             Project: Lucene - Core
>          Issue Type: Wish
>            Reporter: Shalin Shekhar Mangar
>            Assignee: Mike Drob
>             Fix For: master (7.0)
>         Attachments: LUCENE-5822-addemdum.patch, LUCENE-5822.patch, LUCENE-5822.patch
> We have a minimal plain text readme file right now. Github is very popular these days
and we are even accepting pull requests from there. I think we should add a proper markdown
formatted README file which not only talks about the features of Lucene/Solr but also include
a short tutorial on both Lucene and Solr.

This message was sent by Atlassian JIRA

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message