You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "David Smiley (JIRA)" <ji...@apache.org> on 2019/08/06 11:55:00 UTC
[jira] [Resolved] (LUCENE-8883) CHANGES.txt: Auto add issue
categories on new releases
[ https://issues.apache.org/jira/browse/LUCENE-8883?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
David Smiley resolved LUCENE-8883.
----------------------------------
Resolution: Fixed
Fix Version/s: 8.3
> 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
> Fix For: 8.3
>
> Attachments: LUCENE-8883.patch, LUCENE-8883.patch, 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.14#76016)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org