Hi All,
I'd like to backport the change I made to fix:
http://www.zope.org/Collectors/Zope/1490
...to the 2.8 branch, would anyone have any objections to this?
cheers,
Chris
--
Simplistix - Content Management, Zope Python Consulting
- http://www.simplistix.co.uk
--On 8. Oktober 2005 19:15:57 +0100 Chris Withers [EMAIL PROTECTED]
wrote:
Hi All,
I'd like to backport the change I made to fix:
http://www.zope.org/Collectors/Zope/1490
...to the 2.8 branch, would anyone have any objections to this?
The 2.8 branch is closed for new features. With the
Andreas Jung wrote:
I'd like to backport the change I made to fix:
http://www.zope.org/Collectors/Zope/1490
...to the 2.8 branch, would anyone have any objections to this?
The 2.8 branch is closed for new features. With the time-based schedule
new features should appear regularly with new
Andreas Jung wrote:
The 2.8 branch is closed for new features. With the time-based schedule
new features should appear regularly with new major releases. So only
bug fixes should go into minor releases.
In fact, just noticing other mails, I'd also like to merge this to the
2.7 branch, I
Am Samstag, den 08.10.2005, 19:15 +0100 schrieb Chris Withers:
Hi All,
I'd like to backport the change I made to fix:
http://www.zope.org/Collectors/Zope/1490
...to the 2.8 branch, would anyone have any objections to this?
Surely not, but what fix? :-)
Nice to see some movement on this
--On 8. Oktober 2005 20:10:21 +0100 Chris Withers [EMAIL PROTECTED]
wrote:
Andreas Jung wrote:
I'd like to backport the change I made to fix:
http://www.zope.org/Collectors/Zope/1490
...to the 2.8 branch, would anyone have any objections to this?
The 2.8 branch is closed for new
Andreas Jung wrote:
Well, this is arguably a bug fix and I incorrectly filed it as a new
feature on the trunk.
If you can justify it as a bugfix before god and the world,go ahead :-)
Cool, will do so to the 2.7 and 2.8 branches tomorrow :-)
cheers,
Chris
PS: I'll mark it as a bug fix in
