Hi, I plan to release Zope 2.10.2 in a week or so (don't nail me to a particular date). This will be a beta release because it contains several ZPT changes (as discussed earlier on the list) that must/should be tested. In addition I will merge my latest changes (the UnicodeEncodingConflictResolver stuff) in order to make the handling of UnicodeDecodeErrors (possibly introduced by the changes) configurable. I am aware that this is a new feature which is forbidden by design on a release branch however there is a need to deal with such decoding errors in a reasonable and configurable way. However the default behavior won't change. Andreas
Hi! Andreas Jung wrote:
I plan to release Zope 2.10.2 in a week or so (don't nail me to a particular date).
The Zope 2.10 branch still uses Five 1.5.1. There are a few changes on the Five 1.5 branch (including a security fix) which should become part of Zope 2.10.2. I volunteer to resolve this as follows: Five releases are now linked tightly to specific Zope releases, so it doesn't make much sense to do still separate Five releases. See this thread: http://codespeak.net/pipermail/z3-five/2006q4/001889.html If there are no objections, I'll stitch the Five 1.5 branch HEAD directly into the Zope 2.10 branch (without using svn externals) and Five trunk HEAD into the Zope trunk. This would mean that from now on Five 1.5 and 1.6 are maintained as part of Zope 2. In fact there will be no Five 1.5.2 or 1.6 because there will no longer be any separate releases. Thoughts? Cheers, Yuppie
--On 7. Januar 2007 14:48:43 +0100 yuppie <y.2007-@wcm-solutions.de> wrote:
If there are no objections, I'll stitch the Five 1.5 branch HEAD directly into the Zope 2.10 branch (without using svn externals) and Five trunk HEAD into the Zope trunk. This would mean that from now on Five 1.5 and 1.6 are maintained as part of Zope 2. In fact there will be no Five 1.5.2 or 1.6 because there will no longer be any separate releases.
I don't have a problem with this approach. In fact the change would make clear which version belongs to what. Andreas
yuppie wrote:
Hi!
Andreas Jung wrote:
I plan to release Zope 2.10.2 in a week or so (don't nail me to a particular date).
The Zope 2.10 branch still uses Five 1.5.1. There are a few changes on the Five 1.5 branch (including a security fix) which should become part of Zope 2.10.2.
I volunteer to resolve this as follows:
Five releases are now linked tightly to specific Zope releases, so it doesn't make much sense to do still separate Five releases. See this thread: http://codespeak.net/pipermail/z3-five/2006q4/001889.html
If there are no objections, I'll stitch the Five 1.5 branch HEAD directly into the Zope 2.10 branch (without using svn externals) and Five trunk HEAD into the Zope trunk. This would mean that from now on Five 1.5 and 1.6 are maintained as part of Zope 2. In fact there will be no Five 1.5.2 or 1.6 because there will no longer be any separate releases.
Thoughts?
+ sys.maxint -- http://worldcookery.com -- Professional Zope documentation and training 2nd edition of Web Component Development with Zope 3 is now shipping!
Hi! Philipp von Weitershausen wrote:
yuppie wrote:
The Zope 2.10 branch still uses Five 1.5.1. There are a few changes on the Five 1.5 branch (including a security fix) which should become part of Zope 2.10.2.
I volunteer to resolve this as follows:
Five releases are now linked tightly to specific Zope releases, so it doesn't make much sense to do still separate Five releases. See this thread: http://codespeak.net/pipermail/z3-five/2006q4/001889.html
If there are no objections, I'll stitch the Five 1.5 branch HEAD directly into the Zope 2.10 branch (without using svn externals) and Five trunk HEAD into the Zope trunk. This would mean that from now on Five 1.5 and 1.6 are maintained as part of Zope 2. In fact there will be no Five 1.5.2 or 1.6 because there will no longer be any separate releases.
Thoughts?
+ sys.maxint
For the records: After some more off-list discussion with Philipp I decided to move only the trunk. This is done now. The 1.5 branch still exists and Philipp tagged Five 1.5.2 for Zope 2.10.2. Cheers, Yuppie
--On 10. Januar 2007 18:28:42 +0100 yuppie <y.2007-@wcm-solutions.de> wrote:
Hi!
Philipp von Weitershausen wrote:
yuppie wrote:
The Zope 2.10 branch still uses Five 1.5.1. There are a few changes on the Five 1.5 branch (including a security fix) which should become part of Zope 2.10.2.
I volunteer to resolve this as follows:
Five releases are now linked tightly to specific Zope releases, so it doesn't make much sense to do still separate Five releases. See this thread: http://codespeak.net/pipermail/z3-five/2006q4/001889.html
If there are no objections, I'll stitch the Five 1.5 branch HEAD directly into the Zope 2.10 branch (without using svn externals) and Five trunk HEAD into the Zope trunk. This would mean that from now on Five 1.5 and 1.6 are maintained as part of Zope 2. In fact there will be no Five 1.5.2 or 1.6 because there will no longer be any separate releases.
Thoughts?
+ sys.maxint
For the records:
After some more off-list discussion with Philipp I decided to move only the trunk. This is done now.
The 1.5 branch still exists and Philipp tagged Five 1.5.2 for Zope 2.10.2.
Thank you both! Andreas
participants (3)
-
Andreas Jung -
Philipp von Weitershausen -
yuppie