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

David Smiley commented on SOLR-14149:
-------------------------------------

I'll throw up a PR later today Jan.  Maybe the only issue I see is maintaining 
what the outgoing link is since 
https://lucene.apache.org/solr/guide/8_4/solr-upgrade-notes.html is versioned, 
and it doesn't exist until the release actually happens.  We could refer to 
solr-upgrade-notes.adoc instead?  Or give up and don't link :-)  Or maybe the 
release process would do something here; maybe you'd know about that Jan; I've 
never done a release.

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

Reply via email to