[ https://issues.apache.org/jira/browse/SOLR-14214?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17023284#comment-17023284 ]
ASF subversion and git services commented on SOLR-14214: -------------------------------------------------------- Commit ba77a5f2eb13ffb418b84dac1df957dc3e9e2247 in lucene-solr's branch refs/heads/master from Cassandra Targett [ https://gitbox.apache.org/repos/asf?p=lucene-solr.git;h=ba77a5f ] SOLR-14214: Clean up client lists and references > Ref Guide: Clean up info about clients other than SolrJ > ------------------------------------------------------- > > Key: SOLR-14214 > URL: https://issues.apache.org/jira/browse/SOLR-14214 > Project: Solr > Issue Type: Improvement > Components: documentation > Reporter: Cassandra Targett > Priority: Major > > The Ref Guide page client-api-lineup.adoc may have been updated at some point > since Nov 2011, the last time it says it was updated, but I would guess > probably not very recently. > It really would be worth going through the list to see which ones are still > active and removing those that would not work with modern versions of Solr > (say, 6.x or 7.x+?). > My personal POV is that all info on clients should be kept in the Wiki > (cwiki) and the Ref Guide merely link to that - that would allow client > maintainers to keep info about their clients up to date without needing to be > a committer in order to update the Ref Guide. > That approach would mean pretty much removing everything from the > client-api-lineup.adoc page, and also likely removing most if not all of the > other Client pages for Ruby, Python, and JS. > However it plays out, we should take a look at those pages and update > according to the current state of the client universe. -- This message was sent by Atlassian Jira (v8.3.4#803005) --------------------------------------------------------------------- To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org For additional commands, e-mail: issues-h...@lucene.apache.org