[Zope-dev] Hanno, please update the ZTK

[Tres Seaver]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Martijn Faassen wrote:

> On Mon, May 3, 2010 at 7:48 PM, Lennart Regebro <regebro at gmail.com> wrote:
>> On Mon, May 3, 2010 at 18:09, Martijn Faassen <faassen at startifact.com> wrote:
>>> Hanno is making releases of packages in the ZTK. So it's not just
>>> Hanno's waste of time; it's mine too.
>> Obviously he shouldn't hurt the main ZTK in any way. That would be a
>> problem (even if i missed this incident completely and hence dn't
>> understand what or how things broke). But I think the fork in itself
>> is a red herring.
> 
> I spent months trying to get everybody together and there was a fork
> because we had a disagreement in december. Instead of working together
> and working with me, people just forked. That really hurt. With that
> lack of commitment to the ZTK, I didn't feel inclined to be committed
> to it either.

I expect to see Zope2 trunk move to using the ZTK versions list quite
soon:  more than that, I'm willing to to the work to see that it happens
(verifying that everything passes / works with the change), and give
Hanno the patch to make it so, assuming he doesn't get around to it.

> I haven't seen a plausible reason why the fork should be necessary. It
> just uses some updated versions of packages (mostly bugfix releases)
> that would have been updated in the ZTK as well if people had bothered
> to update them.

If the release manager group gets consensus quickly on how their
projects' interests align in the ZTK, then the fork can go away.  Until
then, pushing changes into the ZTK without consulting those projects'
needs is premature.



Tres.
- --
===================================================================
Tres Seaver          +1 540-429-0999          tseaver at 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

iEYEARECAAYFAkvfEdsACgkQ+gerLs4ltQ5lIACgwyWGEHhFRXfBVng1peqKGlVJ
vbIAoLiuAo2sgmT7WxgjuEoNy9mbOBz2
=EMgZ
-----END PGP SIGNATURE-----