-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Lennart Regebro wrote: > On Nov 10, 2007 5:12 AM, Tres Seaver <[EMAIL PROTECTED]> wrote: >> If the REST stuff depended on unreleased versions of upstream packages, >> then it should not have been merged until those packages were released >> in an acceptable (non-snapshot) form. > > That's a good sentiment and I agre with it in practice. But Grok is > still in < 1.0 status so I don't eally think it's a big issue. Waiting > for the zope packages to stabilize would only have delayed the > progress of Grok at this moment, and the amount of people using Grok > in production environments is and should be low as it's still in > experimental form.
The first point is that whoever put the '.dev-r###' eggs out on a public server made an error: if you don't have the time to do proper release management, then don't release at all. We've spent more effort on the argument now than it would have taken to do the releases. That said, if merging a feature branch requires picking up unreleased packages, then the merge should not be done, period: merging in that state is like merging with failing unit tests. Tres. - -- =================================================================== Tres Seaver +1 540-429-0999 [EMAIL PROTECTED] Palladion Software "Excellence by Design" http://palladion.com -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFHNa3B+gerLs4ltQ4RAnqwAJ42iOMN36WusKLCBykn8N5ttT7/vACfUkhj p/7FV6Ve19Crb7S7i/1pWAQ= =eXCq -----END PGP SIGNATURE----- _______________________________________________ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
