documentation/8179: 'Changes' file format should be changed for readability

[Neil Hare <Ne...@fme.fujitsu.com>]

>Number:         8179
>Category:       documentation
>Synopsis:       'Changes' file format should be changed for readability
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    apache
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          change-request
>Submitter-Id:   apache
>Arrival-Date:   Tue Aug 14 00:40:00 PDT 2001
>Closed-Date:
>Last-Modified:
>Originator:     Neil.Hare@fme.fujitsu.com
>Release:        all
>Organization:
apache
>Environment:
all versions, all OS
>Description:
It is very difficult to tell from the 'CHANGES' document if an update is
necessary or not. I would suggest that for each new version the following
sections be created: "Security fixes", "Bug fixes", "Enhancements" and under
each of these catagories the different platform changes should be grouped 
together (e.g. Win32, UNIX, OS2, Linux, Solaris, etc. or all). These changes would
help all administrators (like myself) to quickly decide if an update is necessary
or not. I am happy with the features that Apache 1.3.19 provides, but need to be
able to tell quickly if I should update to the newest version due to Apache 
security issues for the platform that I am running.

If these changes are not possible (for whatever reason), I would suggest at a minimum
that each line start with the platform affected and the word 'SECURITY' if the
change fixes a security issue, 'BUG' for bug fixes, and 'NEW' for new features. 
For example, "Solaris (SECURITY) - fixed bug in mod_xxx which would allow root compromise...."

Thank you for your great work at the Apache Group!!!

Best Regards,

Neil Hare
>How-To-Repeat:

>Fix:

>Release-Note:
>Audit-Trail:
>Unformatted:
 [In order for any reply to be added to the PR database, you need]
 [to include <ap...@Apache.Org> in the Cc line and make sure the]
 [subject line starts with the report component and number, with ]
 [or without any 'Re:' prefixes (such as "general/1098:" or      ]
 ["Re: general/1098:").  If the subject doesn't match this       ]
 [pattern, your message will be misfiled and ignored.  The       ]
 ["apbugs" address is not added to the Cc line of messages from  ]
 [the database automatically because of the potential for mail   ]
 [loops.  If you do not include this Cc, your reply may be ig-   ]
 [nored unless you are responding to an explicit request from a  ]
 [developer.  Reply only with text; DO NOT SEND ATTACHMENTS!     ]