Archetypes 1.3: NEVER CHANGE BEHAVIOUR + how to deal with changes in >1.3
"Jens W. Klein" <jens-/[email protected]>
| Newsgroups | gmane.comp.web.zope.plone.archetypes.devel |
|---|---|
| Organization | BlueDynamics Tyrol - Klein & Partner KEG |
| Message-ID | <[email protected]> |
Sorry for the loud topic. But please: Archetypes 1.3 is in maintanance
mode.
Every fix must not change current behaviour, even if its odd. Current code
relying on Archetypes 1.3 must not break after update, even if it depends
on odd behaviour.
Expection: Security related fixes.
Plan for smaller behaviour changes:
* change it in 1.4 and trunk (1.5) in a sane way.
* mark odd behaviour deprecated in 1.3
Plan for intrusive changes:
* dont touch 1.3,
* discuss on the lists and/or in IRC about it,
* write a PLIP for very intrusive changes,
* mark old behaviour in 1.4 deprecated, introduce new behaviour,
* remove old behaviour in trunk (1.5) and have only the new way.
thx for reading and understanding
Jensens
(Archetypes QA & release management)
--
Jens W. Klein, WEB APPLICATIONS: ZOPE, PLONE - MDA, SOA
BlueDynamics Tyrol production: concept, development, design
Klein & Partner KEG consulting: analysis, coaching, training
http://www.bluedynamics.com management: projects, process, community
-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642