[PLIP-Advisories] Re: [Plone] #8808: Require Python 2.5 or 2.6, Zope 2.12, and CMF 2.2 for Plone 4.0

2009-10-13 Thread plip-advisories
#8808: Require Python 2.5 or 2.6, Zope 2.12, and CMF 2.2 for Plone 4.0
+---
 Reporter:  hannosch|Owner:  davisagli
 Type:  PLIP|   Status:  closed   
 Priority:  major   |Milestone:  4.0  
Component:  Infrastructure  |   Resolution:  fixed
 Keywords:  |  
+---
Changes (by esteele):

  * status:  assigned = closed
  * resolution:  = fixed


-- 
Ticket URL: http://dev.plone.org/plone/ticket/8808#comment:27
Plone http://plone.org
Plone Content Management System
___
PLIP-Advisories mailing list
plip-advisor...@lists.plone.org
http://lists.plone.org/mailman/listinfo/plip-advisories


[PLIP-Advisories] Re: [Plone] #8808: Require Python 2.5 or 2.6, Zope 2.12, and CMF 2.2 for Plone 4.0

2009-10-09 Thread plip-advisories
#8808: Require Python 2.5 or 2.6, Zope 2.12, and CMF 2.2 for Plone 4.0
+---
 Reporter:  hannosch|Owner:  davisagli
 Type:  PLIP|   Status:  assigned 
 Priority:  major   |Milestone:  4.0  
Component:  Infrastructure  |   Resolution:   
 Keywords:  |  
+---

Comment(by esteele):

 Please assist the doc team in creating/updating documentation relating to
 this PLIP. See #9620.

-- 
Ticket URL: http://dev.plone.org/plone/ticket/8808#comment:26
Plone http://plone.org
Plone Content Management System
___
PLIP-Advisories mailing list
plip-advisor...@lists.plone.org
http://lists.plone.org/mailman/listinfo/plip-advisories


[PLIP-Advisories] Re: [Plone] #8808: Require Python 2.5 or 2.6, Zope 2.12, and CMF 2.2 for Plone 4.0

2009-07-25 Thread plip-advisories
#8808: Require Python 2.5 or 2.6, Zope 2.12, and CMF 2.2 for Plone 4.0
+---
 Reporter:  hannosch|Owner:  davisagli
 Type:  PLIP|   Status:  assigned 
 Priority:  major   |Milestone:  4.0  
Component:  Infrastructure  |   Resolution:   
 Keywords:  |  
+---
Changes (by grahamperrin):

 * cc: grahamper...@gmail.com (added)


-- 
Ticket URL: http://dev.plone.org/plone/ticket/8808#comment:23
Plone http://plone.org
Plone Content Management System
___
PLIP-Advisories mailing list
plip-advisor...@lists.plone.org
http://lists.plone.org/mailman/listinfo/plip-advisories


[PLIP-Advisories] Re: [Plone] #8808: Require Python 2.5 or 2.6, Zope 2.12, and CMF 2.2 for Plone 4.0

2009-07-13 Thread plip-advisories
#8808: Require Python 2.5 or 2.6, Zope 2.12, and CMF 2.2 for Plone 4.0
+---
 Reporter:  hannosch|Owner:  davisagli
 Type:  PLIP|   Status:  assigned 
 Priority:  major   |Milestone:  4.0  
Component:  Infrastructure  |   Resolution:   
 Keywords:  |  
+---
Changes (by davisagli):

  * status:  new = assigned


Comment:

 Update:

  * As of last Tuesday, all the backporting work so far has been merged and
 is now the official Plone 4 branch.  Bugs remain, no doubt, and should be
 filed in trac against the 4.0 milestone.
  * At this point, most tests are passing, even while using the same
 package as 3.3 for quite a few more minor packages.  Packages with
 remaining test issues: CMFPlone (1 failure), kss.core (1 failure, 1
 error), plone.app.customerize (2 failures), plone.app.layout (3 failures),
 plone.app.linkintegrity (25 failures), wicked (3 failures, 43 errors but
 that's b/c I haven't run the tests correctly yet), CMFEditions (6
 failures, 1 error), CMFPlacefulWorkflow (1 error), PluggableAuthService
 (16 errors), SecureMailHost (5 errors but this will be removed by another
 PLIP).  (These numbers may be a bit out of date.)  Please feel free to
 help me track down these issues.  Some packages will require a new release
 even though their tests are all passing already, in order to clean up
 deprecation warnings.
  * It would be helpful if someone could start trying out some common add-
 on products and start to document the ways in which they break, so we can
 document commonly needed changes and/or correct things to avoid them.
  * As of today, the branch now has PlonePAS from trunk, which includes
 some refactoring from Hanno to remove the group and member tool
 implementations from CMFPlone (the functionality has been merged into the
 versions of those tools in PlonePAS...essentially it's just collapsing
 some pointless class inheritance) and remove our dependency on
 GroupUserFolder.
  * I'm having second thoughts about the decision to remove most global
 template variables.  We definitely should make Plone itself not depend on
 them being available, which is now the case, but I'm not sure it's worth
 the add-on product breakages this will cause.  Hanno, you've told me
 before that the global_defines were a performance bottleneck...do you have
 any numbers?
  * Andreas Jung has proposed the following release schedule for Zope 2.12:
 Beta 3: July 14th, RC 1: August 6th, Final: September 4th.  The main thing
 that could block this is the final ZODB 3.9 release.
  * Tres Seaver said CMF 2.2 can probably be released whenever Zope 2.12
 is.

-- 
Ticket URL: http://dev.plone.org/plone/ticket/8808#comment:22
Plone http://plone.org
Plone Content Management System
___
PLIP-Advisories mailing list
plip-advisor...@lists.plone.org
http://lists.plone.org/mailman/listinfo/plip-advisories


[PLIP-Advisories] Re: [Plone] #8808: Require Python 2.5 or 2.6, Zope 2.12, and CMF 2.2 for Plone 4.0

2009-07-02 Thread plip-advisories
#8808: Require Python 2.5 or 2.6, Zope 2.12, and CMF 2.2 for Plone 4.0
+---
 Reporter:  hannosch|Owner:  davisagli
 Type:  PLIP|   Status:  new  
 Priority:  major   |Milestone:  4.0  
Component:  Infrastructure  |   Resolution:   
 Keywords:  |  
+---

Comment(by esteele):

 Approved by FWT vote.

-- 
Ticket URL: http://dev.plone.org/plone/ticket/8808#comment:21
Plone http://plone.org
Plone Content Management System
___
PLIP-Advisories mailing list
plip-advisor...@lists.plone.org
http://lists.plone.org/mailman/listinfo/plip-advisories