Gus Heck created SOLR-17259:
-------------------------------
Summary: Reverse the order of two ref guide steps in releaseWizard
Key: SOLR-17259
URL: https://issues.apache.org/jira/browse/SOLR-17259
Project: Solr
Issue Type: Bug
Security Level: Public (Default Security Level. Issues are Public)
Components: release-scripts
Reporter: Gus Heck
I think the reason I've had an issue with the publication of the ref guide for
9.6 is the order of steps 2 and 3 on this menu:
{code:java}
┌─────────────────────────────────────────────────────────────────────────┐
│ │
│ Update the website │
│ │
│ │
│ For every release, we publish docs on the website, we need to update │
│ the │
│ download pages etc. The website is hosted in │
│ https://github.com/apache/solr-site │
│ but the Javadocs and Solr Reference Guide are pushed to SVN and then │
│ included │
│ in the main site through links. │
│ │
│ │
│ 1 - ✓ Publish docs, changes and javadocs │
│ 2 - Update Ref Guide Metadata for release │
│ 3 - Check that the reference guide is ready │
│ 4 - Build the ref guide .htaccess file │
│ 5 - Do a clean git clone of the website repo │
│ 6 - Update website versions │
│ 7 - Update website ref-guide htaccess │
│ 8 - Author the Solr release news │
│ 9 - Update rest of webpage │
│ 10 - Stage the website changes │
│ 11 - Publish the website changes │
│ 12 - Update the DOAP file │
│ 13 - Return │
│ │
│ │
└─────────────────────────────────────────────────────────────────────────┘
{code}
The third step caused me to look at the ref guide and realize that some things
needed to be touched up. As part of bringing in those changes I beleive I ran
buildLocalSite to view them and ensure I hadn't broken anything (after updating
from git to get the changes). Unfortunately based on my reading of
[https://github.com/apache/solr/blob/main/solr/solr-ref-guide/build.gradle#L96]
this would have overwritten the antora.yaml file with incorrect version
information because the build relies on a passed in property to determine
released branch status, and of course I wouldn't have passed in any properties.
I'm still not 100% sure this caused my actual problem, but even if this isn't
the culprit, I can't see any reason we should start building things like the
antora.yaml file before the guide is actually set and ready to go.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
