Re: [Zope-dev] RFC: 3.4.1 KGS?
AG> I created a sheet with versions AG> http://spreadsheets.google.com/pub?key=tUE5Q72d4Kg1FXaacCA3EKQ&output=html AG> Right now it's a sort of highest version affordable after a quick scan AG> through the version. I'm thinking about doing one more round to take a AG> closer look and probably screw some versions back. I did one more round on it. The open questions that remain: * What about pytz 2010g? * Which lxml version to take? 1.3.6? * What about zope.app.container 3.6.2? * Would be nice to have zope.testbrowser 3.5.1 Anyone for/against those versions? -- Best regards, Adam GROSZERmailto:agros...@gmail.com -- Quote of the day: There is nothing except what you sense ___ 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] RFC: 3.4.1 KGS?
Hello Marius, Wednesday, March 31, 2010, 2:50:33 PM, you wrote: ... MG> * look at other possible bugfix upgrades, see if there are any MG>important bugs fixed (zope.release's bin/list-latest is useful here) ... I created a sheet with versions http://spreadsheets.google.com/pub?key=tUE5Q72d4Kg1FXaacCA3EKQ&output=html Right now it's a sort of highest version affordable after a quick scan through the version. I'm thinking about doing one more round to take a closer look and probably screw some versions back. -- Best regards, Adam GROSZERmailto:agros...@gmail.com -- Quote of the day: We die only once, and for such a long time. - Moliere ___ 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] RFC: 3.4.1 KGS?
Hello Marius, Just released zope.publisher 3.4.10. Seems to have a LOT of fixes vs. 3.4.6 Wednesday, March 31, 2010, 2:50:33 PM, you wrote: ... -- Best regards, Adam GROSZERmailto:agros...@gmail.com -- Quote of the day: Civilization is a movement, not a condition; it is a voyage, not a harbor. - Toynbee ___ 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] RFC: 3.4.1 KGS?
Hello Wichert, Because of our toolchain to release and deploy apps: mypypi and keas.build. In fact, because of keas.build depends on zc.buildout. Friday, April 2, 2010, 10:53:26 AM, you wrote: WA> On 4/2/10 10:36 , Adam GROSZER wrote: >> zc.buildout is a tough decision, because it's "not upgrading" issue. >> See http://mail.python.org/pipermail/distutils-sig/2010-March/015794.html WA> Why would you ever install zc.buildout systemwide? Just as with WA> setuptools I consider that to be a recipe for problems. WA> Wichert. WA> ___ WA> Zope-Dev maillist - Zope-Dev@zope.org WA> https://mail.zope.org/mailman/listinfo/zope-dev WA> ** No cross posts or HTML encoding! ** WA> (Related lists - WA> https://mail.zope.org/mailman/listinfo/zope-announce WA> https://mail.zope.org/mailman/listinfo/zope ) -- Best regards, Adam GROSZERmailto:agros...@gmail.com -- Quote of the day: One man tells a falsehood, a hundred repeat it as true. ___ 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] RFC: 3.4.1 KGS?
On 4/2/10 10:36 , Adam GROSZER wrote: > zc.buildout is a tough decision, because it's "not upgrading" issue. > See http://mail.python.org/pipermail/distutils-sig/2010-March/015794.html Why would you ever install zc.buildout systemwide? Just as with setuptools I consider that to be a recipe for problems. Wichert. ___ 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] RFC: 3.4.1 KGS?
Hello Marius, +1 on a KGS 3.4.1 Local overrides here: zope.component = 3.5.1 zope.contenttype = 3.4.2 zope.i18n = 3.5.0 zope.sendmail = 3.5.0 zope.server = 3.5.0 zope.session = 3.5.2 zope.tal = 3.5.0 zope.testing = 3.7.5 #was 3.7.0 but let's try this zope.traversing = 3.5.0a4 zope.testbrowser = 3.5 #mechanize changed the HTTPError class zope.app.appsetup = 3.6.0 zope.app.container = 3.6.0 zope.app.form = 3.5.0 zope.app.intid = 3.5.0 zope.app.publisher = 3.5.0a4 zope.app.wsgi = 3.4.2 #fixes product config zope.app.http = 3.4.5 #fixes IDefaultView vs. PROPFIND lxml = 2.2.4 #or something that works on win32 I might backport a bugfix in zope.publisher r101467 zc.buildout is a tough decision, because it's "not upgrading" issue. See http://mail.python.org/pipermail/distutils-sig/2010-March/015794.html What's the schedule? Wednesday, March 31, 2010, 2:50:33 PM, you wrote: MG> On Wed, Mar 31, 2010 at 01:37:47PM +0200, Christian Theune wrote: >> On 03/31/2010 12:35 PM, Adam GROSZER wrote: >> >One point for the next agenda: >> >As Marius also had the issue to do a KGS 3.4.1. MG> Mostly I wanted to know if anybody was using the KGS in production and MG> interested in a point release. IRC seemed the right place for a straw MG> poll before an email to zope-dev@, except that I had to run sooner than MG> I thought so I didn't see how people reacted. MG> I recently looked at the zope.release 3.4 branch and saw that it has a MG> bunch of updated package versions since the 3.4.0 release (which was in MG> January 2009). I'm especially interested in setuptools 0.6c11, since MG> the KGS currently pins to 0.6c9, which doesn't support Subversion 1.6 MG> checkouts. MG> We use the 3.4 KGS in production with a few extra pins. Some fix MG> important bugs: MG> zope.app.component = 3.4.2 # very important bugfix for BBB MG> ZODB3 = 3.8.4 # security fixes MG> zope.sendmail = 3.5.1 # This version handles the 5xx errors MG> zope.security = 3.4.2 # bugfixes for Python 2.5 MG> setuptools = 0.6c11 MG> then there are the "we just want the latest tools" pins for zc.buildout MG> and zope.testing, which I'm not proposing to push into a KGS point MG> update (especially with the zope.testing.doctest deprecation which MG> pushes people into using buggy stdlib's doctest). MG> I'm also interested in a bugfix for zope.sendmail that's not done yet: MG> currently it starts the background mail processing thread even if do MG> things like bin/development-instance debug. This can result in emails MG> sent out twice. It also doesn't let the process quit, due to changes in MG> Python's 2.5 threading semantics (atexit handlers that are trying to MG> stop the background thread now are postponed until after all threads MG> terminate). The latest zope.sendmail can avoid this mess by disabling MG> the delivery thread and using a standalone thread-watching script, but MG> it depends on newer core packages and is incompatible with the 3.4 KGS. MG> The 3.4 buildbot tracks the tip of the zope.release's 3.4 branch. All MG> tests pass there. I see that zope.app.component 3.4.2 and setuptools MG> 0.6c11 are already in the (unreleased) 3.4 KGS; ZODB3 3.8.4, MG> zope.sendmail 3.5.1 and zope.security 3.4.2 aren't. MG> So, my plan of action is: MG> * fix zope.sendmail using the approach discussed on this list a few MG>weeks ago MG> * look at other possible bugfix upgrades, see if there are any MG>important bugs fixed (zope.release's bin/list-latest is useful here) MG> * bump ZODB3, zope.sendmail, zope.security versions in the 3.4 KGS, see MG>what buildbot things of this MG> * try to get a 3.4.1 release out of the door <-- this is where I'm MG>fuzzy. I think I used to have ssh access to download.zope.org, but I MG>don't even remember how you're supposed to use zope.release's bin/upload, MG>and I never knew how the releases were made. MG> Marius Gedminas -- Best regards, Adam GROSZERmailto:agros...@gmail.com -- Quote of the day: Top ten things you'll never hear in an internet chat room: 6. You know, to get a really fast connection, you've gotta go through America Online. ___ 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] RFC: 3.4.1 KGS?
Sebastien Douche a écrit : > On Wed, Mar 31, 2010 at 14:50, Marius Gedminas wrote: >> Mostly I wanted to know if anybody was using the KGS in production and >> interested in a point release. > > Yes! :) > >> I'm especially interested in setuptools 0.6c11, since >> the KGS currently pins to 0.6c9, which doesn't support Subversion 1.6 >> checkouts. > > we use distribute w/o issue. > >> We use the 3.4 KGS in production with a few extra pins. Some fix >> important bugs: >> >> zope.app.component = 3.4.2 # very important bugfix for BBB >> ZODB3 = 3.8.4 # security fixes >> zope.sendmail = 3.5.1 # This version handles the 5xx errors >> zope.security = 3.4.2 # bugfixes for Python 2.5 >> setuptools = 0.6c11 > > our vendor KGS: > > lxml = 2.2.2 > tl.eggdeps = 0.4 > transaction = 1.0a1 > z3c.batching = 1.1.0 > z3c.contents = 0.5.0 > z3c.coverage = 1.1.3 > z3c.etestbrowser = 1.3.0 > z3c.evalexception = 2.0 > z3c.i18n = 0.1.1 > z3c.layer.minimal = 1.2.0 > z3c.layer.pagelet = 1.0.1 There is a big security issue on this package. You should update to 1.0.2 as soon as possible 1.0.2 (2009-04-03) - http://pypi.python.org/pypi/z3c.layer.pagelet/1.0.2 - **Security issue:** The traverser defined for ``IPageletBrowserLayer`` was a trusted adapter, so the security proxy got removed from each traversed object. Thus all sub-objects were publically accessable, too. Then have fun fixing all the security declaration. Everything seems easy with z3c.layer.pagelet 1.0.1 > z3c.profiler = 0.7.1 > z3c.recipe.compattest = 0.11 > z3c.recipe.depgraph = 0.4.0sa1 > z3c.recipe.i18n = 0.5.4 > z3c.recipe.paster = 0.5.0 > z3c.table = 0.6.0 > z3c.testsetup = 0.5.1 > zc.recipe.egg = 1.2.2 > zope.sqlalchemy = 0.4 > zope.testing = 3.8.3sa1 > > lxml, zope.testing & zope.etestbrowser are the most important update I guess. > >> * try to get a 3.4.1 release out of the door <-- this is where I'm >> fuzzy. I think I used to have ssh access to download.zope.org, but I >> don't even remember how you're supposed to use zope.release's bin/upload, >> and I never knew how the releases were made. > > it's simple: > - upload all eggs on the cheeseshop > - create the controled-packages.cfg. Example: > http://download.zope.org/zope3.4/3.4.0/controlled-packages.cfg > - generate the site with zope.kgs > > ___ 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] RFC: 3.4.1 KGS?
On Wed, Mar 31, 2010 at 14:50, Marius Gedminas wrote: > Mostly I wanted to know if anybody was using the KGS in production and > interested in a point release. Yes! :) > I'm especially interested in setuptools 0.6c11, since > the KGS currently pins to 0.6c9, which doesn't support Subversion 1.6 > checkouts. we use distribute w/o issue. > We use the 3.4 KGS in production with a few extra pins. Some fix > important bugs: > > zope.app.component = 3.4.2 # very important bugfix for BBB > ZODB3 = 3.8.4 # security fixes > zope.sendmail = 3.5.1 # This version handles the 5xx errors > zope.security = 3.4.2 # bugfixes for Python 2.5 > setuptools = 0.6c11 our vendor KGS: lxml = 2.2.2 tl.eggdeps = 0.4 transaction = 1.0a1 z3c.batching = 1.1.0 z3c.contents = 0.5.0 z3c.coverage = 1.1.3 z3c.etestbrowser = 1.3.0 z3c.evalexception = 2.0 z3c.i18n = 0.1.1 z3c.layer.minimal = 1.2.0 z3c.layer.pagelet = 1.0.1 z3c.profiler = 0.7.1 z3c.recipe.compattest = 0.11 z3c.recipe.depgraph = 0.4.0sa1 z3c.recipe.i18n = 0.5.4 z3c.recipe.paster = 0.5.0 z3c.table = 0.6.0 z3c.testsetup = 0.5.1 zc.recipe.egg = 1.2.2 zope.sqlalchemy = 0.4 zope.testing = 3.8.3sa1 lxml, zope.testing & zope.etestbrowser are the most important update I guess. > * try to get a 3.4.1 release out of the door <-- this is where I'm > fuzzy. I think I used to have ssh access to download.zope.org, but I > don't even remember how you're supposed to use zope.release's bin/upload, > and I never knew how the releases were made. it's simple: - upload all eggs on the cheeseshop - create the controled-packages.cfg. Example: http://download.zope.org/zope3.4/3.4.0/controlled-packages.cfg - generate the site with zope.kgs -- Sebastien Douche Twitter: http://bit.ly/afkrK (agile, python, open source) ___ 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] RFC: 3.4.1 KGS?
Hi, Marius Gedminas a écrit : > On Wed, Mar 31, 2010 at 01:37:47PM +0200, Christian Theune wrote: >> On 03/31/2010 12:35 PM, Adam GROSZER wrote: >>> One point for the next agenda: >>> As Marius also had the issue to do a KGS 3.4.1. > > Mostly I wanted to know if anybody was using the KGS in production and > interested in a point release. I do I'm already using all the minor versions upgrades, this is also some kind of unreleased 3.4.1. > > So, my plan of action is: > > * fix zope.sendmail using the approach discussed on this list a few >weeks ago > > * look at other possible bugfix upgrades, see if there are any >important bugs fixed (zope.release's bin/list-latest is useful here) It would be good to have a tool (bin/upgrade-minor or something) to upgrade package versions of a buildout to the highest minor release available. I remember that bin/list-latest only works for the Maybe it already exists? > > * bump ZODB3, zope.sendmail, zope.security versions in the 3.4 KGS, see >what buildbot things of this > > * try to get a 3.4.1 release out of the door <-- this is where I'm >fuzzy. I think I used to have ssh access to download.zope.org, but I >don't even remember how you're supposed to use zope.release's bin/upload, >and I never knew how the releases were made. I had helped a bit for the 3.4.0 release, I still remember a few things, particularly about zope.release or zope.kgs. However I did'nt have any ssh access. But I can probably help. Christophe > > Marius Gedminas ___ 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] RFC: 3.4.1 KGS?
On Wed, Mar 31, 2010 at 01:37:47PM +0200, Christian Theune wrote: > On 03/31/2010 12:35 PM, Adam GROSZER wrote: > >One point for the next agenda: > >As Marius also had the issue to do a KGS 3.4.1. Mostly I wanted to know if anybody was using the KGS in production and interested in a point release. IRC seemed the right place for a straw poll before an email to zope-dev@, except that I had to run sooner than I thought so I didn't see how people reacted. I recently looked at the zope.release 3.4 branch and saw that it has a bunch of updated package versions since the 3.4.0 release (which was in January 2009). I'm especially interested in setuptools 0.6c11, since the KGS currently pins to 0.6c9, which doesn't support Subversion 1.6 checkouts. We use the 3.4 KGS in production with a few extra pins. Some fix important bugs: zope.app.component = 3.4.2 # very important bugfix for BBB ZODB3 = 3.8.4 # security fixes zope.sendmail = 3.5.1 # This version handles the 5xx errors zope.security = 3.4.2 # bugfixes for Python 2.5 setuptools = 0.6c11 then there are the "we just want the latest tools" pins for zc.buildout and zope.testing, which I'm not proposing to push into a KGS point update (especially with the zope.testing.doctest deprecation which pushes people into using buggy stdlib's doctest). I'm also interested in a bugfix for zope.sendmail that's not done yet: currently it starts the background mail processing thread even if do things like bin/development-instance debug. This can result in emails sent out twice. It also doesn't let the process quit, due to changes in Python's 2.5 threading semantics (atexit handlers that are trying to stop the background thread now are postponed until after all threads terminate). The latest zope.sendmail can avoid this mess by disabling the delivery thread and using a standalone thread-watching script, but it depends on newer core packages and is incompatible with the 3.4 KGS. The 3.4 buildbot tracks the tip of the zope.release's 3.4 branch. All tests pass there. I see that zope.app.component 3.4.2 and setuptools 0.6c11 are already in the (unreleased) 3.4 KGS; ZODB3 3.8.4, zope.sendmail 3.5.1 and zope.security 3.4.2 aren't. So, my plan of action is: * fix zope.sendmail using the approach discussed on this list a few weeks ago * look at other possible bugfix upgrades, see if there are any important bugs fixed (zope.release's bin/list-latest is useful here) * bump ZODB3, zope.sendmail, zope.security versions in the 3.4 KGS, see what buildbot things of this * try to get a 3.4.1 release out of the door <-- this is where I'm fuzzy. I think I used to have ssh access to download.zope.org, but I don't even remember how you're supposed to use zope.release's bin/upload, and I never knew how the releases were made. Marius Gedminas -- http://pov.lt/ -- Zope 3 consulting and development 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 )
