[z3-checkins] r18149 - z3/Five/branch/Five-1.1

[philikon at codespeak.net]

Author: philikon
Date: Tue Oct  4 18:14:32 2005
New Revision: 18149

Modified:
   z3/Five/branch/Five-1.1/CHANGES.txt
Log:
sort entries into the usual categories: features, restructuring, bugfixes


Modified: z3/Five/branch/Five-1.1/CHANGES.txt
==============================================================================
--- z3/Five/branch/Five-1.1/CHANGES.txt	(original)
+++ z3/Five/branch/Five-1.1/CHANGES.txt	Tue Oct  4 18:14:32 2005
@@ -5,6 +5,25 @@
 Five 1.1 (2005-10-04)
 =====================
 
+Features
+--------
+
+* When Zope was not in debug mode, an error in a ZCML file would cause Five to
+  stop loading ZCML completely, making all subsequent products "dead". The
+  effect would typically be that objects appeared to have no views at all. 
+  Now a ZCML error will only stop the ZCML loading for that product, but the 
+  rest of the products will load as usual. A traceback will still be printed 
+  in the event log.
+
+  In debug mode the behaviour has not changed; a ZCML error will stop Zope 
+  startup completely, and print a traceback if running in foreground mode.
+  
+Restructuring
+-------------
+
+* The deprecated FivePageTemplateFile was removed, and the erroneous use of 
+  this by EditView was changed.
+
 Bugfixes
 --------
 
@@ -31,23 +50,10 @@
 * Added backwards compatibility for some moved classes (AddForm, EditForm, 
   ContentAdding)
 
-* The deprecated FivePageTemplateFile was removed, and the erroneous use of 
-  this by EditView was changed.
-
 * The ZPT variable 'container' makes little sense in Zope3/Five, but is now
   always set to be the same as 'here' which is normal Zope2 behaviour.
   It is in Five 1.0.x set to be the same as 'view' which breaks some templates.
   
-* When Zope was not in debug mode, an error in a ZCML file would cause Five to
-  stop loading ZCML completely, making all subsequent products "dead". The
-  effect would typically be that objects appeared to have no views at all. 
-  Now a ZCML error will only stop the ZCML loading for that product, but the 
-  rest of the products will load as usual. A traceback will still be printed 
-  in the event log.
-  
-  In debug mode the behaviour has not changed; a ZCML error will stop Zope 
-  startup completely, and print a traceback if running in foreground mode.
-  
 * In some hard to replicate cases, using the "modules" variable in ZPT cause
   an AuthenticationError. Using the secure module importer fixes this.