[Zope-dev] [SVN] Zope trunk - merged stuff for Zope 2.11 released
The Zope trunk has been updated in preparation for the next Zope 2.11 release. It contains now the Zope 3.4 codebase and uses ZODB 3.8 with BLOB support. We will start with the Zope 2.11 beta cycle shortly after Zope 3.4 goes beta. Are any major developments pending for Zope 2.11? I only know of some Five exception work (Martijn Faasen). Andreas pgpDpVCUzFMep.pgp Description: PGP signature ___ 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 )
[Zope-dev] Re: State of 'Zope211-3.4-integration' branch
--On 26. Juni 2007 15:00:23 +0200 Philipp von Weitershausen <[EMAIL PROTECTED]> wrote: Don't we need a released 3.3.x? Right, right. I meant to say: What's the matter with the latest Zope 3.3.x release? Are there any bugfixes in the Zope 3.3 branch that Zope 2 is waiting for? Otherwise we can just release with the latest Zope 3.3.x... There is basically nothing with the 3.2 and 3.3 branches. I just don't know about all details of the current 3.X development in order to feel comfortable enough to create a Zope 2 release from the current branches without having the OK from the related release masters. I could make (internal) tags on my own but this should be done in general by the responsible release manager (just for release safety) :-) Andreas pgpx9X1eIFW7p.pgp Description: PGP signature ___ 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 )
[Zope-dev] Re: SVN problems merging the Zope 2.11 integration branch
Andreas Jung wrote: Cdoc/CHANGES.txt Ulib/python/Products/Five/i18n.zcml Ulib/python/Products/Five/event.zcml Ulib/python/Products/Five/meta.zcml Ulib/python/Products/Five/form/tests/forms.txt Dlib/python/Products/Transience/tests/testCounters.py Ulib/python/Products/PageTemplates/www/ptEdit.zpt Ulib/python/ZPublisher/HTTPRequest.py Ulib/python/ZPublisher/tests/testHTTPRequest.py Ulib/python/tempstorage/tests/testTemporaryStorage.py U lib/python/zope/app U lib/python/zope C lib/python You're getting a conflict here on the externals because you recently stitched RestrictedPython 3.4.1 into the trunk. I suggest resolving this manually. Usetup.py U utilities updates only some files. Well, perhaps only those few files were changed in the branch? No svn:externals are being updated. That is hard to believe. The 'zope' and 'zope/app' externals should be ok. -- http://worldcookery.com -- Professional Zope documentation and training ___ 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 )
[Zope-dev] Re: State of 'Zope211-3.4-integration' branch
On 26 Jun 2007, at 14:56 , Tres Seaver wrote: Philipp von Weitershausen wrote: On 25 Jun 2007, at 12:09 , Andreas Jung wrote: --On 25. Juni 2007 10:13:44 +0200 Andreas Zeidler <[EMAIL PROTECTED]> wrote: On Jun 25, 2007, at 10:05 AM, Philipp von Weitershausen wrote: true, but i think philipp was only asking about 2.11 for the time being. i agree the fix should be backported, though. i'd even volunteer to do it, if nobody else wants to... :) That would be great, especially since we're on the verge of new maintenance releases for 2.9 and 2.10. when are they due? unfortunately i won't be able to do the backporting before thursday, since we've got a project release on wednesday... I defer the 2.9/2.10 for some days until I know how we should deal with the current state of the Zope 3.2/3.3 branches. I realize you're waiting for a "release" of the Zope 3.2 branch to make another Zope 2.9.x release. I meant to respond earlier, apologies for the delay. I have no intentions of making another Zope 3.2 release (unless somebody really wants me to, in which case I'll do it). So for all I care, you can just tag Zope 3.2.3, put that in the external of Zope 2.9 and be done with it. Please do the rest of the release managment before making that tag: - Update the changelog to indicate the release date, SVN tag, etc. (on the branch before copying!) - Update any version ID in the configure script. Then make the tag. Yeah, thanks for the reminder. What's the matter with the Zope 3.3 branch then? Don't we need a released 3.3.x? Right, right. I meant to say: What's the matter with the latest Zope 3.3.x release? Are there any bugfixes in the Zope 3.3 branch that Zope 2 is waiting for? Otherwise we can just release with the latest Zope 3.3.x... ___ 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 )
[Zope-dev] Re: State of 'Zope211-3.4-integration' branch
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Philipp von Weitershausen wrote: > On 25 Jun 2007, at 12:09 , Andreas Jung wrote: >> --On 25. Juni 2007 10:13:44 +0200 Andreas Zeidler <[EMAIL PROTECTED]> wrote: >> >>> On Jun 25, 2007, at 10:05 AM, Philipp von Weitershausen wrote: > true, but i think philipp was only asking about 2.11 for the time > being. i agree the fix should be backported, though. i'd even > volunteer to do it, if nobody else wants to... :) That would be great, especially since we're on the verge of new maintenance releases for 2.9 and 2.10. >>> when are they due? unfortunately i won't be able to do the >>> backporting >>> before thursday, since we've got a project release on wednesday... >> I defer the 2.9/2.10 for some days until I know how we should deal >> with the >> current state of the Zope 3.2/3.3 branches. > > I realize you're waiting for a "release" of the Zope 3.2 branch to > make another Zope 2.9.x release. I meant to respond earlier, > apologies for the delay. I have no intentions of making another Zope > 3.2 release (unless somebody really wants me to, in which case I'll > do it). So for all I care, you can just tag Zope 3.2.3, put that in > the external of Zope 2.9 and be done with it. Please do the rest of the release managment before making that tag: - Update the changelog to indicate the release date, SVN tag, etc. (on the branch before copying!) - Update any version ID in the configure script. Then make the tag. > What's the matter with the Zope 3.3 branch then? Don't we need a released 3.3.x? Tres. - -- === Tres Seaver +1 540-429-0999 [EMAIL PROTECTED] Palladion Software "Excellence by Design"http://palladion.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFGgQzy+gerLs4ltQ4RAtOxAKCW0G62p+AKqM+5ixUvPJABaAaqVgCghg+Y 0U5Ns+Sx9MpFxlpsvsTc5Ng= =+O+G -END PGP SIGNATURE- ___ 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 )
[Zope-dev] Zope Tests: 5 OK
Summary of messages to the zope-tests list. Period Mon Jun 25 12:00:00 2007 UTC to Tue Jun 26 12:00:00 2007 UTC. There were 5 messages: 5 from Zope Unit Tests. Tests passed OK --- Subject: OK : Zope-2.7 Python-2.3.6 : Linux From: Zope Unit Tests Date: Mon Jun 25 20:51:04 EDT 2007 URL: http://mail.zope.org/pipermail/zope-tests/2007-June/007939.html Subject: OK : Zope-2.8 Python-2.3.6 : Linux From: Zope Unit Tests Date: Mon Jun 25 20:52:35 EDT 2007 URL: http://mail.zope.org/pipermail/zope-tests/2007-June/007940.html Subject: OK : Zope-2.9 Python-2.4.4 : Linux From: Zope Unit Tests Date: Mon Jun 25 20:54:06 EDT 2007 URL: http://mail.zope.org/pipermail/zope-tests/2007-June/007941.html Subject: OK : Zope-2.10 Python-2.4.4 : Linux From: Zope Unit Tests Date: Mon Jun 25 20:55:36 EDT 2007 URL: http://mail.zope.org/pipermail/zope-tests/2007-June/007942.html Subject: OK : Zope-trunk Python-2.4.4 : Linux From: Zope Unit Tests Date: Mon Jun 25 20:57:07 EDT 2007 URL: http://mail.zope.org/pipermail/zope-tests/2007-June/007943.html ___ 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 )
[Zope-dev] Re: howto move the portal_catalog to a separate zeo-server ?
Joachim Schmitz(e)k dio: > hi, > In a zeo-client, zeo-server-setup is it possible to move the > portal_catalog of a cmf/cps-instance, to a separate zeo-server ? If yes, > what would be the steps ? Especially how to define the mount-point. > > It's explained in this How-To: http://plone.org/documentation/how-to/mount-portal_catalog-in-separate-zodb/ Mikel -- Mikel Larreategi [EMAIL PROTECTED] CodeSyntax Azitaingo Industrialdea 3 K E-20600 Eibar Tel: (+34) 943 82 17 80 ___ 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 )
[Zope-dev] howto move the portal_catalog to a separate zeo-server ?
hi, In a zeo-client, zeo-server-setup is it possible to move the portal_catalog of a cmf/cps-instance, to a separate zeo-server ? If yes, what would be the steps ? Especially how to define the mount-point. -- Mit freundlichen GrüßenJoachim Schmitz .. AixtraWare eK ..Joachim Schmitz ..www.aixtraware.de ..t: +49-2464-8851 Hüsgenstr. 33a .d-52457 Aldenhoven .f: +49-2464-905163 ___ 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 )
