sorry for the lag (and thanks for Charlie to pick up the reminder today).
Here's last weeks summary.
Biggeste note: next bug day is on 2010-05-19 which is a rainy Wednesday
- a perfect day for sitting inside and smashing bugs.
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
Weekly Zope developer meeting
This is the summary of the weekly Zope developer meeting which happened on
Tuesday, 2010-04-27 on #z...@irc.freenode.org from 3pm to 3:30pm (UTC).
The agenda for this meeting is available in the mailing list archives:
The IRC logs are located here:
Review bug day outcome
Quite a few people showed up (Christophe Combelles, Tres Seaver, Christian
Theune, Charlie Clark, Roman Joost, during bug day and a substantial
number of bugs were handled.
Christophe Combelles reported having worked on zope.container and
zope.app.container. He backported his fixes to 3.5 and 3.6 awaiting for minor
releases (binaries needed).
Charlie Clark reported enjoyment about committing patches that were sitting
around for quite a while. He had a good experience asking questions as he knew
others were working on bugs as well. He points out that we still have a lot of
work to do and coding style and test coverage have to improve.
Christian Theune reported that he was around during 9am and 3pm CEST as a
guide and handled all the Zope 3 bugs that had patches attached. He started
working on a test browser bug about referrer handling which is the hottest bug
as indicated by launchpad. He'd like to see and attend monthly bug days
although weekends are hard.
We do have some fixes that are sitting in the repository, waiting for a
release now. A task that would be helpful is going through the "fix comitted"
bugs and releasing the packages as appropriate.
Adam Groszer worked on the KGS 3.4.1 and made some progress, but he'll need
more small steps to conclude the release.
Many people agreed that regular bug days will help a lot
and we definitely need to do them monthly. A quick discussion about having them
on weekdays or weekends turned towards having the next bug day during the
week. Charlie suggested Wednesday 2010-05-19 which was supported by other
participants and thus agreed as the next bug day. (Already announced on the
list and with a wiki page: http://wiki.zope.org/ztk/BugDays)
State of bug tracking/LP usage
Christian Theune created the "zopeapp" project group in anticipation of the
bug day and gathered as many zope.app.* packages he could find on Launchpad in
them. He also created new projects based on bugs he found/worked on. If any
are missing, please tell and more projects can be created quickly.
The Zope 3 project which we want to empty out from bug reports (by setting
them to 'wontfix' and assigning the bugs to individual projects) still has
bugs assigned. Although many people contributed, we need to continue work on
For the next bug day, we should also plan to clean up the bug trackers
Christian Theune pointed out that the 'zope.org' project group on Launchpad
(https://edge.launchpad.net/zope) is messy and not defined clearly. Although
the project group and name is a good entry point for marketing/advertisement
the way it's used does more harm than good. The recommendation is to get rid
of the project group but there has been no clear decision for this.
Windows machines status update
Tres wasn't around but Christian Theune reported that there was progress on
the topic of getting people access to the MSDN compiler suite. We'll wait for
a report of Tres.
Zope-Dev maillist - Zope-Dev@zope.org
** No cross posts or HTML encoding! **
(Related lists -