[Zope3-dev] Re: Zope 3.3.1 and 3.4
Christian Theune wrote: Hi, Baiju M wrote: On 9/28/06, Christian Theune [EMAIL PROTECTED] wrote: Please provide fixes and tests on the trunk and the 3.3 branch. What about 3.2, dropped ? Of course you can provide them for 3.2 as well. I'm not sure whether it's officially maintained anymore now ... My understanding was that we support: Current stable branch (3.3) + trunk No! 3.2 is maintained. Bugfixes will *first go to the 3.2 branch*. This is important, as Zope 3.2 is not only used out there in deployments but also part of Zope 2.9 which will increase its life time a lot more. Only during release time, we support three branches, e.g. yesterday it was: Stable (3.2) + In-Release (3.3) + trunk No. ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
[Zope3-dev] Re: Zope 3.3.1 and 3.4
Hi, Philipp von Weitershausen wrote: Christian Theune wrote: Hi, Baiju M wrote: On 9/28/06, Christian Theune [EMAIL PROTECTED] wrote: Please provide fixes and tests on the trunk and the 3.3 branch. What about 3.2, dropped ? Of course you can provide them for 3.2 as well. I'm not sure whether it's officially maintained anymore now ... My understanding was that we support: Current stable branch (3.3) + trunk No! 3.2 is maintained. Bugfixes will *first go to the 3.2 branch*. This is important, as Zope 3.2 is not only used out there in deployments but also part of Zope 2.9 which will increase its life time a lot more. Only during release time, we support three branches, e.g. yesterday it was: Stable (3.2) + In-Release (3.3) + trunk No. Can you repeat the specific rule for me? Christian -- gocept gmbh co. kg - forsterstraße 29 - 06112 halle/saale - germany www.gocept.com - [EMAIL PROTECTED] - phone +49 345 122 9889 7 - fax +49 345 122 9889 1 - zope and plone consulting and development signature.asc Description: OpenPGP digital signature ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
[Zope3-dev] Re: Zope 3.3.1 and 3.4
Christian Theune wrote: Hi, I saw some updates in the wiki tonight and thought I'll catch up with some stuff too. As I opted to take care for the Zope 3.4 release and Zope 3.3 is out of the door since yesterday, I've updated the roadmap. (Someone correct me if my information is out-dated) Current focus: Bug fixing Zope 3.3 -- Currently, we're aiming for a Zope 3.3 bugfix release (3.3.1) in November, which is managed by Martijn. Everybody is very encouraged to take a look at the collector and fix bugs instead of introducing new functionality. Please provide fixes and tests on the trunk and the 3.3 branch. ... *after* having it fixed on the 3.2 branch *first*. I'm the 3.2 bugfix manager and hope that we can soon have a 3.2.2 bugfix release as well. Next milestone: Zope 3.4 Due to the late release date for Zope 3.3 and the amount of open bugs, Zope 3.4 will be postponed one release cycle and will be released in May 2007. The largest project that I know of that aims for Zope 3.4 will be the eggification of Zope 3. I haven't seen a formal proposal for this yet, but AFAIK this is Jim's pet. Anybody else with larger features that are planned to go in for Zope 3.4? I want to make most of the browser:* directives saner in implementation, without actually changing their behaviour, though. Unless people want to make their behaviour saner, too ;). ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
[Zope3-dev] Re: Zope 3.3.1 and 3.4
Christian Theune wrote: Hi, Philipp von Weitershausen wrote: Christian Theune wrote: Hi, Baiju M wrote: On 9/28/06, Christian Theune [EMAIL PROTECTED] wrote: Please provide fixes and tests on the trunk and the 3.3 branch. What about 3.2, dropped ? Of course you can provide them for 3.2 as well. I'm not sure whether it's officially maintained anymore now ... My understanding was that we support: Current stable branch (3.3) + trunk No! 3.2 is maintained. Bugfixes will *first go to the 3.2 branch*. This is important, as Zope 3.2 is not only used out there in deployments but also part of Zope 2.9 which will increase its life time a lot more. Only during release time, we support three branches, e.g. yesterday it was: Stable (3.2) + In-Release (3.3) + trunk No. Can you repeat the specific rule for me? We'll repeat two stable branches, just like Zope 2. So, Zope 2 currently maintains 2.9 and 2.10. We maintain the Zope 3 counterparts, 3.2 and 3.3. ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
[Zope3-dev] Re: Zope 3.3.1 and 3.4
Hi, Philipp von Weitershausen wrote: I want to make most of the browser:* directives saner in implementation, without actually changing their behaviour, though. Unless people want to make their behaviour saner, too ;). I wouldn't mind making myself behave saner. :) As we're at it: I forgot to mention that the Blob project is still alive and got some rejuvenation in the last days by making the unit tests almost run on windows. (One problem with packing). So upgrading the ZODB would be another step. Something that I imagine could happen alongside the eggification is to do a kind of spring cleaning and check for the modules that won't be core-modules in the future - and decide how people will be able to still use them. Christian -- gocept gmbh co. kg - forsterstraße 29 - 06112 halle/saale - germany www.gocept.com - [EMAIL PROTECTED] - phone +49 345 122 9889 7 - fax +49 345 122 9889 1 - zope and plone consulting and development signature.asc Description: OpenPGP digital signature ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
[Zope3-dev] Re: Zope 3.3.1 and 3.4
Christian Theune wrote: Hi, Philipp von Weitershausen wrote: I want to make most of the browser:* directives saner in implementation, without actually changing their behaviour, though. Unless people want to make their behaviour saner, too ;). I wouldn't mind making myself behave saner. :) As we're at it: I forgot to mention that the Blob project is still alive and got some rejuvenation in the last days by making the unit tests almost run on windows. (One problem with packing). So upgrading the ZODB would be another step. Something that I imagine could happen alongside the eggification is to do a kind of spring cleaning and check for the modules that won't be core-modules in the future - and decide how people will be able to still use them. Yup. There are some things in zope.app (e.g. workflow, externaleditor, zopetop, module, schemacontent) that aren't shipped with a Zope 3 install and don't seem to be maintained anymore. I suggest that if no-one steps up for them they will simply be deleted. There are also some things in zope.app that may be maintained but never shipped. These things don't really belong in zope.app, IMO (boston, homefolder, styleguide, css) and should probably be moved out. Discussions with their individual authors/maintainers will be necessary. Philipp ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
Re: [Zope3-dev] Re: Zope 3.3.1 and 3.4
Hi, Philipp von Weitershausen wrote: Christian Theune wrote: Hi, Philipp von Weitershausen wrote: I want to make most of the browser:* directives saner in implementation, without actually changing their behaviour, though. Unless people want to make their behaviour saner, too ;). I wouldn't mind making myself behave saner. :) As we're at it: I forgot to mention that the Blob project is still alive and got some rejuvenation in the last days by making the unit tests almost run on windows. (One problem with packing). So upgrading the ZODB would be another step. Something that I imagine could happen alongside the eggification is to do a kind of spring cleaning and check for the modules that won't be core-modules in the future - and decide how people will be able to still use them. Yup. There are some things in zope.app (e.g. workflow, externaleditor, zopetop, module, schemacontent) that aren't shipped with a Zope 3 install and don't seem to be maintained anymore. I suggest that if no-one steps up for them they will simply be deleted. There are also some things in zope.app that may be maintained but never shipped. These things don't really belong in zope.app, IMO (boston, homefolder, styleguide, css) and should probably be moved out. Discussions with their individual authors/maintainers will be necessary. I agree on that. I'll put that on the prospective feature list so we don't forget about it. Christian -- gocept gmbh co. kg - forsterstraße 29 - 06112 halle/saale - germany www.gocept.com - [EMAIL PROTECTED] - phone +49 345 122 9889 7 - fax +49 345 122 9889 1 - zope and plone consulting and development signature.asc Description: OpenPGP digital signature ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
