I plan to release Zope 2.12.1 on November 2nd, 2009. Objections or open issues? Andreas -- ZOPYX Ltd. & Co KG \ ZOPYX & Friends Charlottenstr. 37/1 \ The experts for your Python, Zope and D-72070 Tübingen \ Plone projects www.zopyx.com, info@zopyx.com \ www.zopyx.de/friends, friends@zopyx.de ------------------------------------------------------------------------ E-Publishing, Python, Zope & Plone development, Consulting
On Fri, 23 Oct 2009 19:15:54 +0200 Andreas Jung <lists@zopyx.com> wrote: Hello,
I plan to release Zope 2.12.1 on November 2nd, 2009.
Objections or open issues?
I agree it will be great, if that issue is fixed: https://bugs.launchpad.net/zope2/+bug/360761 Otherwise, I still can't used Zope 2.12. Best regards, Sylvain, -- Sylvain Viollon -- Infrae t +31 10 243 7051 -- http://infrae.com Hoevestraat 10 3033GC Rotterdam -- The Netherlands
Am 26.10.09 10:25, schrieb Sylvain Viollon:
I agree it will be great, if that issue is fixed:
https://bugs.launchpad.net/zope2/+bug/360761
Otherwise, I still can't used Zope 2.12.
Best regards,
Sylvain,
@Andi: could you please give some love to this issue? Andreas
On Oct 23, 2009, at 1:15 PM, Andreas Jung wrote:
I plan to release Zope 2.12.1 on November 2nd, 2009.
Objections or open issues?
Andreas
For what it's worth, that'd be perfect timing for Plone 4. I'm hoping to put out a first alpha right after the conference and we'll need 2.12.1 to do so. Eric
Am 26.10.09 14:13, schrieb Eric Steele:
On Oct 23, 2009, at 1:15 PM, Andreas Jung wrote:
I plan to release Zope 2.12.1 on November 2nd, 2009.
Objections or open issues?
Andreas
For what it's worth, that'd be perfect timing for Plone 4. I'm hoping to put out a first alpha right after the conference and we'll need 2.12.1 to do so. Give Andi Zeidler a gentle kick :)
Andreas
Andreas Jung wrote:
I plan to release Zope 2.12.1 on November 2nd, 2009.
Objections or open issues?
I'd like to nominate this bug: https://bugs.launchpad.net/zope2/+bug/461446 It's a regression. Cheers, Yuppie
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 yuppie wrote:
Andreas Jung wrote:
I plan to release Zope 2.12.1 on November 2nd, 2009.
Objections or open issues?
I'd like to nominate this bug: https://bugs.launchpad.net/zope2/+bug/461446
It's a regression.
+1 for fixing this prior to release: the regression breaks the zopectl shell. Tres. - -- =================================================================== Tres Seaver +1 540-429-0999 tseaver@palladion.com Palladion Software "Excellence by Design" http://palladion.com -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkrnM5kACgkQ+gerLs4ltQ4SQQCfYovGBcNwGUhNpFeWoa7eIJ+4 fzsAoJTejSDBtcL9BHtKAZkGeYnolPIx =ZFXz -----END PGP SIGNATURE-----
Am 26.10.09 22:28, schrieb yuppie:
Andreas Jung wrote:
I plan to release Zope 2.12.1 on November 2nd, 2009.
Objections or open issues?
I'd like to nominate this bug: https://bugs.launchpad.net/zope2/+bug/461446 You're going to fix it?
Andrea
Hi! Andreas Jung wrote:
Am 26.10.09 22:28, schrieb yuppie:
Andreas Jung wrote:
I plan to release Zope 2.12.1 on November 2nd, 2009.
Objections or open issues?
I'd like to nominate this bug: https://bugs.launchpad.net/zope2/+bug/461446 You're going to fix it?
I hope Chris W. will fix this. He is more familiar with the zopectl code and he already fixed some other regressions caused by his refactoring. AFAICT my patch fixes the issue, but it fixes it in the wrong place. And it would cost me some time to figure out how to do this right. Cheers, Yuppie
yuppie wrote:
I hope Chris W. will fix this.
I'll try and have a look before Nov 1st. He is more familiar with the zopectl code
and he already fixed some other regressions caused by his refactoring.
I have? News to me...
AFAICT my patch fixes the issue, but it fixes it in the wrong place. And it would cost me some time to figure out how to do this right.
Your patch seems a bit odd... If I understand what you're trying to report: when using zopectl interactively (on windows? on linux? on both?) some commands (which commands?) cause the interactive session to end when you'd expect them not to? If so, perhaps you could update the issue with the requested information? cheers, Chris -- Simplistix - Content Management, Batch Processing & Python Consulting - http://www.simplistix.co.uk
Hi! Chris Withers wrote:
yuppie wrote:
I hope Chris W. will fix this.
I'll try and have a look before Nov 1st.
Great!
He is more familiar with the zopectl code
and he already fixed some other regressions caused by his refactoring.
I have? News to me...
I don't want to argue about this. I might be wrong. But these things did work for me in 2.12.0 so I consider them regression issues: https://bugs.launchpad.net/zope2/+bug/440490 https://bugs.launchpad.net/zope2/+bug/443005
AFAICT my patch fixes the issue, but it fixes it in the wrong place. And it would cost me some time to figure out how to do this right.
Your patch seems a bit odd...
Did I say something different? I never proposed to check it in. I just thought it might be useful for understanding the issue.
If I understand what you're trying to report: when using zopectl interactively (on windows? on linux? on both?)
Quoting from my bug report: "Windows only"
some commands (which commands?)
Quoting from my bug report: "most commands, e.g. after start, restart and stop"
cause the interactive session to end when you'd expect them not to?
Exactly.
If so, perhaps you could update the issue with the requested information?
The requested information is already in the bug report. Please let me know if you need additional information. Cheers, Yuppie
yuppie wrote:
He is more familiar with the zopectl code
and he already fixed some other regressions caused by his refactoring. I have? News to me...
I don't want to argue about this. I might be wrong. But these things did work for me in 2.12.0 so I consider them regression issues:
https://bugs.launchpad.net/zope2/+bug/440490 https://bugs.launchpad.net/zope2/+bug/443005
These were broken before I made any changes. I submitted these issues and then fixed them in what you're calling my "refactoring". There was refactoring involved, but it was primarily to fix these bugs and make buildout instances possible on Windows. cheers, Chris -- Simplistix - Content Management, Batch Processing & Python Consulting - http://www.simplistix.co.uk
participants (6)
-
Andreas Jung -
Chris Withers -
Eric Steele -
Sylvain Viollon -
Tres Seaver -
yuppie