[
https://issues.apache.org/jira/browse/SOLR-238?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12495706
]
Hoss Man commented on SOLR-238:
-------------------------------
Thorsten ... thanks for the prod on this issue. One thing that makes this
tricky is that the tutorial (and the entire website) are bundled with every
release ... that's why we keep the site up to date with the trunk, so that
people can review the docs as time goes on, but when a release is cut people
using that release should refer to the docs that come with it.
I'm not very knowledgeable in forest, do you (or anyone else watching this
issue) know if there is an easy way to do variable substitution into the
generated docs when they are build using property files (or something like it)
Then the docs could always contain the current Solr spec version number when
the tutorial is regenerated (for official releases, the spec version number
looks like 1.1, 1.2, etc... for nightly builds it looks like
1.1.2007.05.11.10.10.53 -- the last official version number followed by the
current datetime)
> [Patch] The tutorial on our website is against trunk which causes confusion
> by user
> -----------------------------------------------------------------------------------
>
> Key: SOLR-238
> URL: https://issues.apache.org/jira/browse/SOLR-238
> Project: Solr
> Issue Type: Improvement
> Components: documentation
> Reporter: Thorsten Scherler
> Attachments: SOLR-238.diff, SOLR-238.png
>
>
> The patch will add a note to the tutorial page with the following headsup:
> "This is documentation for the development version (TRUNK). Some instructions
> may only work if you are working against svn head."
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
