Re: [Zope3-dev] Re: NAG NAG NAG (Was: Let's have a bug day -- sort of)
Philipp von Weitershausen wrote: Lennart Regebro wrote: On 8/11/06, Jim Fulton [EMAIL PROTECTED] wrote: :) I really wish some more people would help out -- not just the usual suspects. Well, I as usual oppose the friday bugdays, but that said, I have vacation this week, so this friday would work for me. Thursday or Friday would work for me. Shall I make an announcement so that everybody joins in (perhaps the Zope 2/Five guys also want to particpate)? As for the goal, I suggest we try to have a Zope 3.3 release candidate by the end of that bug day. I'll be making another beta release this weekend, if no one objects. The first beta is really old now and has lots of packaging bugs (a few haven't even been fixed yet, like the missing test.py; I'm on that). So, even though a second beta wouldn't fix all reported bugs, it would at least fix the packaging bugs and a few other ones. I suspect I'll land 3.3beta2 some time Sunday afternoon CEST. Finally! 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 ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
[Zope3-dev] Zope bugday on Thursday
Hi all, we're having a bugday for the Zope June releases this Thursday. Yes, we know it's August. That's why we need YOUR help to get this release out quickly. How can you help? Look at the issue trackers at http://www.zope.org/Collectors and search for bugs of the 'critical' or '3.3 release' category. If you want to work on a particular issue, assign it to yourself and hack away! You won't have to wait till Thursday for that, of course... The goal for this bugday is to have release candidates of Zope 3.3 and 2.10 by the end of the day. See you all on Thursday, Philipp ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
[Zope3-dev] Re: [Zope3-checkins] SVN: Zope3/trunk/src/zope/dublincore/ Dublin Core property to use Dublin Core meta data as simple properties.
Am Montag, 14. August 2006 12:52 schrieb Jürgen Kartnaller: Log message for revision 69463: Dublin Core property to use Dublin Core meta data as simple properties. Changed: A Zope3/trunk/src/zope/dublincore/property.py A Zope3/trunk/src/zope/dublincore/property.txt A Zope3/trunk/src/zope/dublincore/tests/test_property.py Do I understand this change correctly that it obsoletes zope.dublincore.annotatableadapter.partialAnnotatableAdapterFactory? Quote from zope/dublincore/tests/partial.txt which describes the partialAnnotatableAdapterFactory: Sometimes we want to include data in content objects which mirrors one or more Dublin Core fields. In these cases, we want the Dublin Core structures to use the data in the content object rather than keeping a separate value in the annotations typically used. What fields we want to do this with can vary, however, and we may not want the Dublin Core APIs to constrain our choices of field names for our content objects. Should the partialAnnotatableAdapterFactory therefore be removed/deprecated? Regards, Florian ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
[Zope3-dev] Re: [Zope3-checkins] SVN: Zope3/trunk/src/zope/dublincore/ Dublin Core property to use Dublin Core meta data as simple properties.
Florian Lindner wrote: Am Montag, 14. August 2006 12:52 schrieb Jürgen Kartnaller: Log message for revision 69463: Dublin Core property to use Dublin Core meta data as simple properties. Changed: A Zope3/trunk/src/zope/dublincore/property.py A Zope3/trunk/src/zope/dublincore/property.txt A Zope3/trunk/src/zope/dublincore/tests/test_property.py Do I understand this change correctly that it obsoletes zope.dublincore.annotatableadapter.partialAnnotatableAdapterFactory? It definitely doesn't obsolete the existing implementation. DCProperty is the other way around. DCProperty allows access to DC meta data via simple properties. partialAnnotatableAdapterFactory allows access via DC meta data to content properties. Quote from zope/dublincore/tests/partial.txt which describes the partialAnnotatableAdapterFactory: Sometimes we want to include data in content objects which mirrors one or more Dublin Core fields. In these cases, we want the Dublin Core structures to use the data in the content object rather than keeping a separate value in the annotations typically used. What fields we want to do this with can vary, however, and we may not want the Dublin Core APIs to constrain our choices of field names for our content objects. Should the partialAnnotatableAdapterFactory therefore be removed/deprecated? No Regards Jürgen ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
Re: [Zope3-dev] Re: New beta releases tonight
Philipp von Weitershausen wrote at 2006-8-13 23:09 +0200: ... forker.shutdown_zeo_server(adminaddr) File src/ZEO/tests/forker.py, line 182, in shutdown_zeo_server s.connect(adminaddr) File string, line 1, in connect error: (22, 'Invalid argument') Looks as if adminaddr where not a tuple consisting of a string and an integer. -- Dieter ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
Re: [Zope3-dev] Re: [Zope3-checkins] SVN: Zope3/trunk/src/zope/dublincore/ Dublin Core property to use Dublin Core meta data as simple properties.
On 8/14/06, Jürgen Kartnaller [EMAIL PROTECTED] wrote: It definitely doesn't obsolete the existing implementation. DCProperty is the other way around. DCProperty allows access to DC meta data via simple properties. I agree that these should co-exist. I'm not sure just what motivated DCProperty, but it's clearly different from the partial adapter. The motivation for theh partial adapter was that for some content, some of the data fields correspond directly to DC elements. For those, we wanted the DC adapter to use the fields instead of storing the information outside the object. -Fred -- Fred L. Drake, Jr.fdrake at gmail.com Every sin is the result of a collaboration. --Lucius Annaeus Seneca ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
