[
https://issues.apache.org/jira/browse/SOLR-10675?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16008578#comment-16008578
]
Hoss Man commented on SOLR-10675:
---------------------------------
[~thetaphi] it does in fact work very similar, and if you note in the
patch/commits both the "guide version" and "solr version" defaults come from
the existing {{version.properties}} file -- but please note my comments when i
attached the patch...
bq. This will typically be the same - but now if we want to do a "bug fix
release" of the guide itself, we can – and if we do so, the bug fix number for
the doc doesn't need to be tied to any particular code bug fix that has/has not
yet happened on the same branch_X_Y
We specifically can *NOT* depend on the guide version matching the
{{version.base}} to know if it's a "release" because the {{version.base}} on
the release branch will be incremented immediately after the code releases, but
the solr guide may be released after that. likewise, we may want to do a
"guide bugfix" release (to fix some egregious formatting mistake or missleading
content) independent of if/when there was a "code bugfix" release on the same
branch.
hence the introduction of the new {{solr-guide-version}} sys property.
> differentiate DRAFT builds of the html/pdf ref-guides vs the official releases
> ------------------------------------------------------------------------------
>
> Key: SOLR-10675
> URL: https://issues.apache.org/jira/browse/SOLR-10675
> Project: Solr
> Issue Type: Sub-task
> Security Level: Public(Default Security Level. Issues are Public)
> Components: documentation
> Reporter: Hoss Man
> Assignee: Hoss Man
> Fix For: 6.6, master (7.0)
>
> Attachments: draft-background.png, SOLR-10675.patch
>
>
> We should tweak the build system for the new ref guide so that it's obvious
> from the artifacts when they are unofficial "DRAFT" copies (default) vs
> official releases
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
