lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robert Muir (JIRA)" <>
Subject [jira] [Commented] (SOLR-4618) Integrate LucidWorks' Solr Reference Guide with Solr documentation
Date Wed, 20 Mar 2013 19:23:15 GMT


Robert Muir commented on SOLR-4618:

    * separate page for minor errata about previous releases (since they would just be PDFs
if we go with that strategy).

isn't that just CHANGES.txt?

I was thinking in case we had a horrible documentation bug in 4.2.PDF and we just today realized
it, we could have 4.2-Errata which is a list of corrections.

    After we release 4.5 or 4.9 or whatever is the last minor one, we work on integrating
the trunk changes before 5.0 and clear that page for 6.0

I'm okay with that ... but i'm suprised you're suggesting it – you're usually the biggest
proponent of keeping trunk in a state that it could, in theory, be released as X.0 on a moments
notice – this type of a approach would mean a decent amount of doc work needed to make a
bunch of doc changes related to trunk specific features/improvements just before an X.0 release.

Under this plan we still could? We'd make 5.0.PDF and i'd take the TrunkChanges page and copy
it into 5.0-Errata :)

I'm not recommending we would actually do that: its evil, I'm just saying there would exist
a shortest path to make it possible in case we really want to release and no one is willing
to do the doc work to make it nice.

Mainly I was just trying to suggest a solution that would be simplest to manage since clearly
our docs could use improvement.
> Integrate LucidWorks' Solr Reference Guide with Solr documentation
> ------------------------------------------------------------------
>                 Key: SOLR-4618
>                 URL:
>             Project: Solr
>          Issue Type: Improvement
>          Components: documentation
>    Affects Versions: 4.1
>            Reporter: Cassandra Targett
>         Attachments: NewSolrStyle.css,
> LucidWorks would like to donate the "Apache Solr Reference Guide", maintained by LucidWorks
tech writers, to the Solr community. It was first produced in 2009 as a download-only PDF
for Solr 1.4, but since 2011 it has been online at
and updated for Solr 3.x releases and for Solr 4.0 and 4.1.
> I've prepared an XML export from our Confluence installation, which can be easily imported
into the Apache Confluence installation by someone with system admin rights. The doc has not
yet been updated for 4.2, so it covers Solr 4.1 so far. I'll add some additional technical
notes about the export itself in a comment. 
> Since we use Confluence at LucidWorks, I can also offer assistance getting Confluence
set up, importing this package into it, or any other help needed for the community to start
using this. 

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

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

View raw message