[Checkins] SVN: Products.CMFCalendar/branches/2.1/ - pinning GS to 1.3.3

Tue Aug 26 07:23:09 EDT 2008

Log message for revision 90297:
  - pinning GS to 1.3.3
  - reformat README for PyPI prettiness
  - synthesized CHANGES.txt from the monolithic file at
    http://svn.zope.org/CMF/branches/2.1/CHANGES.txt?rev=87755&view=auto
  

Changed:
  _U  Products.CMFCalendar/branches/2.1/
  A   Products.CMFCalendar/branches/2.1/Products/CMFCalendar/CHANGES.txt
  U   Products.CMFCalendar/branches/2.1/Products/CMFCalendar/README.txt
  U   Products.CMFCalendar/branches/2.1/setup.py

-=-

Property changes on: Products.CMFCalendar/branches/2.1
___________________________________________________________________
Name: svn:ignore
   + Products.CMFCalendar.egg-info


Copied: Products.CMFCalendar/branches/2.1/Products/CMFCalendar/CHANGES.txt (from rev 90273, Products.CMFCalendar/trunk/Products/CMFCalendar/CHANGES.txt)
===================================================================

--- Products.CMFCalendar/branches/2.1/Products/CMFCalendar/CHANGES.txt	                        (rev 0)
+++ Products.CMFCalendar/branches/2.1/Products/CMFCalendar/CHANGES.txt	2008-08-26 11:23:09 UTC (rev 90297)
@@ -0,0 +1,98 @@
+Products.CMFCalendar Changelog
+==============================
+
+2.1.2 (2008-08-26)
+------------------
+
+- completed devolution from monolithic CMF package into its component
+  products that are distributed as eggs from PyPI.
+
+
+2.1.1 (2008-01-06)
+------------------
+
+- no changes
+
+
+2.1.1-beta(2007-12/29)
+----------------------
+
+- Testing: Derive test layers from ZopeLite layer if available.
+
+
+2.1.0 (2007-08-08)
+------------------
+
+- Fixed all componentregistry.xml files to use plain object paths and strip
+  and slashes. GenericSetup does only support registering objects which are
+  in the site root.
+
+
+2.1.0-beta2 (2007-07-12)
+------------------------
+
+- moved the Zope dependency to version 2.10.4
+
+- Remove antique usage of marker attributes in favor of interfaces,
+  leaving BBB behind for places potentially affecting third-party code.
+  (http://www.zope.org/Collectors/CMF/440)
+
+- Add POST-only protections to security critical methods.
+  http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2007-0240)
+
+- Fixed DST-driven test breakage by adding an optional 'zone' argument to 
+  the DublineCore methods which return string renditions of date metadata.
+  (http://www.zope.org/Collectors/CMF/476)
+
+
+2.1.0-beta (2007-03-09)
+-----------------------
+
+- moved the Zope dependency to verson 2.10.2
+
+- Tool lookup and registration is now done "the Zope 3 way" as utilities, see
+  http://svn.zope.org/CMF/branches/2.1/docs/ToolsAreUtilities.stx?view=auto
+
+- Zope3 style browser views are now used by default. An additional setup profile
+  allows you to hook up the oldstyle skins and to make customizations TTW.
+
+
+2.1.0-alpha2 (2006-11-23)
+-------------------------
+
+- moved the Zope dependency to version 2.10.1
+
+- Fixed test breakage induced by use of Z3 pagetemplates in Zope 2.10+.
+
+- browser views: Added some zope.formlib based forms.
+
+- testing: Added test layers for setting up ZCML.
+
+
+2.1.0-alpha (2006-10-09)
+------------------------
+
+- skins: Changed encoding of translated portal_status_messages.
+  Now getBrowserCharset is used to play nice with Five forms. Customized
+  setRedirect and getMainGlobals scripts have to be updated.
+
+- Profiles: All profiles are now registered by ZCML.
+
+- ZClasses: Removed unmaintained support for ZClasses.
+  Marked the 'initializeBases*' methods as deprecated.
+
+- Content: Added IFactory utilities for all content classes.
+  They are now used by default instead of the old constructor methods.
+
+- Content: All content classes are now registered by ZCML.
+  ContentInit is still used to register oldstyle constructors.
+
+- setup handlers: Removed support for CMF 1.5 CMFSetup profiles.
+
+
+Earlier releases
+----------------
+
+For a complete list of changes before version 2.1.0-alpha, see the HISTORY.txt
+file on the CMF-2.1 branch:
+http://svn.zope.org/CMF/branches/2.1/HISTORY.txt?view=auto

Modified: Products.CMFCalendar/branches/2.1/Products/CMFCalendar/README.txt
===================================================================
--- Products.CMFCalendar/branches/2.1/Products/CMFCalendar/README.txt	2008-08-26 11:22:40 UTC (rev 90296)
+++ Products.CMFCalendar/branches/2.1/Products/CMFCalendar/README.txt	2008-08-26 11:23:09 UTC (rev 90297)
@@ -1,25 +1,25 @@
-CMFCalendar README
+======================
+ Products.CMFCalendar
+======================
 
-  The CMFCalendar product is an example of creating a CMF
-  Product.  The CMFCalendar product is also expected to be a
-  generally useful out of the 'box' and skinnable to accomodate
-  customization within your existing CMF instance.  To see how to
-  go about building a CMF product, this hopefully allows a
-  developer to follow through the process of registering their
-  product, skins, and help with the CMF by example.  It shows how
-  an object is created and registered with the types_tool,
-  necessary skins added to the skins_tool, with the Calendar
-  skins directory added to the skin paths, and providing
-  portal_metadatool with an Element policy for the content_type
-  of the object.
+.. contents::
 
-  The event portal_type is complete, and can be stand alone, but
-  now accompanyied by the CMFCalendar which is fully functional
-  and tested.
+The CMFCalendar product is an example of creating a CMF
+Product.  The CMFCalendar product is also expected to be a
+generally useful *out of the box* and skinnable to accomodate
+customization within your existing CMF instance.  To see how to
+go about building a CMF product, this hopefully allows a
+developer to follow through the process of registering their
+product, skins, and help with the CMF by example.  It shows how
+an object is created and registered with the types_tool,
+necessary skins added to the skins_tool, with the Calendar
+skins directory added to the skin paths, and providing
+portal_metadatool with an Element policy for the content_type
+of the object.
 
-  For installing set the 'active site configuration' of your site's
-  setup tool to the CMFCalendar profile and import all steps.
+For installing set the *active site configuration* of your site's
+setup tool to the CMFCalendar profile and import all steps.
 
-  After installing the CMFCalendar you should notice a calendar
-  appear in your CMF.  This is fully customisable to your portals
-  needs.
+After installing the CMFCalendar you should notice a calendar
+appear in your CMF.  This is fully customisable to your portals
+needs.

Modified: Products.CMFCalendar/branches/2.1/setup.py
===================================================================
--- Products.CMFCalendar/branches/2.1/setup.py	2008-08-26 11:22:40 UTC (rev 90296)
+++ Products.CMFCalendar/branches/2.1/setup.py	2008-08-26 11:23:09 UTC (rev 90297)
@@ -48,7 +48,7 @@
           'Products.CMFDefault',
           'Products.CMFTopic',
           'Products.DCWorkflow',
-          'Products.GenericSetup',
+          'Products.GenericSetup==1.3.3',
           ],
       entry_points="""
       [zope2.initialize]

