-----BEGIN PGP SIGNED MESSAGE-----
Martijn Faassen wrote:
> Hanno Schlichting wrote:
>> Hi Martijn,
>> On Mon, May 3, 2010 at 2:03 PM, Martijn Faassen <faas...@startifact.com>
>>> Because my suggestions (besides the fork issue) as a ZTK
>>> user/contributor were scattered through the thread, here's a handy summary:
>> Thank you very much for your suggestions. I'm sure the release team
>> will pick these up, once we get to start actual discussions.
>> We have only started talking to each other last week and are slowly
>> bootstrapping. Please don't expect us to solve everything in a matter
>> of days.
> Why not? Why can't you solve things in a matter of days?
> The fork took 5 minutes. Does it really take more than saying, "okay,
> we're going to unfork", a few modifications to a buildout.cfg and
> figuring out a couple of test failures? I know it's hard to admit a
> mistake, but heck, it shouldn't have to take 4 months.
One issue with insta-updates to ztk.cfg is that ongoing development of a
package can be in real tension with the needs of ZTK consumers for
"stability" in the package set. E.g., I have updated
zope.testbrowser/trunk to use the new version of mechanize, but don't
know whether pulling that version into the ZTK proper is reasonable (in
fact, I decided to have the ZTK development buildout use a "stable"
branch for the meanwhile).
If you are a ZTK consumer, and would like to see the ZTK include a newer
version of one of its packages, then that need has to be balanced with
the needs of the "downstream" projects. In effect, the new "release
manager group" is supposed to represent the interests of Grok, Zope2,
and BlueBream in a shared definition of the ZTK "known good set."
Getting that nailed down into a version which works for all three is
*way* more important than picking up individual package changes.
Once a "ZTK 1.0" release is out and frozen, then we can look at opening
up the trunk to more rapid breakage^Wimprovements.
Tres Seaver +1 540-429-0999 tsea...@palladion.com
Palladion Software "Excellence by Design" http://palladion.com
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
-----END PGP SIGNATURE-----
Zope-Dev maillist - Zope-Dev@zope.org
** No cross posts or HTML encoding! **
(Related lists -