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

Alexandre Rafalovitch commented on LUCENE-8883:
-----------------------------------------------

I wonder if we could also include the templates for various ways to make the 
actual change entry (single JIRA, multi JIRA, multi-users, hattip, username vs 
real names, etc). The ideal thing would have been to be able to completely 
parse the README entries, instead of regexp hack them as happens now for HTML 
conversion.

> CHANGES.txt: Auto add issue categories on new releases
> ------------------------------------------------------
>
>                 Key: LUCENE-8883
>                 URL: https://issues.apache.org/jira/browse/LUCENE-8883
>             Project: Lucene - Core
>          Issue Type: Task
>          Components: general/build
>            Reporter: David Smiley
>            Assignee: David Smiley
>            Priority: Minor
>
> As I write this, looking at Solr's CHANGES.txt for 8.2 I see we have some 
> sections: "Upgrade Notes", "New Features", "Bug Fixes", and "Other Changes".  
> There is no "Improvements".... so no surprise here, the New Features category 
> has issues that ought to be listed as such.  I think the order vary as well.  
> I propose that on new releases, the initial state of the next release in 
> CHANGES.txt have these sections.  They can easily be removed at the upcoming 
> release if there are no such sections, or they could stay as empty.  It seems 
> addVersion.py is the code that sets this up and it could be enhanced.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org

Reply via email to