Re: Archetypes 1.3: NEVER CHANGE BEHAVIOUR + how to deal with changes in >1.3
Sidnei da Silva <sidnei-/awGbKECNgO/3pe1ocb+swC/[email protected]>
| Newsgroups | gmane.comp.web.zope.plone.archetypes.devel |
|---|---|
| Message-ID | <20060223124615.GI4398@cotia> |
On Thu, Feb 23, 2006 at 10:21:46AM +0100, Jens W. Klein wrote: | 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. Jens, I think you missed the point on my fix: 1. It has tests, which you plain broke! 2. It helps the user not to commit an error that would cause lots of pain. Someone just spent 5 hours trying to understand why a field would not be saved. 3. It was never a intended feature to start with, and I can't see a case where someone would use it except for a real copy-and-paste error or a typo. So, by all means it's a bugfix. If you don't agree with that, at least fix the tests. Shame on you for making the rules and not living by them. -- Sidnei da Silva Enfold Systems, LLC. http://enfoldsystems.com ------------------------------------------------------- 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