[ https://issues.apache.org/jira/browse/SOLR-15800?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17466993#comment-17466993 ]
ASF subversion and git services commented on SOLR-15800: -------------------------------------------------------- Commit c2db3a943e665cfb39e9ea53640be40cf2c09fbc in solr's branch refs/heads/main from Houston Putman [ https://gitbox.apache.org/repos/asf?p=solr.git;h=c2db3a9 ] SOLR-15800: Add ref-guide upload to the release wizard. (#419) * Add ref-guide upload to the release wizard. * Add a list stage before deleting remote svn files Co-authored-by: Mike Drob <md...@apache.org> Co-authored-by: Jan Høydahl <jan...@apache.org> > 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 > Components: documentation > Reporter: Cassandra Targett > Assignee: Jan Høydahl > Priority: Blocker > Fix For: main (9.0) > > Time Spent: 1.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