[
https://issues.apache.org/jira/browse/SOLR-14149?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17033118#comment-17033118
]
ASF subversion and git services commented on SOLR-14149:
--------------------------------------------------------
Commit e6701680f4ecb051dc932cd1b809abe4b84eb6b5 in lucene-solr's branch
refs/heads/branch_8x from David Smiley
[ https://gitbox.apache.org/repos/asf?p=lucene-solr.git;h=e670168 ]
SOLR-14149: CHANGES.txt Remove off-topic stuff
* No Introduction (to Solr) header. Point at solr-upgrade-notes.adoc instead
* No Getting Started header
* No Versions of Major Components header
* No "Upgrade Notes" for subsequent releases. See solr-upgrade-notes.adoc
Closes #1202
(cherry picked from commit 46c09456140fca0244ef726bd18a3ca7c5c7d131)
> 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: 1h 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
