Re: [Zope-dev] Developer meeting on IRC in #zope today at 15:00 UTC
Hi, On 06/08/2010 09:18 AM, Christian Theune wrote: Hi, it's time again. See the attached agenda. Better late then never, here's the info from last weeks meeting: - ZTK 3.4.1 seems to be done (RC needs to be turned into final) - Funding for Windows VM is there, Adam is building a tool for automatically building binary eggs when packages are released - On the meta side: the last weeks had fewer participants than before which could be due to the topics stalling with maintenance tasks. We'll try to give better opportunity to bring up topics by inviting for the meeting already on Monday and making it clear that we don't have to stick with the topics from the draft agenda. The full summary will be available here: http://docs.zope.org/zopetoolkit/zope-dev/zope-dev-20100608.html Cheers, Christian -- Christian Theune · c...@gocept.com gocept gmbh co. kg · forsterstraße 29 · 06112 halle (saale) · germany http://gocept.com · tel +49 345 1229889 0 · fax +49 345 1229889 1 Zope and Plone consulting and development ___ 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 )
[Zope-dev] Developer meeting in IRC tomorrow at 15:00 UTC
Hi, I'd like to invite to the next developer meeting on IRC (#z...@freenode) which happens tomorrow at 15:00 UTC. If you have anything you'd like to talk about, please feel free too send a topic suggestion in response to this post: it's really intended to be a platform for anyone of us to get itches scratched, so I want *you* to speak up. :) If nothing else comes up, we'll keep following up on the test runners and how to get some metrics for bug days. Christian -- Christian Theune · c...@gocept.com gocept gmbh co. kg · forsterstraße 29 · 06112 halle (saale) · germany http://gocept.com · tel +49 345 1229889 0 · fax +49 345 1229889 1 Zope and Plone consulting and development ___ 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 )
[Zope-dev] Zope Tests: 36 OK, 10 Failed
Summary of messages to the zope-tests list. Period Sun Jun 13 12:00:00 2010 UTC to Mon Jun 14 12:00:00 2010 UTC. There were 46 messages: 6 from Zope Tests, 12 from ccomb at free.fr, 1 from ct at gocept.com, 27 from jdriessen at thehealthagency.com. Test failures - Subject: FAILED: Repository policy check found errors in 470 projects From: ct at gocept.com Date: Sun Jun 13 21:13:08 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-June/015237.html Subject: FAILED : BlueBream template / Python2.6.4 32bit linux From: ccomb at free.fr Date: Sun Jun 13 22:00:55 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-June/015245.html Subject: FAILED : BlueBream template / Python2.5.2 32bit linux From: ccomb at free.fr Date: Sun Jun 13 22:00:57 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-June/015246.html Subject: FAILED : BlueBream template / Python2.7b2 32bit linux From: ccomb at free.fr Date: Sun Jun 13 22:00:57 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-June/015247.html Subject: FAILED : ZTK 1.0dev / Python2.4.6 Linux 32bit From: ccomb at free.fr Date: Sun Jun 13 23:33:08 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-June/015248.html Subject: FAILED : ZTK 1.0dev / Python2.5.2 Linux 32bit From: ccomb at free.fr Date: Sun Jun 13 23:34:21 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-June/015249.html Subject: FAILED : ZTK 1.0dev / Python2.6.4 Linux 32bit From: ccomb at free.fr Date: Sun Jun 13 23:34:28 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-June/015250.html Subject: FAILED : Zope 3.4.1 KGS / Python2.4.6 32bit linux From: ccomb at free.fr Date: Mon Jun 14 00:00:16 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-June/015251.html Subject: FAILED : Zope Buildbot / ztk_win slave-win From: jdriessen at thehealthagency.com Date: Mon Jun 14 02:31:52 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-June/015256.html Subject: FAILED : Zope Buildbot / ztk_win slave-win From: jdriessen at thehealthagency.com Date: Mon Jun 14 07:25:30 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-June/015262.html Tests passed OK --- Subject: OK : Zope Buildbot / zope2.12 slave-osx From: jdriessen at thehealthagency.com Date: Sun Jun 13 08:48:01 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-June/015218.html Subject: OK : Zope Buildbot / zope2 slave-osx From: jdriessen at thehealthagency.com Date: Sun Jun 13 08:55:36 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-June/015219.html Subject: OK : Zope Buildbot / ztk slave-osx From: jdriessen at thehealthagency.com Date: Sun Jun 13 09:24:43 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-June/015220.html Subject: OK : Zope Buildbot / zope2.12 slave-osx From: jdriessen at thehealthagency.com Date: Sun Jun 13 09:33:52 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-June/015221.html Subject: OK : Zope Buildbot / zope2.12 slave-ubuntu64 From: jdriessen at thehealthagency.com Date: Sun Jun 13 11:55:09 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-June/015222.html Subject: OK : Zope Buildbot / zope2.12 slave-ubuntu32 From: jdriessen at thehealthagency.com Date: Sun Jun 13 11:55:17 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-June/015223.html Subject: OK : Zope Buildbot / zope2 slave-ubuntu64 From: jdriessen at thehealthagency.com Date: Sun Jun 13 11:57:04 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-June/015224.html Subject: OK : Zope Buildbot / zope2 slave-ubuntu32 From: jdriessen at thehealthagency.com Date: Sun Jun 13 11:57:18 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-June/015225.html Subject: OK : Zope Buildbot / zope2.12 slave-osx From: jdriessen at thehealthagency.com Date: Sun Jun 13 12:02:01 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-June/015226.html Subject: OK : Zope Buildbot / zope2 slave-osx From: jdriessen at thehealthagency.com Date: Sun Jun 13 12:09:32 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-June/015227.html Subject: OK : Zope Buildbot / zope2.12 slave-ubuntu64 From: jdriessen at thehealthagency.com Date: Sun Jun 13 12:55:11 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-June/015228.html Subject: OK : Zope Buildbot / zope2.12 slave-ubuntu32 From: jdriessen at thehealthagency.com Date: Sun Jun 13 12:55:16 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-June/015229.html Subject: OK : Zope Buildbot / zope2.12 slave-osx From: jdriessen at thehealthagency.com Date: Sun Jun 13 13:01:45 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-June/015230.html Subject: OK : Zope Buildbot / zope2.12 slave-ubuntu64 From: jdriessen at thehealthagency.com Date: Sun Jun 13 13:55:08 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-June/015231.html Subject: OK : Zope Buildbot / zope2.12 slave-ubuntu32 From:
Re: [Zope-dev] Zope Tests: 36 OK, 10 Failed
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Subject: FAILED : ZTK 1.0dev / Python2.4.6 Linux 32bit From: ccomb at free.fr Date: Sun Jun 13 23:33:08 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-June/015248.html Subject: FAILED : ZTK 1.0dev / Python2.5.2 Linux 32bit From: ccomb at free.fr Date: Sun Jun 13 23:34:21 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-June/015249.html Subject: FAILED : ZTK 1.0dev / Python2.6.4 Linux 32bit From: ccomb at free.fr Date: Sun Jun 13 23:34:28 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-June/015250.html These apparent test failures are due to the following problem in the buildout step, which did not cause the step to fail: - $ -- Installing test-zopeapp. Generated script '/home/ccomb/slave3/Python2.6.4-Linux-32bit/build/bin/test-zopeapp-zope.app.locales'. Generated script '/home/ccomb/slave3/Python2.6.4-Linux-32bit/build/bin/test-zopeapp-zope.app.folder'. Generated script '/home/ccomb/slave3/Python2.6.4-Linux-32bit/build/bin/test-zopeapp-zope.app.error'. Generated script '/home/ccomb/slave3/Python2.6.4-Linux-32bit/build/bin/test-zopeapp-zope.app.publisher'. Generated script '/home/ccomb/slave3/Python2.6.4-Linux-32bit/build/bin/test-zopeapp-zope.app.principalannotation'. Generated script '/home/ccomb/slave3/Python2.6.4-Linux-32bit/build/bin/test-zopeapp-zope.app.server'. Generated script '/home/ccomb/slave3/Python2.6.4-Linux-32bit/build/bin/test-zopeapp-zope.app.http'. Generated script '/home/ccomb/slave3/Python2.6.4-Linux-32bit/build/bin/test-zopeapp-zope.app.dependable'. Generated script '/home/ccomb/slave3/Python2.6.4-Linux-32bit/build/bin/test-zopeapp-zope.app.broken'. Generated script '/home/ccomb/slave3/Python2.6.4-Linux-32bit/build/bin/test-zopeapp-zope.app.locking'. Generated script '/home/ccomb/slave3/Python2.6.4-Linux-32bit/build/bin/test-zopeapp-zope.app.pagetemplate'. Generated script '/home/ccomb/slave3/Python2.6.4-Linux-32bit/build/bin/test-zopeapp-zope.app.form'. Generated script '/home/ccomb/slave3/Python2.6.4-Linux-32bit/build/bin/test-zopeapp-zope.app.intid'. Generated script '/home/ccomb/slave3/Python2.6.4-Linux-32bit/build/bin/test-zopeapp-zope.app.container'. Generated script '/home/ccomb/slave3/Python2.6.4-Linux-32bit/build/bin/test-zopeapp-zope.app.interpreter'. Generated script '/home/ccomb/slave3/Python2.6.4-Linux-32bit/build/bin/test-zopeapp-zope.app.interface'. Generated script '/home/ccomb/slave3/Python2.6.4-Linux-32bit/build/bin/test-zopeapp-zope.app.basicskin'. Generated script '/home/ccomb/slave3/Python2.6.4-Linux-32bit/build/bin/test-zopeapp-zope.app.publication'. Generated script '/home/ccomb/slave3/Python2.6.4-Linux-32bit/build/bin/test-zopeapp-zope.app.wsgi'. Generated script '/home/ccomb/slave3/Python2.6.4-Linux-32bit/build/bin/test-zopeapp-zope.app.testing'. Generated script '/home/ccomb/slave3/Python2.6.4-Linux-32bit/build/bin/test-zopeapp-zope.app.zopeappgenerations'. Generated script '/home/ccomb/slave3/Python2.6.4-Linux-32bit/build/bin/test-zopeapp-zope.app.ftp'. Generated script '/home/ccomb/slave3/Python2.6.4-Linux-32bit/build/bin/test-zopeapp-zope.app.localpermission'. Generated script '/home/ccomb/slave3/Python2.6.4-Linux-32bit/build/bin/test-zopeapp-zope.app.schema'. Generated script '/home/ccomb/slave3/Python2.6.4-Linux-32bit/build/bin/test-zopeapp-zope.app.tree'. While: Installing test-zopeapp. Getting distribution for 'zope.preference'. Error: Picked: zope.preference = 3.8.0 program finished with exit code 0 - $ -- That egg needs to be called out in the zopeapp.cfg file, I think (wasn't it just spun out of zope.app.preference?) 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 iEYEARECAAYFAkwWMVcACgkQ+gerLs4ltQ6CvgCgqEB0cxwOqTkbVnTu3vrEe5u6 +2MAnRZGZBGe+etJ9jDUivYVXDDb7vMI =hWo7 -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] Zope 2.13 - next steps
hello, On 13/06/2010 Hanno Schlichting wrote: On Sat, Jun 12, 2010 at 10:45 PM, Jonas Meurer jo...@freesources.org wrote: another build system would be magnificent :-) the new build system in zope2.12 makes it hard/impossible to distribute zope2 binaries within linux/*bsd/hurd/... distributions. so far no distribution i know contains zope2.12, and the most obvious reason is the new build system. In the Zope community we have decided to stop maintaining our own build infrastructure, as we simply do not have the resources to do so. Getting this right in a cross platform manner including Windows is no small task and there's no general open-source build infrastructure that provides this. Therefor we have decided to go with a language specific build infrastructure in the form of distutils and its extension setuptools / distribute. Personally I think this has been the right choice for us and has triggered a new interest in distutils. distutils2 is the latest offspring of that effort and is making good progress. Better integration into operating system package managers is one of the main focus areas of that effort. While solving these issues on the Python language level takes more time, it ultimately is the better approach. thus i suggest to either provide monolithic tarballs which do contain the debendencies, or change release policy for the dependencies to not break backwards compability with every minor release. I consider packaging up individual Python distributions as individual system packages as a flawed approach. The specific dependencies on exact versions of these distributions for any given application are too diverse for this approach to make much sense. The number of releases is so frequent and the stability requirements so different from system packages, that this just isn't a good match. If I were to package anything as a system package, then it would be one big package for something like CMFDefault, Plone or Zenoss as an application or one package for a custom developed application. zc.sourcerelease is one approach to help in this task for a zc.buildout based application. first, thanks for clarifying. did i get you right, that for the future, monolithic source releases of zope2 are planned again once the dust has settled? and second, does documentation exist which explains how to craft a monolithic tarball with zc.sourcerelease in order to build zope2.12 without network access? i still didn't get the picture regarding buildout, and thus don't understand zc.sourcerelease either :-/ greetings, jonas signature.asc Description: Digital 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] Zope 2.13 - next steps
Hi. On Mon, Jun 14, 2010 at 4:16 PM, Jonas Meurer jo...@freesources.org wrote: first, thanks for clarifying. did i get you right, that for the future, monolithic source releases of zope2 are planned again once the dust has settled? No. There is currently no monolithic released planned at all. Only if someone does all the work of automating such a release, engage with the community to discuss the approach and is willing to adjust to community feedback, only then I as the release manager might make those steps part of the release process. I'm not aware of anyone who has shown even remote interest in this task. and second, does documentation exist which explains how to craft a monolithic tarball with zc.sourcerelease in order to build zope2.12 without network access? i still didn't get the picture regarding buildout, and thus don't understand zc.sourcerelease either :-/ I'm not aware of any specific documentation. www.buildout.org and the distutils-sig mailing list [1] would be the appropriate places to look. Hanno [1] http://mail.python.org/mailman/listinfo/distutils-sig ___ 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] Zope 2.13 - next steps
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Jonas Meurer wrote: hello, On 13/06/2010 Hanno Schlichting wrote: On Sat, Jun 12, 2010 at 10:45 PM, Jonas Meurer jo...@freesources.org wrote: another build system would be magnificent :-) the new build system in zope2.12 makes it hard/impossible to distribute zope2 binaries within linux/*bsd/hurd/... distributions. so far no distribution i know contains zope2.12, and the most obvious reason is the new build system. In the Zope community we have decided to stop maintaining our own build infrastructure, as we simply do not have the resources to do so. Getting this right in a cross platform manner including Windows is no small task and there's no general open-source build infrastructure that provides this. Therefor we have decided to go with a language specific build infrastructure in the form of distutils and its extension setuptools / distribute. Personally I think this has been the right choice for us and has triggered a new interest in distutils. distutils2 is the latest offspring of that effort and is making good progress. Better integration into operating system package managers is one of the main focus areas of that effort. While solving these issues on the Python language level takes more time, it ultimately is the better approach. thus i suggest to either provide monolithic tarballs which do contain the debendencies, or change release policy for the dependencies to not break backwards compability with every minor release. I consider packaging up individual Python distributions as individual system packages as a flawed approach. The specific dependencies on exact versions of these distributions for any given application are too diverse for this approach to make much sense. The number of releases is so frequent and the stability requirements so different from system packages, that this just isn't a good match. If I were to package anything as a system package, then it would be one big package for something like CMFDefault, Plone or Zenoss as an application or one package for a custom developed application. zc.sourcerelease is one approach to help in this task for a zc.buildout based application. first, thanks for clarifying. did i get you right, that for the future, monolithic source releases of zope2 are planned again once the dust has settled? No such plans exist. Your desire for a network-free install needs to be backed up by some work, as none of the core developers have that goal. and second, does documentation exist which explains how to craft a monolithic tarball with zc.sourcerelease in order to build zope2.12 without network access? i still didn't get the picture regarding buildout, and thus don't understand zc.sourcerelease either :-/ A casual browse of the zc.sourcerelease page on PyPI yields: http://pypi.python.org/pypi/zc.sourcerelease#creating-source-releases-from-buildouts 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 iEYEARECAAYFAkwWQzsACgkQ+gerLs4ltQ5oTwCeOGZHOldy6fOZblczsbZ9rJtq iKIAn0lzIXtgFqb2jrPu1yo7RE4KqzN7 =Hsxl -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] Zope 2.13 - next steps
Hi there, thanks to all of you for the feedback. Given the general agreement to the plan, I'm going to release a first alpha on Friday June 25. More alpha releases will follow depending on the changes that go into the codebase. But I expect them on a roughly 3-4 weeks basis. If the code stays as stable as it is and no new major features come in, I expect to release a first beta in early September, in time for the German Zope User Group conference. The concrete plan up to the final will be decided once we get a beta out of the door. Thanks all, Hanno On Sat, Jun 12, 2010 at 8:58 PM, Hanno Schlichting ha...@hannosch.eu wrote: Aim for having a Zope 2.13 release in time for Plone 4.1, get a first alpha release out by the end of the month or early July. We can have more alpha releases during the summer, a beta probably around the zope-dev summit / German Zope User Group conference in early September. ___ 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 )
