Re: [Zope-dev] Retiring the Zope SVN trunk!
Andreas Jung wrote: > On 03.02.2009 13:56 Uhr, Hanno Schlichting wrote: >> It becomes somewhat hard and annoying to keep the old full Zope trunk >> tree based on externals in sync with the Zope2 buildout and its KGS >> definition and it seems I failed yesterday. > >> I'd suggest we reorganize the Zope trunk and replace it by the current >> buildout. As part of that we can move the code that has been moved to >> its own projects like Acquisition and DateTime out of the main tree. > >> I'd volunteer to do this work if nobody objects. I had time to work on this on our Berlinale Sprint and this is now done! I marked the old Zope2.buildout area as retired after moving the code, so we don't confuse people anymore with two locations doing the same. Hanno ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Retiring the Zope SVN trunk? was: Re: Zope Tests: 6 OK, 2 Failed
On Tue, Feb 3, 2009 at 19:44, Hanno Schlichting wrote: > It would mean buildout becomes a requirement for the development of > Zope2 itself. Oh, +1 to that. > > For the devlopment with or on top of Zope2 any system that can deal with > normal Python distributions would work. In addition the plan is to > release at least for Zope 2.12 an old-style tarball release in the same > way all releases up to 2.11 have been handled. > > Hanno > > ___ > Zope-Dev maillist - Zope-Dev@zope.org > http://mail.zope.org/mailman/listinfo/zope-dev > ** No cross posts or HTML encoding! ** > (Related lists - > http://mail.zope.org/mailman/listinfo/zope-announce > http://mail.zope.org/mailman/listinfo/zope ) > -- Lennart Regebro: Zope and Plone consulting. http://www.colliberty.com/ +33 661 58 14 64 ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Retiring the Zope SVN trunk? was: Re: Zope Tests: 6 OK, 2 Failed
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 03.02.2009 13:56 Uhr, Hanno Schlichting wrote: > Zope Tests Summarizer wrote: >> Summary of messages to the zope-tests list. >> Period Mon Feb 2 12:00:00 2009 UTC to Tue Feb 3 12:00:00 2009 UTC. >> There were 8 messages: 8 from Zope Tests. >> >> Test failures >> - >> >> Subject: FAILED (failures=7) : Zope-trunk Python-2.4.5 : Linux >> From: Zope Tests >> Date: Mon Feb 2 20:50:11 EST 2009 >> URL: http://mail.zope.org/pipermail/zope-tests/2009-February/011003.html >> >> Subject: FAILED (failures=9) : Zope-trunk Python-2.5.4 : Linux >> From: Zope Tests >> Date: Mon Feb 2 20:51:41 EST 2009 >> URL: http://mail.zope.org/pipermail/zope-tests/2009-February/011004.html > > It becomes somewhat hard and annoying to keep the old full Zope trunk > tree based on externals in sync with the Zope2 buildout and its KGS > definition and it seems I failed yesterday. > > I'd suggest we reorganize the Zope trunk and replace it by the current > buildout. As part of that we can move the code that has been moved to > its own projects like Acquisition and DateTime out of the main tree. > > I'd volunteer to do this work if nobody objects. I am fine with giving up the current Zope 2 SVN branch. Keeping it in sync with the Z3 packages is already hard enough - so a single source of complexity is enough :) > > Stefan checked in a new alltests.cfg into the buildout, that lets him > run the tests for all direct dependencies of Zope2 in much the same way > as we did run all tests for the full package tree before. So we > shouldn't loose test coverage of the entire Zope2 release. Thanks Stefan! Andreas -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkmJN5YACgkQCJIWIbr9KYxyzgCgrM5NaCX0jzu+JZErUsTYbvHR l6oAoKcAW8v9nPB6zvNDi+zc3JZ4/QpP =paCm -END PGP SIGNATURE- begin:vcard fn:Andreas Jung n:Jung;Andreas org:ZOPYX Ltd. & Co. KG adr;quoted-printable:;;Charlottenstr. 37/1;T=C3=BCbingen;;72070;Germany email;internet:i...@zopyx.com title:CEO tel;work:+49-7071-793376 tel;fax:+49-7071-7936840 tel;home:+49-7071-793257 x-mozilla-html:FALSE url:www.zopyx.com version:2.1 end:vcard ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Retiring the Zope SVN trunk? was: Re: Zope Tests: 6 OK, 2 Failed
I don't think you faired that badly. ;-) One obvious problem is the removal of the 'defaultSkin' directive, which is still in use by CMFDefault. The rest looks harmless. I am not opposed to ditching the trunk, but I don't think keeping it in sync (if only for a transition period) is impossible either. Stefan On 03.02.2009, at 13:56, Hanno Schlichting wrote: > It becomes somewhat hard and annoying to keep the old full Zope trunk > tree based on externals in sync with the Zope2 buildout and its KGS > definition and it seems I failed yesterday. > > I'd suggest we reorganize the Zope trunk and replace it by the current > buildout. As part of that we can move the code that has been moved to > its own projects like Acquisition and DateTime out of the main tree. > > I'd volunteer to do this work if nobody objects. ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Retiring the Zope SVN trunk? was: Re: Zope Tests: 6 OK, 2 Failed
Lennart Regebro wrote: > On Tue, Feb 3, 2009 at 13:56, Hanno Schlichting wrote: >> It becomes somewhat hard and annoying to keep the old full Zope trunk >> tree based on externals in sync with the Zope2 buildout and its KGS >> definition and it seems I failed yesterday. >> >> I'd suggest we reorganize the Zope trunk and replace it by the current >> buildout. As part of that we can move the code that has been moved to >> its own projects like Acquisition and DateTime out of the main tree. > > Would that mean that 2.12 becomes buildout-only? Not that I mind, I > use buildouts all the time anyway. Maybe that's the plan anyhow? It would mean buildout becomes a requirement for the development of Zope2 itself. For the devlopment with or on top of Zope2 any system that can deal with normal Python distributions would work. In addition the plan is to release at least for Zope 2.12 an old-style tarball release in the same way all releases up to 2.11 have been handled. Hanno ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Retiring the Zope SVN trunk? was: Re: Zope Tests: 6 OK, 2 Failed
On Tue, Feb 3, 2009 at 13:56, Hanno Schlichting wrote: > It becomes somewhat hard and annoying to keep the old full Zope trunk > tree based on externals in sync with the Zope2 buildout and its KGS > definition and it seems I failed yesterday. > > I'd suggest we reorganize the Zope trunk and replace it by the current > buildout. As part of that we can move the code that has been moved to > its own projects like Acquisition and DateTime out of the main tree. Would that mean that 2.12 becomes buildout-only? Not that I mind, I use buildouts all the time anyway. Maybe that's the plan anyhow? -- Lennart Regebro: Zope and Plone consulting. http://www.colliberty.com/ +33 661 58 14 64 ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
