[
https://issues.apache.org/jira/browse/HADOOP-1667?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12516824
]
Doug Cutting commented on HADOOP-1667:
--------------------------------------
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?
> organize CHANGES.txt messages into sections for future releases
> ---------------------------------------------------------------
>
> Key: HADOOP-1667
> URL: https://issues.apache.org/jira/browse/HADOOP-1667
> Project: Hadoop
> Issue Type: Improvement
> Components: documentation
> Reporter: Doug Cutting
> Assignee: Doug Cutting
> Fix For: 0.15.0
>
> Attachments: changes.patch
>
>
> 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.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
