Hi there, I was in too much of a good mood while having some vacation. So I thought I need more work to do :) I'd like to step up as the release manager for Zope2 for the 2.12 and 2.13 (trunk) releases. I've gotten an overwhelmingly positive response to this proposal from the Zope Foundation board. The ZF board was discussing a general release manager process. This discussion will become obsolete, should nobody in the Zope2 developer community have significant objections against my proposal. Unless there is a real need for it, the Zope Foundation will continue to stay out of direct decisions on the development process. Q&A Who am I? I'm going to assume everyone on this list knows me by now. Should you have any questions, please feel free to ask. You know this is Zope2 and not Plone? Indeed. I hope I have shown in the past, that I'm able to distinguish between the two. And what is appropriate and sensible for Zope2 with its many different consumers. Plone might be a major consumer of Zope2, but it's not the only one. Since I only use Zope2 as a base for Plone, I do have a certain bias. Wait, you say 2.12 and 2.13, what about 2.11 and before? Sorry, I have to pick my playground. The non-eggified Zope2 releases are very different in their release procedures. I find that process to be tedious and no fun at all, so I'm not going to spent my free time on it. Should nobody else step up to act as a release manager for those releases, they will be unsupported. Are you a new Andreas? Nobody can replace Andreas and the tremendous amount of time and dedication he has shown. Personally I do not care about evangelizing Zope2 or helping out end-users on mailing lists amongst others. So no, I'm not going to do all the work Andreas did. I'm only here to help out as a release manager, whose job it is to get stable releases out. I do read the developers mailing lists and watch the bug trackers, I don't read any users mailing list or see it as my job to fix or respond to every bug anyone reports. What about that Plone release manager position? I am currently the release manager for Plone 5. We have clarified the overall roadmap for Plone 5, and we aren't going to work on any of the formal release parts for the next 12 months or longer. The current focus is on the Plone 4.x release series, where Eric Steele serves as the release manager. So while I'm going to keep my post as a Plone release manager, it currently doesn't involve any time commitments. What about Zope 2.14 or beyond? Nobody knows yet. We will see once we get there. My formal commitment is for 2.12 and 2.13. Are you insane? Maybe a little bit. But seriously if anyone knows anyone else who would be interested in this job, speak up. I haven't seen anyone else since Andreas stepped down. And I happen to work for a company which is 100% dependent on Zope / Plone for their income stream. While I'm doing this in my spare time, I do have a very real need for Zope2 releases. I'm planning to make a 2.12.4 release on Easter Monday (April 5). You have until then to ask questions and complain :) Hanno
Am 31.03.2010, 14:39 Uhr, schrieb Hanno Schlichting <hanno@hannosch.eu>:
I'm planning to make a 2.12.4 release on Easter Monday (April 5). You have until then to ask questions and complain
Hi Hanno, great that you'll be Release Manager. I only have questions on the forthcoming release - a summary of the proposed changes / bugfixes for us to moan about! ;-) Charlie -- Charlie Clark Managing Director Clark Consulting & Research German Office Helmholtzstr. 20 Düsseldorf D- 40215 Tel: +49-211-600-3657 Mobile: +49-178-782-6226
On Wed, Mar 31, 2010 at 2:48 PM, Charlie Clark <charlie.clark@clark-consulting.eu> wrote:
great that you'll be Release Manager. I only have questions on the forthcoming release - a summary of the proposed changes / bugfixes for us to moan about! ;-)
We release whatever is on the stable branch, as seen at http://svn.zope.org/Zope/branches/2.12/doc/CHANGES.rst?view=markup You moan about things when they get checked in. Otherwise silence is consent. Unless I'll use my dictator power for a release of course ;-) Hanno
Am 31.03.2010, 14:59 Uhr, schrieb Hanno Schlichting <hanno@hannosch.eu>:
We release whatever is on the stable branch, as seen at http://svn.zope.org/Zope/branches/2.12/doc/CHANGES.rst?view=markup You moan about things when they get checked in. Otherwise silence is consent. Unless I'll use my dictator power for a release of course
Looks all good to me. - Restore ability to traverse to 'macros' on template-based browser views I've probably been struggling with this on my current project. What are the tell-tale signs? Don't see a bug number and a quick search of the mailing list throws up nothing. Charlie -- Charlie Clark Managing Director Clark Consulting & Research German Office Helmholtzstr. 20 Düsseldorf D- 40215 Tel: +49-211-600-3657 Mobile: +49-178-782-6226
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hanno, thanks a lot for jumping on the Zope 2 boat. I can not think of any other person being better suited for the new Zope 2 releases than Hanno especially because the Plone and Zope 2 project will leverage from each other. Good luck! Andreas Hanno Schlichting wrote:
Hi there,
I was in too much of a good mood while having some vacation. So I thought I need more work to do :)
I'd like to step up as the release manager for Zope2 for the 2.12 and 2.13 (trunk) releases.
I've gotten an overwhelmingly positive response to this proposal from the Zope Foundation board. The ZF board was discussing a general release manager process. This discussion will become obsolete, should nobody in the Zope2 developer community have significant objections against my proposal. Unless there is a real need for it, the Zope Foundation will continue to stay out of direct decisions on the development process.
Q&A
Who am I?
I'm going to assume everyone on this list knows me by now. Should you have any questions, please feel free to ask.
You know this is Zope2 and not Plone?
Indeed. I hope I have shown in the past, that I'm able to distinguish between the two. And what is appropriate and sensible for Zope2 with its many different consumers. Plone might be a major consumer of Zope2, but it's not the only one. Since I only use Zope2 as a base for Plone, I do have a certain bias.
Wait, you say 2.12 and 2.13, what about 2.11 and before?
Sorry, I have to pick my playground. The non-eggified Zope2 releases are very different in their release procedures. I find that process to be tedious and no fun at all, so I'm not going to spent my free time on it. Should nobody else step up to act as a release manager for those releases, they will be unsupported.
Are you a new Andreas?
Nobody can replace Andreas and the tremendous amount of time and dedication he has shown. Personally I do not care about evangelizing Zope2 or helping out end-users on mailing lists amongst others. So no, I'm not going to do all the work Andreas did. I'm only here to help out as a release manager, whose job it is to get stable releases out. I do read the developers mailing lists and watch the bug trackers, I don't read any users mailing list or see it as my job to fix or respond to every bug anyone reports.
What about that Plone release manager position?
I am currently the release manager for Plone 5. We have clarified the overall roadmap for Plone 5, and we aren't going to work on any of the formal release parts for the next 12 months or longer. The current focus is on the Plone 4.x release series, where Eric Steele serves as the release manager. So while I'm going to keep my post as a Plone release manager, it currently doesn't involve any time commitments.
What about Zope 2.14 or beyond?
Nobody knows yet. We will see once we get there. My formal commitment is for 2.12 and 2.13.
Are you insane?
Maybe a little bit. But seriously if anyone knows anyone else who would be interested in this job, speak up. I haven't seen anyone else since Andreas stepped down. And I happen to work for a company which is 100% dependent on Zope / Plone for their income stream. While I'm doing this in my spare time, I do have a very real need for Zope2 releases.
I'm planning to make a 2.12.4 release on Easter Monday (April 5). You have until then to ask questions and complain :)
Hanno _______________________________________________ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
- -- ZOPYX Limited \ zopyx group Charlottenstr. 37/1 \ The full-service network for your D-72070 Tübingen \ Python, Zope and Plone projects www.zopyx.com, info@zopyx.com \ www.zopyxgroup.com - ------------------------------------------------------------------------ E-Publishing, Python, Zope & Plone development, Consulting -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkuzVyIACgkQCJIWIbr9KYxMtQCeMnG0GBG86Sk3QcTD5tGqfQYV E5oAn1amaO3AfN7rWfuOkBFPc+2m/kjQ =7iYf -----END PGP SIGNATURE-----
Op 31-03-10 14:39, Hanno Schlichting schreef:
Hi there,
I was in too much of a good mood while having some vacation. So I thought I need more work to do :)
I'd like to step up as the release manager for Zope2 for the 2.12 and 2.13 (trunk) releases.
This is great news. Thanks, Hanno! Maurits
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hanno Schlichting wrote:
Hi there,
I was in too much of a good mood while having some vacation. So I thought I need more work to do :)
I'd like to step up as the release manager for Zope2 for the 2.12 and 2.13 (trunk) releases.
I've gotten an overwhelmingly positive response to this proposal from the Zope Foundation board. The ZF board was discussing a general release manager process. This discussion will become obsolete, should nobody in the Zope2 developer community have significant objections against my proposal. Unless there is a real need for it, the Zope Foundation will continue to stay out of direct decisions on the development process.
Q&A
Who am I?
I'm going to assume everyone on this list knows me by now. Should you have any questions, please feel free to ask.
You know this is Zope2 and not Plone?
Indeed. I hope I have shown in the past, that I'm able to distinguish between the two. And what is appropriate and sensible for Zope2 with its many different consumers. Plone might be a major consumer of Zope2, but it's not the only one. Since I only use Zope2 as a base for Plone, I do have a certain bias.
Wait, you say 2.12 and 2.13, what about 2.11 and before?
Sorry, I have to pick my playground. The non-eggified Zope2 releases are very different in their release procedures. I find that process to be tedious and no fun at all, so I'm not going to spent my free time on it. Should nobody else step up to act as a release manager for those releases, they will be unsupported.
Are you a new Andreas?
Nobody can replace Andreas and the tremendous amount of time and dedication he has shown. Personally I do not care about evangelizing Zope2 or helping out end-users on mailing lists amongst others. So no, I'm not going to do all the work Andreas did. I'm only here to help out as a release manager, whose job it is to get stable releases out. I do read the developers mailing lists and watch the bug trackers, I don't read any users mailing list or see it as my job to fix or respond to every bug anyone reports.
What about that Plone release manager position?
I am currently the release manager for Plone 5. We have clarified the overall roadmap for Plone 5, and we aren't going to work on any of the formal release parts for the next 12 months or longer. The current focus is on the Plone 4.x release series, where Eric Steele serves as the release manager. So while I'm going to keep my post as a Plone release manager, it currently doesn't involve any time commitments.
What about Zope 2.14 or beyond?
Nobody knows yet. We will see once we get there. My formal commitment is for 2.12 and 2.13.
Are you insane?
Maybe a little bit. But seriously if anyone knows anyone else who would be interested in this job, speak up. I haven't seen anyone else since Andreas stepped down. And I happen to work for a company which is 100% dependent on Zope / Plone for their income stream. While I'm doing this in my spare time, I do have a very real need for Zope2 releases.
I'm planning to make a 2.12.4 release on Easter Monday (April 5). You have until then to ask questions and complain :)
An enthusiastic +1 from me: I think you are an ideal candidate for the job. 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 iEYEARECAAYFAkuzZSsACgkQ+gerLs4ltQ7lKgCdFc0gLLMRen1+OsARfge6nCtO jKEAoIDQ+ipXNheOGWNFLyYzC9MuGTWT =1ld2 -----END PGP SIGNATURE-----
On 31/03/10 17:07, Tres Seaver wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Hanno Schlichting wrote:
<snip>
I'm planning to make a 2.12.4 release on Easter Monday (April 5). You have until then to ask questions and complain :)
An enthusiastic +1 from me: I think you are an ideal candidate for the job.
Tres Seaver
Same enthusiastic support and thanks from me ! -- Godefroid Chapelle (aka __gotcha) http://bubblenet.be
On 3/31/10 8:39 AM, Hanno Schlichting wrote:
Hi there,
I was in too much of a good mood while having some vacation. So I thought I need more work to do :)
I'd like to step up as the release manager for Zope2 for the 2.12 and 2.13 (trunk) releases.
Thanks for doing this Hanno. -- Chris McDonough Agendaless Consulting, Fredericksburg VA The repoze.bfg Web Application Framework Book: http://bfg.repoze.org/book
Hanno Schlichting wrote:
Hi there,
I was in too much of a good mood while having some vacation. So I thought I need more work to do :)
I'd like to step up as the release manager for Zope2 for the 2.12 and 2.13 (trunk) releases.
Sucke^H^H^H^H^H Good man! Very happy you're doing this. I was going to try to prod you into doing this, but thought it'd be cruel. You're the perfect person for the job.
I'm planning to make a 2.12.4 release on Easter Monday (April 5). You have until then to ask questions and complain :)
Great news. There are some important bug fixes in there. What's the next step? I'd love to see some roadmapping ala that you did for Plone 5, in particular to discuss our WSGI story (which I'm interested in helping out with if others can help too). Martin -- Author of `Professional Plone Development`, a book for developers who want to work with Plone. See http://martinaspeli.net/plone-book
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Martin Aspeli wrote:
What's the next step? I'd love to see some roadmapping ala that you did for Plone 5, in particular to discuss our WSGI story (which I'm interested in helping out with if others can help too).
FWIW, I'm scheduled to sprint on finishing my cleanup of ZPublisher.WSGIResponse with the WebLion guys at or around PSE in May. 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 iEYEARECAAYFAkuz/PEACgkQ+gerLs4ltQ5QSgCffb6Rzr9KUccbXszw3zUGoNgz 2osAnAuSXjLzz4vMAOUGMq+W9fCkUu/6 =M+wo -----END PGP SIGNATURE-----
Tres Seaver wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Martin Aspeli wrote:
What's the next step? I'd love to see some roadmapping ala that you did for Plone 5, in particular to discuss our WSGI story (which I'm interested in helping out with if others can help too).
FWIW, I'm scheduled to sprint on finishing my cleanup of ZPublisher.WSGIResponse with the WebLion guys at or around PSE in May.
That's awesome! :-) Is there a list somewhere about what remains of this work, i.e. what's broken and what features are missing? Martin -- Author of `Professional Plone Development`, a book for developers who want to work with Plone. See http://martinaspeli.net/plone-book
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Martin Aspeli wrote:
Tres Seaver wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Martin Aspeli wrote:
What's the next step? I'd love to see some roadmapping ala that you did for Plone 5, in particular to discuss our WSGI story (which I'm interested in helping out with if others can help too). FWIW, I'm scheduled to sprint on finishing my cleanup of ZPublisher.WSGIResponse with the WebLion guys at or around PSE in May.
That's awesome! :-)
Is there a list somewhere about what remains of this work, i.e. what's broken and what features are missing?
Nope: the thing I know of for sure is that some images bork their content length (like ZMI icons) under WSGI. 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 iEYEARECAAYFAku0xKQACgkQ+gerLs4ltQ5uegCfRlz9maTe4NhqJYFVGJSP+QFT CtUAnjKhD6ILzln9Fk9BRhKOP2c/RUs7 =9UPf -----END PGP SIGNATURE-----
On Thu, Apr 1, 2010 at 03:55, Tres Seaver <tseaver@palladion.com> wrote:
FWIW, I'm scheduled to sprint on finishing my cleanup of ZPublisher.WSGIResponse with the WebLion guys at or around PSE in May.
Cleanup, really? Since the repoze effort reimplemented the publisher I had the feeling that the old experimental WSGI support was trash and needed to be thrown out. -- Lennart Regebro: Python, Zope, Plone, Grok http://regebro.wordpress.com/ +33 661 58 14 64
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Lennart Regebro wrote:
On Thu, Apr 1, 2010 at 03:55, Tres Seaver <tseaver@palladion.com> wrote:
FWIW, I'm scheduled to sprint on finishing my cleanup of ZPublisher.WSGIResponse with the WebLion guys at or around PSE in May.
Cleanup, really? Since the repoze effort reimplemented the publisher I had the feeling that the old experimental WSGI support was trash and needed to be thrown out.
The repoze.zope2 reimplementation was a bandaid: we would like to fix the actual underlying issues. I went down the rabbit hole of cleaning it up over Christmas break: $ svn log --stop-on-copy \ svn+ssh://svn.zope.org/repos/main/Zope/branches/tseaver-fix_wsgi/ As you can see from the diffs, I gut sidetracked writing tests for HTTPResponse, since I needed to make changes to it to do the WSGI fix, and it was effectively untested. 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 iEYEARECAAYFAku0pW4ACgkQ+gerLs4ltQ6p9gCfbfOp1KCGF+cnUQWW5fAWC7Li NVkAn2ke0U959msfP6aE251USJVhIaM3 =3ZP4 -----END PGP SIGNATURE-----
On Thu, Apr 1, 2010 at 15:53, Tres Seaver <tseaver@palladion.com> wrote:
As you can see from the diffs, I gut sidetracked writing tests for HTTPResponse, since I needed to make changes to it to do the WSGI fix, and it was effectively untested.
Very cool!
On Thu, Apr 1, 2010 at 18:24, Lennart Regebro <regebro@gmail.com> wrote:
On Thu, Apr 1, 2010 at 15:53, Tres Seaver <tseaver@palladion.com> wrote:
As you can see from the diffs, I gut sidetracked writing tests for HTTPResponse, since I needed to make changes to it to do the WSGI fix, and it was effectively untested.
Very cool!
I vaguely seem to remember that I discovered that it in practice was single-threaded, which of course is a disaster. Also there was no streaming support, and the configuration assumed that the WSGI server you were using was Twisted, but that is probably one of the least tricky things to fix. In fact the whole point at that times was to be able to use Twisted, and WSGI was only one way there. This obviously has changed, now WSGI is the goal. -- Lennart Regebro: Python, Zope, Plone, Grok http://regebro.wordpress.com/ +33 661 58 14 64
Lennart Regebro wrote:
On Thu, Apr 1, 2010 at 18:24, Lennart Regebro<regebro@gmail.com> wrote:
On Thu, Apr 1, 2010 at 15:53, Tres Seaver<tseaver@palladion.com> wrote:
As you can see from the diffs, I gut sidetracked writing tests for HTTPResponse, since I needed to make changes to it to do the WSGI fix, and it was effectively untested. Very cool!
I vaguely seem to remember that I discovered that it in practice was single-threaded, which of course is a disaster.
Eeek. Any idea how that happened? Presumably, thread control in a WSGI scenario would be up to the WSGI web server, not Zope 2.
Also there was no streaming support
I implemented IStreamIterator support in repoze.zope2; it's actually pretty easy, since a stream iterator is an iterable, just like a WSGI response. I think you can just chuck it back. The only thing to watch out for is that you don't accidentally unwind it anywhere.
, and the configuration assumed that the WSGI server you were using was Twisted, but that is probably one of the least tricky things to fix. In fact the whole point at that times was to be able to use Twisted, and WSGI was only one way there. This obviously has changed, now WSGI is the goal.
I think testing with the Paste server is probably the best idea. Martin -- Author of `Professional Plone Development`, a book for developers who want to work with Plone. See http://martinaspeli.net/plone-book
On Fri, Apr 2, 2010 at 05:34, Martin Aspeli <optilude+lists@gmail.com> wrote:
Eeek. Any idea how that happened? Presumably, thread control in a WSGI scenario would be up to the WSGI web server, not Zope 2.
Which may be the case here to, ie, it was the Twisted integration that was single threaded. I don't remember the details any more actually. I also don't remember how the thread support with ZServer works.
I implemented IStreamIterator support in repoze.zope2; it's actually pretty easy, since a stream iterator is an iterable, just like a WSGI response. I think you can just chuck it back. The only thing to watch out for is that you don't accidentally unwind it anywhere.
Sounds good. -- Lennart Regebro: Python, Zope, Plone, Grok http://regebro.wordpress.com/ +33 661 58 14 64
participants (10)
-
Andreas Jung -
Charlie Clark -
Chris McDonough -
Godefroid Chapelle -
Hanno Schlichting -
Lennart Regebro -
Martin Aspeli -
Maurits van Rees -
Simon Michael -
Tres Seaver