You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@lucene.apache.org by "Jan Høydahl (Jira)" <ji...@apache.org> on 2020/01/22 09:09:00 UTC

[jira] [Commented] (SOLR-14149) Remove non-changes from CHANGES.txt

    [ https://issues.apache.org/jira/browse/SOLR-14149?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17020903#comment-17020903 ] 

Jan Høydahl commented on SOLR-14149:
------------------------------------

So is there some simple commits we can do in master and branch_8x that will clean up CHANGES and add a link to one or two RefGuide pages? Or do we need to wait for some other RefGuide JIRA to be resolved first?

> 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
>
> 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-unsubscribe@lucene.apache.org
For additional commands, e-mail: issues-help@lucene.apache.org