[Zope3-dev] Zope 3.2 maintenance
Hi! Recently I started to use formlib in Zope 2. The current stable release of Zope 3 is shipped with Zope 2.9, so I thought I would use actively maintained code. But I stumbled over some rough edges in zope.formlib and zope.app.form and started to wonder if I'm the first person who tries to use some specific features. So I decided to work on some fixes. But surprise! Many issues are already fixed on the 3.3 branch and trunk. Here is a small list of fixes that were never backported to the current stable branch: http://svn.zope.org/?rev=41043view=rev http://svn.zope.org/?rev=66579view=rev http://svn.zope.org/?rev=68157view=rev http://svn.zope.org/?rev=69760view=rev Are there good reasons why these changes were not backported? I volunteer to backport some fixes I'm missing in Zope 3.2, but that's no general solution for keeping the current stable branch maintained. Cheers, Yuppie ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
Re: [Zope3-dev] Zope 3.2 maintenance
yuppie wrote: [snip] I volunteer to backport some fixes I'm missing in Zope 3.2, but that's no general solution for keeping the current stable branch maintained. I think you bring up a very good point. Of course this also implies new Zope 2 release which include bugfix releases of Zope 3.2. It needs to become very clear who the point of contact is for maintenance issues, and some guidelines about backporting bugfixes might also be useful. In the Zope 2 world it's clear it's Andreas Jung, but unfortunately it's a bit more difficult in the Zope 3 world at this point in time. With the start of the Zope Foundation we also have the opportunity to consider such issues. Jim will shortly start a discussion concerning the Zope Management Organisation. Perhaps we can come up with something concerning maintainership and maintenance policy that we all like. Regards, Martijn ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
Re: [Zope3-dev] Zope 3.2 maintenance
On Friday 08 September 2006 04:12, yuppie wrote: Are there good reasons why these changes were not backported? I volunteer to backport some fixes I'm missing in Zope 3.2, but that's no general solution for keeping the current stable branch maintained. The short answer is: We are a bit sloppy. I always develop against the trunk, so when I fix an issue, I do not event think about porting it back to another release, other when one is imminent, like Zope 3.3 now. I think most other Zope 3 developers are the same. Overall, I would really like to find a person for each release being responsible for backporting bug fixes. It would be a relatively easy way to contribute to Zope 3. Regards, Stephan -- Stephan Richter CBU Physics Chemistry (B.S.) / Tufts Physics (Ph.D. student) Web2k - Web Software Design, Development and Training ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
