[Zope-CMF] Seeing what changes have happened.

[Seb Bacon]

I guess what we really need is a well-defined, well-documentated API,
and a clear, visible process for changing it.  

Actually, the API is pretty well defined.  If someone could write a
script which produces some documentation for the public parts, and
publish this, it would be nice (I've not tried Dieter's API doctool
thing yet, perhaps it's what is needed?)

The change process is probably the area which needs more thought,
although perhaps such a thing already exists but it's not visible
enough?  DC folks, is there such a process?  How could it be improved,
do you think?

seb


* Jon Edwards <jon@pcgs.freeserve.co.uk> [010627 10:10]:
> I've had a problem with 1.1 breaking some of my skins too.
> 
> Don't forget that a lot of us love CMF because we can do so much with so
> little knowledge! To us, a "cvs diff" is black-magic!
> 
> One suggestion - perhaps when DC release a new version, they could include a
> list of "Skin Changes" - e.g. "We changed xyz-method in 123-folder to
> accomodate the underlying change to blah-blah"
> 
> Then we could see at a glance that if we had customised "xyz-method", we
> needed to re-visit it. I'm sure this info is around somewhere, but having it
> collected together in a nice simple way might help the less-knowledgable
> users?
> 
> Of course, that's not relevant to Chris' original problem. Sorry for
> side-tracking, Chris! :-)
> 
> Cheers, Jon
> 
> ----------------------------------------------
> Seb wrote -
> 
> 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.
> 

-- 

   [] j a m k i t 
           
        seb bacon
T:  020 7749 7218
F:  020 7739 8683
M:  07968 301 336
W: www.jamkit.com