[
https://issues.apache.org/jira/browse/LUCENE-8883?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16881452#comment-16881452
]
David Smiley commented on LUCENE-8883:
--------------------------------------
Thanks Adrien for determining this list of actual usages! Just curious; did
you do this with a script or just haphazardly with repeated "Find" or similar?
I suppose we need differences between Lucene and Solr with this list. Solr
doesn't have "API Changes" as a section but it does use "Upgrade Notes" which
is conceptually similar. I'll have this list get passed into this method so
that we can specialize per-project.
For bug fix releases, I suppose we can detect this via the last octet being
non-zero? And then we only generate "Bug Fixes"?
I'm aware "Optimizations" has been a popular heading in Lucene's CHANGES.txt
but might it be better re-categorized as "Improvements", and thus make the
mapping of JIRA issue types to CHANGES heading the same? Or maybe for
consistency we could get this new type added to JIRA if it's so important?
I'll add "(No changes)".
> 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
> Attachments: LUCENE-8883.patch
>
>
> 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: [email protected]
For additional commands, e-mail: [email protected]
