[
https://issues.apache.org/jira/browse/SOLR-15800?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17444870#comment-17444870
]
Gus Heck commented on SOLR-15800:
---------------------------------
I'm wondering if it couldn't be a fully automated job so that the RM didn't
have to do a thing. Scan for tags, matching the format and publish. Also
publish the alpha version from main (clearly marked alpha)....
[~janhoy] You say we need the DRAFT watermark? Why? The point is to not confuse
folks into thinking features are permanent or available etc.... The fact it's
an alpha version should adequately communicate that? Sure the DRAFT watermark
is kinda neat, but if it's in the way of automating, maybe it's not neat
enough? Is there some high level policy around artifacts that specifically
requires it?
> 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: issues-unsubscr...@solr.apache.org
For additional commands, e-mail: issues-h...@solr.apache.org
