-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Stephan Richter wrote: > On Friday 08 September 2006 04:12, yuppie wrote: >> Are there good reasons why these changes were not backported? >> >> I volunteer to backport some fixes I'm missing in Zope 3.2, but that's >> no general solution for keeping the current stable branch maintained. > > The short answer is: We are a bit sloppy. I always develop against the trunk, > so when I fix an issue, I do not event think about porting it back to another > release, other when one is imminent, like Zope 3.3 now. I think most other > Zope 3 developers are the same.
I consider this practice unacceptable for work on an allegedly ready-for-production package. The Zope Development Process document  states: When you check in a bug fix, you almost always need to: * Check in the fix on the current release branch * Note the fix in the /doc/CHANGES.txt on the current release branch * Merge the fix to the trunk to be sure its fixed for the next feature release Only "feature work" should be done primarily on the trunk.  http://www.zope.org/DevHome/Subversion/ZopeDevelopmentProcess Tres. - -- =================================================================== Tres Seaver +1 202-558-7113 [EMAIL PROTECTED] Palladion Software "Excellence by Design" http://palladion.com -----BEGIN PGP SIGNATURE----- Version: GnuPG v220.127.116.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFFAbKx+gerLs4ltQ4RAt6SAJ9fYC0322cIzW0NeHMe+EGT+RSqsgCdHH7T t2Um2o27+28g6mMLDZiI5XU= =l+RS -----END PGP SIGNATURE----- _______________________________________________ Zope3-dev mailing list Zope3firstname.lastname@example.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com