[
https://issues.apache.org/jira/browse/SOLR-15800?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17444729#comment-17444729
]
Cassandra Targett commented on SOLR-15800:
------------------------------------------
bq. I wonder if we can automate it all with Jenkins
I love the idea of automating the whole thing. Today it is a little hard since
by default we add this "DRAFT" watermark to all the pages so if people find
pre-release versions they at least have some indication it might not be the
right docs. Do we have to keep doing that? Is it actually helpful or useful?
I'd be willing to entertain "no" to both questions and see what opportunities
open up from there.
I also think this is the kind of thing Antora could help us with because it has
built-in logic to help us define how to handle version labels on pre-release
branches.
> 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
>
> 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: issues-unsubscr...@solr.apache.org
For additional commands, e-mail: issues-h...@solr.apache.org
