Hello,
My only task was to setup the zope.wineggbuilder on the server with a
buildbot.
It is here:
http://173.203.65.130/
will be http://winbot.zope.org once DNS entries propagate
For this night it will do a testing round with zope.i18nmessageid,
for tomorrow night I'm going to switch it to full mode if nothing big
happens.
--
Best regards,
Adam GROSZER mailto:agroszer@gmail.com
--
Quote of the day:
The question is not whether we will die, but how we will live.
- Borysenko, Joan
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Today, I was able to fix two bugs in zope.testrunner:
. zope.testrunner 4.0.0b2 uninstallable when using Python 2.4,
https://bugs.launchpad.net/bugs/595052
- - StartUpFailure.shortDescription() fails with AttributeError,
https://bugs.launchpad.net/bugs/221151
and to release a 4.0.0b3 containing another three fixes:
- - zope.testrunner's buildout makes failing tests
https://bugs.launchpad.net/bugs/580083
- - Layer tearDown isn't called when running more processes,
https://bugs.launchpad.net/bugs/579019
- - Remove requirement for the $Id$ marker in module docstrings,
https://bugs.launchpad.net/bugs/569541
Tres.
- --
===================================================================
Tres Seaver +1 540-429-0999 tseaver(a)palladion.com
Palladion Software "Excellence by Design" http://palladion.com
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iEYEARECAAYFAkwY4W0ACgkQ+gerLs4ltQ4YmwCgj5vEQwziTne3OpJLytEmF/CJ
ufoAoJ+C+EIAO4gDdVSCq6DjoFOEx2P2
=7N8X
-----END PGP SIGNATURE-----
Hi,
here's what I did during the bugday today:
- tried fixing an invalidation issue with blobs, savepoints and ZEO
(#509801) This is now waiting for review by Jim
- triaged all remaining zope 3 bug issues into separate projects (and
created projects in LP as needed)
- set up the nightly languishing bug watch
- reviewed a couple of bugs fixed by romanofski and gotcha
I'll be dropping out for today, so everybody who's still bugdaying:
enjoy and thanks for all the work!
Christian
--
Christian Theune · ct(a)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
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi all,
Unknown to the Zope Foundation and the ZF admins it appears the zope.org
and zopefoundation.org domains have expired. The domains were held by
Rob Page as Zope Corporation representative.
For community members this means services like the different community
websites, SVN access, and the mailing lists may be disrupted until the
domain situation is corrected.
We are in the process of trying to reach Rob Page.
jens
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.8 (Darwin)
iEYEARECAAYFAkwYusUACgkQRAx5nvEhZLKzRgCfen1pSegA6r7ZigvwsRISM7Tu
rBUAnjBmAXwS6HECUYcoF3357z3750pF
=MVaV
-----END PGP SIGNATURE-----
Hi,
to improve our response time to new bugs Charlie did the nice job of
writing a script using the launchpad API that can poll projects and
project groups for languishing bugs.
I have set up nightly checks for the following scope:
- zopeapp project group
- zopetoolkit project group
- zope project group
- Zope2 project
Those should start appearing beginning from tomorrow and should be
included with the nightly reports.
Christian
--
Christian Theune · ct(a)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
Hi,
as doodled, there's a bug day coming up tomorrow. That means reporting,
triaging, fixing, and discussing bugs of Zope 2, Bluebream, grok, ZTK,
just everything touching Zope code to have a shared experience.
If you want to join, we'll hang out on #zope@freenode and me (Theuni,
I'll be around during working hours in CEST) and others are happy to
assist if you don't know how bug days work.
For everyone who is used to bug days I'm also inviting you to write a
short summary when you finish your bug day so that everyone can see
where we're making progress.
Happy bug daying everyone!
Christian
--
Christian Theune · ct(a)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
Hi there,
we had an initial roadmap discussion back in March
(https://mail.zope.org/pipermail/zope-dev/2010-March/039915.html).
Some things have changed since then, so it's time for an update.
The big picture:
Zope 2.12.0 final was released October 1, 2009 - the first alpha back
in February 2009. A lot of time has passed since then and we have made
quite a number of changes to Zope2 in the meantime.
Plone 4.0 is getting ever more delayed and is still in late beta.
Based on the current speed it will be another two years until there's
a final 5.0 release of Plone. This is far too long for not having a
Zope 2 release.
So I talked to Eric Steele as the Plone 4.x release manager and a
couple of people in the community. There is general agreement that
updating to a Zope 2.13 release for Plone 4.1 is a sensible approach.
Plone 4.1 has an approximate release of sometime in six to nine
months.
The plan:
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.
What do we have in Zope 2.13:
- zope.app removal
- moving formlib out of the core into five.formlib
- WSGI - thx to Tres and some help from the Plone Symposium East
sprint, we have native WSGI support in Zope 2 now. Probably can use
some polishing, more testing and documentation - perfect tasks for
alpha releases and larger community involvement.
- ZTK - The ZTK release team is getting close to having a first ZTK
1.0 alpha release out. I'm confident Zope 2.13 can be based on an
official ZTK release.
- Five deprecation - I did a whole bunch of work here and I consider
it good enough for a next step. There's always more to do, but there's
enough already in this release.
- Reduce C code in Zope 2 - I made good progress on this.
AccessControl has almost no Zope2 dependencies anymore and
DocumentTemplate is cleaned up. Some more work can be done during the
alpha releases and we can probably finish this one.
- ZODB 3.10 - Current Zope 2 trunk is already using a 3.10 beta
release. I talked to Jim and he's confident to get a final release out
in a matter of two to three months or so.
That's quite a bit already. Support for Python 2.7 is blocking on the
RestrictedPython security review for the most part, Python 3 support
is not on the radar.
I hope we get some more changes from Martin Aspeli's work on
plone.(app.)testing and a new more modular testing infrastructure.
There's a bunch of stuff in the startup process and ZCML loading that
can be cleaned up.
In order to make this story more appealing, I spent the last two
weekends on cleaning up CMF and Plone and making it compatible with
current Zope trunk. As of this moment all tests of CMF and Plone pass
on Zope trunk. The changes are minimal and backwards compatible, so
they are also in the stable releases. This means both CMF 2.2.1 and
Plone 4.0 beta5 are going to be fully compatible with Zope trunk.
Comments, suggestions, more work you'd like to get into 2.13?
Cheers,
Hanno