[
https://issues.apache.org/jira/browse/SOLR-15800?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17444787#comment-17444787
]
Jan Høydahl commented on SOLR-15800:
------------------------------------
The draft watermark is for sure needed on main branch and branch_9x etc, but on
the release branch branch_9_0, branch_9_1 etc, the refguide build could be
kicked off without watermark, since that branch is actually released (or soon
to be). But I don't know how easy it is to have Jenkins do svn import
automatically... Guess infra can help us with that. [~uschindler] ? That
Jenkins job may kick off for every commit but exit if no changes to the ref
guide.
> Make publishing the Ref Guide a step in the release process
> -----------------------------------------------------------
>
> Key: SOLR-15800
> URL: https://issues.apache.org/jira/browse/SOLR-15800
> Project: Solr
> Issue Type: Task
> Security Level: Public(Default Security Level. Issues are Public)
> Components: documentation
> Reporter: Cassandra Targett
> Priority: Blocker
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> Publishing the Ref Guide for each release is still done "outside" the Solr
> artifact release process, done basically manually by a single person. So when
> she isn't available, it seems to often get skipped.
> If we agree that the Ref Guide is an important part of the release, and that
> we should release a new version in conjunction with the artifacts, then it
> should be part of the overall release process.
> I don't understand the release process or wizard well enough to know how to
> integrate the steps, so cannot tackle this myself.
> The steps are documented in our source repo:
> https://github.com/apache/solr/blob/main/dev-docs/ref-guide/publish.adoc
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
