[
https://issues.apache.org/jira/browse/SOLR-15926?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17476694#comment-17476694
]
Cassandra Targett commented on SOLR-15926:
------------------------------------------
bq. Currently many places use the docs version (major.minor) with .0 added to
the end
I'm not sure I'm following this statement - do you have an example where you
see where we're using the major.minor version and tacking on .0 to the end?
Part of me suspects what you're seeing is simply a wide inconsistency in the
part of our various content authors with regard to when and how they refer to a
version. In most cases there shouldn't really be talk about a specific version
at all - the Ref Guide is versioned, so there's no need for things like "Now in
8.8.0..." or "Until 7.7.3..." That stuff should be in the upgrade notes, and
the page itself should just talk about how the feature works for that version.
I occasionally will edit these out, but don't have a ton of time for to seek
out little things like this.
> Fix version specification in the Solr Ref Guide
> -----------------------------------------------
>
> Key: SOLR-15926
> URL: https://issues.apache.org/jira/browse/SOLR-15926
> Project: Solr
> Issue Type: Bug
> Security Level: Public(Default Security Level. Issues are Public)
> Components: documentation
> Affects Versions: 9.0
> Reporter: Houston Putman
> Priority: Blocker
>
> Currently many places use the docs version (major.minor) with .0 added to the
> end, when we can easily just use the full solr version instead.
> There are also instances where the Solr version is used for the lucene
> version. This needs to be updated now that the two cannot be conflated.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@solr.apache.org
For additional commands, e-mail: issues-h...@solr.apache.org
