Re: [Zope3-dev] Cleaning up the widget mess a little bit: bug or feature
Hi again, Gary Poster wrote: > I don't have a very strong feeling about it, but lean towards "bug > fix". It didn't break any of our code (or at least any of our > tests :-) ) so it seems safe from my perspective. I was trying to apply the patch to the 3.3 branch and noticed that the patch isn't compatible, as it requires a restructuring that happened on the trunk a while ago. This refactoring (r70331) introduces a very small feature, but the broken behaviour (trying to put anything into _toFormValue) exists in the old variant as well. I'd both apply r70331 and r71548 to 3.3 and 3.2 then. 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
Re: [Zope3-dev] Issue 712: Bug or feature?
On Dec 18, 2006, at 2:27 PM, Christian Theune wrote: Can somebody help me classify this issue? http://www.zope.org/Collectors/Zope3-dev/721 I'd consider it a bug and change my original target of 3.4 to include it as a bugfix in 3.3 (and a backport to 3.2). But I smell that there might be disagreement this not being a bug but a feature and then only add it to 3.4. Thanks for some feedback! 'submitted' cleanup is a bugfix. I'll also claim that the rest is a bugfix, because of the "not valid XHTML" bit, but it does feel more questionable. I say backport it if noone complains soon. :-) Thanks! Gary ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
Re: [Zope3-dev] Removing SSL/SSH-Keys from Skeleton
Hey Michael, Michael Kerrin wrote: > Suppose I could merge some of the changes that from that branch to get > rid of ssh_* and sftp code which should be independent of any twisted > upgrade. Then a SSL cleanup is also independent of an upgrade, come to > think about it. Did you have any chance to look into this? I also guess that the twisted upgrade could be documented on the road map for Zope 3.4 so everybody knows that this is currently happening and maybe someone wants to join you. Want to put a short page in there? 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] On the road to Zope 3.4
Hi, I've updated the roadmap for Zope 3.4 a bit to start reflecting what I remembered people said they wanted to see. I've identified four larger pieces of work: * EggificationOfZopePackages (turn Zope into smaller pieces by using eggs) * [ZopeAsABuildout]? (pull the smaller pieces together again using zc.buildout) * SpringCleaning07 (remove unmaintained, undistributed components from zope.app) * BlobIntegration I've written up something for the spring cleaning and the blob integration as a first draft. Any additions/comments are welcome! I'd like to get some feedback on the eggification, as the proposal IMHO needs some work on the goals that should be achieved within the scope and how it relates to zc.buildout. (Is turning each package into a buildout within the scope or not?) When reading through earlier mailing list posts, I noticed that Jim wanted Zope 3.4 to be based on zc.buildout. I think this is a good idea because it gives us the mechanism to get the eggs back into the distribution. I don't know what needs to be done on the Zope side and/or the buildout-side though. Can someone help out with writing a couple of sentences there? 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
Re: [Zope3-dev] Cleaning up the widget mess a little bit: bug or feature
On Dec 14, 2006, at 7:55 AM, Christian Theune wrote: Hi, ... Zagy and I fixed this issue, by making the methods "_getCurrentValue" and "_getFormValue" use a common method to retrieve the "input value" and handle the case of converting to the "form value" cleanly. However, we are not sure, whether this should be considered a bug or a feature and would like to discuss whether this should be back ported. You can find the change set in r71548. (We documented the change in the 'Bug fixes' section of the CHANGES.txt for now.) I don't have a very strong feeling about it, but lean towards "bug fix". It didn't break any of our code (or at least any of our tests :-) ) so it seems safe from my perspective. Gary ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
[Zope3-dev] Issue 712: Bug or feature?
Can somebody help me classify this issue? http://www.zope.org/Collectors/Zope3-dev/721 I'd consider it a bug and change my original target of 3.4 to include it as a bugfix in 3.3 (and a backport to 3.2). But I smell that there might be disagreement this not being a bug but a feature and then only add it to 3.4. Thanks for some feedback! 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
Re: [Zope3-dev] "Core" topic in Collector
Chris Withers wrote: Jim Fulton wrote: Chris Withers wrote: Jim Fulton wrote: The Zope3 collector isn't actually *that* bad in this respect. IMO, it could do without the topic and version info fields. Topic I'd agree with, but I would have thought version info would be pretty useful? Sure, but it could go in the description along with all of the other information needed to reproduce the problem. I thought the idea of a seperate field was to make it a mandatory dropdown so that at least we know what version of Zope the reporter is using... I have no idea. That's certainly not what exists. Jim -- Jim Fulton mailto:[EMAIL PROTECTED] Python Powered! CTO (540) 361-1714http://www.python.org Zope Corporation http://www.zope.com http://www.zope.org ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
Re: [Zope3-dev] "Core" topic in Collector
Steve Alexander wrote: I'd be happy using launchpad too. The last link points to a discussion that didn't have any decision in the end. I wouldn't go as far as abandoning the old collector data. Then I think we should stick with the current collector unless someone comes forward to do the work of moving the data, or unless we decide we don't need to. ... As many of you know, I'm manager of the Launchpad project at Canonical. I hereby offer the services of a member of the Launchpad team at Canonical to write Collector code if necessary in order to get an export of bugs from the Collector in a format that can be imported into Launchpad, to import said bugs into a demonstration server of Launchpad so we can check that the data conversion is good enough, and to do an actual import into the Launchpad production database, and to do this during January 2007. In return, I want a commitment that we'll use Launchpad for bug tracking for 6 months. (The bug data will be available in a documented XML format if y'all decide that Launchpad isn't for you, and you want to move to something else after this time.) I also want to give the Launchpad developer a single point of contact in the Zope community who will make decisions about any questions around mapping the semantics of Collector issues into Launchpad bugs, or lead discussions on the mailing list about this if necessary. There are a few Launchpad developers in the Zope developer community, so I think there's a good communication channel there. Nonetheless, I would also like to offer the Zope Foundation Board phone and online access to the Canonical 24/7 support office for getting a quick response on any critical issues that are affecting use of Launchpad, while the Zope project is using Launchpad as its bug tracker. I'd appreciate a decision on this offer before Christmas, and preferably sooner, so I can schedule the time before I leave on vacation. Thanks for this very generous offer. We've discussed this on the Zope Foundation Board and we unanimously accept your offer. I assume that this pertains to Zope 3 only. I'd love to move the ZODB issues to Launchpad, but that would require converting at least some of the Zope collector as well. Jim -- Jim Fulton mailto:[EMAIL PROTECTED] Python Powered! CTO (540) 361-1714http://www.python.org Zope Corporation http://www.zope.com http://www.zope.org ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
Re: [Zope3-dev] "Core" topic in Collector
Hi, Chris Withers wrote: > I thought the idea of a seperate field was to make it a mandatory > dropdown so that at least we know what version of Zope the reporter is > using... We can know it without the drop down. Using the drop down would allow us to query for it or to restrict the entries to known/valid values. 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
Re: [Zope3-dev] "Core" topic in Collector
Jim Fulton wrote: Chris Withers wrote: Jim Fulton wrote: The Zope3 collector isn't actually *that* bad in this respect. IMO, it could do without the topic and version info fields. Topic I'd agree with, but I would have thought version info would be pretty useful? Sure, but it could go in the description along with all of the other information needed to reproduce the problem. I thought the idea of a seperate field was to make it a mandatory dropdown so that at least we know what version of Zope the reporter is using... cheers, Chris -- Simplistix - Content Management, Zope & Python Consulting - http://www.simplistix.co.uk ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
