You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Mark Miller (JIRA)" <ji...@apache.org> on 2009/09/08 01:32:57 UTC
[jira] Updated: (LUCENE-1898) Decide if we should remove lines
numbers from latest Changes
[ https://issues.apache.org/jira/browse/LUCENE-1898?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mark Miller updated LUCENE-1898:
--------------------------------
Attachment: LUCENE-1898.patch
> 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
>
> Attachments: LUCENE-1898.patch
>
>
> 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-unsubscribe@lucene.apache.org
For additional commands, e-mail: java-dev-help@lucene.apache.org