Steve McMahon 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.
Me bad :-(
I'm so sorry, I wasn't aware that we are aiming for
2.1 compatibility as well. I did test on 2.5 and as
all test pass there even after me introducing the
GS profile I thought it's fine to commit it right
away.
Again sorry for the trouble and thanks for cleaning
up after myself,
Raphael
(PS: I shouldn't be doing dev work if I can only affort
a few hours at random times per week at all ... and
I remember now that you told me the other day to branch
off which I had thought I did but now looking back I realize
that I did this for PSC only and not PHC - me needs to
get better organized ...)
My goal is to release PHC 1.0.0 within the next couple of weeks, then
try to get a 1.5.0 released very quickly that will add Plone 3.0
compatibility.
Steve
Raphael Ritz wrote:
Martijn Pieters wrote:
On 9/20/07, Raphael Ritz
<[EMAIL PROTECTED]> wrote:
Turning to the helpcenter next before getting back to the remaining
issues for PSC.
I've already massaged PSC to at least import on Plone 3, for a
customer migration project.
any chance this makes it into the collective then?
BTW: current trunk works on P2.5 and 3 reasonably well TTP
by now.
I have not yet tested migrating existing content however.
Raphael
_______________________________________________
Product-Developers mailing list
[email protected]
http://lists.plone.org/mailman/listinfo/product-developers
_______________________________________________
Product-Developers mailing list
[email protected]
http://lists.plone.org/mailman/listinfo/product-developers
