Uploaded image for project: 'Hadoop Common'
  1. Hadoop Common
  2. HADOOP-1667

organize CHANGES.txt messages into sections for future releases

Details

    • Improvement
    • Status: Closed
    • Major
    • Resolution: Fixed
    • None
    • 0.15.0
    • documentation
    • None

    Description

      The entries in CHANGES.txt should have the following sections per release:

      INCOMPATIBLE CHANGES
      NEW FEATURES
      OPTIMIZATIONS
      BUG FIXES

      This should make it easier for folks to read this file.

      Attachments

        1. changes.patch
          1 kB
          Doug Cutting

        Activity

          cutting Doug Cutting added a comment -

          Here's a patch. I've also removed the numbering, which complicated merging. Now folks should be able to more easily include change messages with their patches.

          cutting Doug Cutting added a comment - Here's a patch. I've also removed the numbering, which complicated merging. Now folks should be able to more easily include change messages with their patches.

          +1. This looks good.

          dhruba Dhruba Borthakur added a comment - +1. This looks good.
          cutting Doug Cutting added a comment -

          I just committed this.

          cutting Doug Cutting added a comment - I just committed this.

          Can you pl clarify what is an INCOMPATIBLE change? For example, is a change in ClientProtocol an incompatible change?

          dhruba Dhruba Borthakur added a comment - Can you pl clarify what is an INCOMPATIBLE change? For example, is a change in ClientProtocol an incompatible change?
          cutting Doug Cutting added a comment -

          I'd define an incompatible change as anything that requires the user to do more than restart the cluster on version upgrade: any changes required to user code, any upgrade procedures, etc. An internal protocol change isn't necessarily incompatible: we don't in general support RPCs across versions. Does that work?

          cutting Doug Cutting added a comment - I'd define an incompatible change as anything that requires the user to do more than restart the cluster on version upgrade: any changes required to user code, any upgrade procedures, etc. An internal protocol change isn't necessarily incompatible: we don't in general support RPCs across versions. Does that work?
          rangadi Raghu Angadi added a comment -

          +1 : I don't think RPC version changes qualify as 'incompatible'.

          rangadi Raghu Angadi added a comment - +1 : I don't think RPC version changes qualify as 'incompatible'.

          People

            cutting Doug Cutting
            cutting Doug Cutting
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: