[Zope-dev] Another buildbot with the package trunks of the ZTK
I've added another buildbot that runs the ZTK tests against all the package trunks: http://buildbot.afpy.org This should allow to detect breakages earlier (before releasing packages) on the different versions of Python. The Python 3.1 slave is just there to remind us there's another task waiting ;) Christophe ___ Zope-Dev maillist - Zope-Dev@zope.org 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 )
Re: [Zope-dev] Another buildbot with the package trunks of the ZTK
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Christophe Combelles wrote: I've added another buildbot that runs the ZTK tests against all the package trunks: http://buildbot.afpy.org This should allow to detect breakages earlier (before releasing packages) on the different versions of Python. The Python 3.1 slave is just there to remind us there's another task waiting ;) I'm not sure that testing ZTK against the package trunks is quite the right thing: we have to be free to make changes to trunks while leaving the ZTK known good on older, stable versions: otherwise we might as well[ be releasing a monolithic tarball. For instance, there were proposals to release zope.component 4.0, with a bunch of potentially incompatible architectural changes: the ZTK would need to stick with older versions until after the whole set caught up with the new APIs / usage patterns. Tres. - -- === Tres Seaver +1 540-429-0999 tsea...@palladion.com Palladion Software Excellence by Designhttp://palladion.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkuT9+4ACgkQ+gerLs4ltQ6qVQCdGh/dy7m5oZgFNmEblbI+mK2U txIAn2pQFQ9InxANIIrQl8ymE+i5iM7Z =uxik -END PGP SIGNATURE- ___ Zope-Dev maillist - Zope-Dev@zope.org 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 )
Re: [Zope-dev] Another buildbot with the package trunks of the ZTK
On 2010-3-7 20:01, Tres Seaver wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Christophe Combelles wrote: I've added another buildbot that runs the ZTK tests against all the package trunks: http://buildbot.afpy.org This should allow to detect breakages earlier (before releasing packages) on the different versions of Python. The Python 3.1 slave is just there to remind us there's another task waiting ;) I'm not sure that testing ZTK against the package trunks is quite the right thing: we have to be free to make changes to trunks while leaving the ZTK known good on older, stable versions: otherwise we might as well[ be releasing a monolithic tarball. For instance, there were proposals to release zope.component 4.0, with a bunch of potentially incompatible architectural changes: the ZTK would need to stick with older versions until after the whole set caught up with the new APIs / usage patterns. Debian has fully automated that approach in its testing distribution. Perhaps something similar might be doable for the ZTK. Wichert.= -- Wichert Akkerman wich...@wiggy.net It is simple to make things. http://www.wiggy.net/ It is hard to make things simple. ___ Zope-Dev maillist - Zope-Dev@zope.org 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 )
Re: [Zope-dev] Another buildbot with the package trunks of the ZTK
On Sun, Mar 7, 2010 at 8:01 PM, Tres Seaver tsea...@palladion.com wrote: I'm not sure that testing ZTK against the package trunks is quite the right thing: we have to be free to make changes to trunks while leaving the ZTK known good on older, stable versions: otherwise we might as well[ be releasing a monolithic tarball. I think the term trunk is misleading here. The ztk.cfg [1] uses the mr.developer approach, which is based on a sources section. So there's is an explicit configuration for each package noting which SVN location is considered the source of the next release for that package. The buildbot uses this information and checks out each of these SVN locations. It just so happens that these all point to trunk at the moment. But as soon as we get some stability guarantee / feature freeze for the ZTK, some of the locations will need to change to appropriate maintenance branches. I think it is useful to get notified if changes to Subversion break the ZTK. One of the appropriate actions for the ZTK maintainers might then be to create a maintenance branch of a breaking package and opt-out of the new feature. That's at least the way we handle this in Plone :-) Hanno [1] http://svn.zope.org/zopetoolkit/trunk/ztk.cfg?view=markup ___ Zope-Dev maillist - Zope-Dev@zope.org 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 )
