Uploaded image for project: 'Lucene - Core'
  1. Lucene - Core
  2. LUCENE-1898

Decide if we should remove lines numbers from latest Changes

    XMLWordPrintableJSON

Details

    • Improvement
    • Status: Closed
    • Major
    • Resolution: Fixed
    • None
    • 2.9
    • core/other
    • None
    • New, Patch Available

    Description

      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.

      Attachments

        1. LUCENE-1898.patch
          60 kB
          Steven Rowe
        2. LUCENE-1898.patch
          46 kB
          Mark Miller

        Activity

          People

            markrmiller@gmail.com Mark Miller
            markrmiller@gmail.com Mark Miller
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: