Decide if we should remove lines numbers from latest Changes ------------------------------------------------------------
Key: LUCENE-1898 URL: https://issues.apache.org/jira/browse/LUCENE-1898 Project: Lucene - Java Issue Type: Improvement Components: Other Reporter: Mark Miller Fix For: 2.9 As Lucene dev has grown, a new issue has arisen - many times, new changes invalidate old changes. A proper changes file should just list the changes from the last version, not document the dev life of the issues. Keeping changes in proper order now requires a lot of renumbering sometimes. The numbers have no real meaning and could be added to more rich versions (such as the html version) automatically if desired. I think an * makes a good replacement myself. The issues already have ids that are stable, rather than the current, decorational numbers which are subject to change over a dev cycle. I think we should replace the numbers with an asterix for the 2.9 section and going forward (ie 4. becomes *). If we don't get consensus very quickly, this issue won't block. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. --------------------------------------------------------------------- To unsubscribe, e-mail: java-dev-unsubscr...@lucene.apache.org For additional commands, e-mail: java-dev-h...@lucene.apache.org