Jan Høydahl created SOLR-15817:
----------------------------------
Summary: Ensure refGuide upgrade notes are completed before
announcing a release
Key: SOLR-15817
URL: https://issues.apache.org/jira/browse/SOLR-15817
Project: Solr
Issue Type: Improvement
Security Level: Public (Default Security Level. Issues are Public)
Components: documentation, release-scripts
Reporter: Jan Høydahl
Assignee: Jan Høydahl
Now when we have started publishing the RefGuide as part of the actual release,
we need to make sure it is ready. For the 8.11 release the announcement went
out with a broken link to refGuide, and when the guide was published it lacked
Upgrade Notes for 8.11.
The proposal is as I wrote in
[dev@email|https://lists.apache.org/thread/m0gofszo79l96s0gv0yj6r4mp9np0zho]:
{quote}
Early on, right after cutting the branch, the RM files a blocker JIRA issue
with title e.g. "Complete Major changes and Upgrade Notes in RefGudie for 9.1".
Note that the RM will not need to be the one authoring the text (and not
Cassandra either), but the release will be blocked on *someone* stepping up.
And of course we know that RCs can in theory still be voted upon while ref
guide is being completed, but that blocker JIRA must be resolved before
announcing the release.
{quote}
I plan to add two steps to RM process - 1) to file that blocker JIRA, and 2)
making sure the blocker is closed before announcing the release.
--
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
