: I don't think this should prevent a hypothetical 5.6 release of the code : (Lucene/Solr itself). It would just either not have a companion ref guide, : or maybe we could add some simple addendum (some simple pages) to the front : or something.
I don't have a link handy, but I remember this exact hypothetical question was discussed when the decision was first made to accept the ref guide content and use confluence to manage it, and the concensus at the time was that it was going to be enough of an effort to keep the ref guide up to date with the "latest" released version, let alone trying to maintaining multiple "branches" to handle the possibility of minor releases off the stable branch (or publishing updates with errata regarding bug fixes on X.Y.1 releases) -Hoss http://www.lucidworks.com/ --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
