[
https://issues.apache.org/jira/browse/SOLR-14149?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17021575#comment-17021575
]
Cassandra Targett commented on SOLR-14149:
------------------------------------------
bq. Perhaps we could change the release process so that the RefGuide is always
published as-is on the day of the release
Uhhh, we already did make that change [1].
Since that thread (around 8.2), every X.y.0 release I publish a DRAFT version
as soon as I can after the RC is up for vote (the same day so far). I've
replied to the VOTE threads with the URLs. As soon as the release artifacts are
published, I update the version to the final (remove the DRAFT watermark and
publish latest updates). The only thing from that thread that I have not yet
done is automate it for the release manager to be able to push it themselves
(mostly because I don't know how).
If you want to include versioned Ref Guide URLs in CHANGES.txt for the upgrade
notes, there is no barrier to do so as far as I'm concerned.
bq. I removed "Upgrade Notes" from CHANGES.txt because arguably this should
only go to solr-upgrade-notes.adoc because it's more narrative-like and doesn't
replace the Jira issue references that generally should remain in their
appropriate sections. WDYT? I predict Cassandra Targett is a fan
Ha! Yes, you're right, I love the idea.
[1] Thread where we discussed this:
https://lists.apache.org/thread.html/f517b3b74a0a33e5e6fa87e888459fc007decc49d27a4f49822ca2ee%40%3Cdev.lucene.apache.org%3E
> Remove non-changes from CHANGES.txt
> -----------------------------------
>
> Key: SOLR-14149
> URL: https://issues.apache.org/jira/browse/SOLR-14149
> Project: Solr
> Issue Type: Improvement
> Reporter: David Smiley
> Assignee: David Smiley
> Priority: Minor
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Our CHANGES.txt should just list our changes / release notes. Nothing else.
> * no Introduction
> * no "Getting Started"
> * no "Versions of Major Components" with each release.
> We have a website, a reference guide, and a README.md that are all more
> suitable places. Lets not maintain it here as well; lets keep this file
> focused on it's namesake. We can/should *link* to that information from
> CHANGES.txt. For example linking to
> https://lucene.apache.org/solr/guide/8_4/solr-upgrade-notes.html is highly
> appropriate as it's a more user friendly editorialized version of CHANGES.txt.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org
For additional commands, e-mail: issues-h...@lucene.apache.org
