[Zope-CMF] Seeing what changes have happened.

[seb bacon]

Not sure I get your drift...what's wrong with a cvs diff for helping
you to work out how the file has changed?

Upgrading to CMF1.1 broke one of my products in all sorts of lairy
ways, and it took me a while to sort it out.  In particular, there was
a change in PortalContent which wasn't documented in the changelog, so
I wasn't sure why or when it was added.  In the absence of enough
spare time to work it out, I replaced it with an old PortalContent and
everything *seems* to work fine.  But this could become a 'bit' of a
problem in the future.  

I wonder if it's feasible for the DC folks to circulate proposed
changes before they're made, perhaps on a different mailing list
(cmf-dev?) as a matter of course?  Or would this be impractical?  

seb

* Chris Withers <chrisw@nipltd.com> [010626 16:26]:
> Hi,
> 
> I just ran into a problem I've been anticipating for a while.
> 
> I customised a skin, now the underlying method has changed to fix a bug. I can't
> see what I need to change in my customised version to get the same effect.
> 
> Has anyone else experienced this?
> Has anyone found a solution?
> 
> cheers,
> 
> Chris
> 
> _______________________________________________
> Zope-CMF maillist  -  Zope-CMF@zope.org
> http://lists.zope.org/mailman/listinfo/zope-cmf
> 
> See http://www.zope.org/Products/PTK/Tracker for bug reports and feature requests