Those changes were fine. It's the recent work on adding a GS profile
that broke under Plone 2.1.
And, I'd like to make it clear I'm not complaining! All work on PHC is
appreciated. I'm just trying to keep a little control of PHC 1.0 pending
its release. I have this theory that it's not a good idea to make big
changes at the RC2 stage ;) .
I think that now that 1.0 is in a branch, that will be no problem.
Steve
Martijn Pieters wrote:
On 9/20/07, Steve McMahon <[EMAIL PROTECTED]> wrote:
Just a reminder: PHC 1.0 is promised to work with Plone 2.1 and 2.5.
This may seem archaic, but that was the original target, and several
Plone 2.1 users have contacted me to indicate they are depending on it.
So, if you add any code that breaks 2.1 or 2.5 compatibility, please
guard it with version test code or do it in a branch.
All my fixes for PHC where import-only fixes, where I used try:/except
ImportError: blocks to preserve Plone 2.1 compatibility.
--
______________________________________________________
Steve McMahon
Reid-McMahon, LLC
[EMAIL PROTECTED]
[EMAIL PROTECTED]
_______________________________________________
Product-Developers mailing list
[email protected]
http://lists.plone.org/mailman/listinfo/product-developers
