tseaver at palladion
May 18, 2012, 1:21 PM
Post #1 of 1
(160 views)
Permalink
|
|
Moving zTK 1.0 and 1.1 off of trunk checkouts
|
|
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
I created a bunch of SVN churn today, setting up "stable" branches for
use by the ZTK 1.0 and 1.1 development modes.. We've talked about it in
the past, but I realized that keeping those trees using trunk checkouts,
even partially, was too painful: the straw which broke this camel's back
was realizing that fixing deprecation warnings (about
zope.interface.implements etc.) might break the bots, because they would
pull in code which was intended only for Python 2.6 and later.
I believe that this state (the released ZTK trees depending on "release
branches", rather than trunks), is actually where we wanted to be all
along, only it seemed too much effort at the time.
Tres.
- --
===================================================================
Tres Seaver +1 540-429-0999 tseaver [at] palladion
Palladion Software "Excellence by Design" http://palladion.com
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAk+2rzMACgkQ+gerLs4ltQ7xogCgx8LTHVUaDOhuzlxKuz+rUHgf
6IQAoJblodMaCnMHP4gokeENkJ2bRvGM
=Cx0f
-----END PGP SIGNATURE-----
_______________________________________________
Zope-Dev maillist - Zope-Dev [at] zope
https://mail.zope.org/mailman/listinfo/zope-dev
** No cross posts or HTML encoding! **
(Related lists -
https://mail.zope.org/mailman/listinfo/zope-announce
https://mail.zope.org/mailman/listinfo/zope )
|
