[Zope-dev] Zope Tests: 15 OK, 1 Failed
Summary of messages to the zope-tests list. Period Mon May 17 12:00:00 2010 UTC to Tue May 18 12:00:00 2010 UTC. There were 16 messages: 6 from Zope Tests, 9 from ccomb at free.fr, 1 from ct at gocept.com. Test failures - Subject: FAILED: Repository policy check found errors in 583 projects From: ct at gocept.com Date: Mon May 17 21:18:16 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-May/014475.html Tests passed OK --- Subject: OK : Zope-2.10 Python-2.4.6 : Linux From: Zope Tests Date: Mon May 17 21:29:46 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-May/014476.html Subject: OK : Zope-2.11 Python-2.4.6 : Linux From: Zope Tests Date: Mon May 17 21:31:46 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-May/014477.html Subject: OK : Zope-2.12 Python-2.6.5 : Linux From: Zope Tests Date: Mon May 17 21:33:46 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-May/014478.html Subject: OK : Zope-2.12-alltests Python-2.6.5 : Linux From: Zope Tests Date: Mon May 17 21:35:46 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-May/014479.html Subject: OK : Zope-trunk Python-2.6.5 : Linux From: Zope Tests Date: Mon May 17 21:37:46 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-May/014480.html Subject: OK : Zope-trunk-alltests Python-2.6.5 : Linux From: Zope Tests Date: Mon May 17 21:39:46 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-May/014481.html Subject: OK : BlueBream template / Python2.4.6 32bit linux From: ccomb at free.fr Date: Mon May 17 22:00:51 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-May/014482.html Subject: OK : BlueBream template / Python2.6.4 32bit linux From: ccomb at free.fr Date: Mon May 17 22:00:54 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-May/014484.html Subject: OK : BlueBream template / Python2.5.2 32bit linux From: ccomb at free.fr Date: Mon May 17 22:00:55 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-May/014483.html Subject: OK : BlueBream template / Python2.7b2 32bit linux From: ccomb at free.fr Date: Mon May 17 22:00:56 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-May/014485.html Subject: OK : ZTK 1.0dev / Python2.4.6 Linux 32bit From: ccomb at free.fr Date: Tue May 18 00:05:40 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-May/014486.html Subject: OK : ZTK 1.0dev / Python2.5.2 Linux 32bit From: ccomb at free.fr Date: Tue May 18 00:05:44 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-May/014487.html Subject: OK : ZTK 1.0dev / Python2.6.4 Linux 32bit From: ccomb at free.fr Date: Tue May 18 00:06:06 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-May/014488.html Subject: OK : Zope 3.4.1 KGS / Python2.4.6 32bit linux From: ccomb at free.fr Date: Tue May 18 00:26:26 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-May/014489.html Subject: OK : Zope 3.4.1 KGS / Python2.5.2 32bit linux From: ccomb at free.fr Date: Tue May 18 00:50:35 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-May/014490.html ___ 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 )
[Zope-dev] ZTK release team - kickoff meeting - delayed summary
Hi there, I've been slacking and forgot to post the summary of the first ZTK release team meeting. Here it is. I'll put it into SVN into the ztk-docs area as well. Cheers, Hanno ZTK meeting - 2010-05-06 Attendance -- ccomb, j-w, hannosch Agenda -- - No fixed agenda, this is a kick-off meeting. Discussion -- Communication - We'll use the zope-dev mailing list for our discussions and no separate list Our role - We see ourselves as representatives of communities that make use of the ZTK - We should ensure stable releases of the ZTK, which are useful to our projects not more and not less Release outcome - Should produce a http://download.zope.org/ztk/release/1.1 with a ztk.cfg in it and a the zopeapp.cfg (for as long as it exists) in it. - Nice to have: an index (for easy_install people) - Should have some documentation site stating changes (http://docs.zope.org/zopetoolkit/releases/overview-trunk.html) Release policies - At first manual releases (x.y.Z), automate the process to generate the bugfix releases later. We need to make sure to release only versions sets for which all tests passed. - ztk x.y.z. releases, stable package list per release - a ztk minor release per month would be ok - a ztk major release when one of the consumers projects needs it. - backward compatibility breaking only happens in X.y.z that means, if we have a zope.component 4.0.0, it will be part of ZTK 2.0 or 3.0 - generally upstream releases happen in a 6-12 month interval, so the same timeline makes sense for ZTK releases Tasks - - We want 64bit Linux and Windows tests for the ZTK. j-w is bugging janjaap to create those. Maybe contact ccomb for adding slaves to afpy [j-w] - Make sure we have a buildbot testing the ZTK releases (and not SVN) [ccomb] Open points --- - Look at Tres's list of packages in all three frameworks, decide on a way to drop things from the initial ZTK set and on a process for the future. - Look at and update http://docs.zope.org/zopetoolkit/about/coreextra.html for adding/removing policies, probably have a deprecated.cfg file - Decide on process for new feature versions and the process for going from 1.1.0 alpha to a final Next meeting 2010-05-18, 14:00 to 15:00 UTC before the zope-dev meeting, in #zope ___ 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 )
[Zope-dev] where to annouce?
Hello, Does anyone have a list where to announce something like a KGS 3.4.1 release? -- Best regards, Adam GROSZER mailto:agros...@gmail.com -- Quote of the day: We can conceive of a world in which God corrected the results of abuse of free will by His creatures: so that a wooden beam became soft as grass when used as a weapon... But such a world would be one in which wrong actions were impossible, and therefore, freedom of the will would be void. - C.S. Lewis ___ 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 )
Re: [Zope-dev] where to annouce?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Adam GROSZER wrote: Hello, Does anyone have a list where to announce something like a KGS 3.4.1 release? The zope-announce list? :-) Andreas - -- ZOPYX Limited | zopyx group Charlottenstr. 37/1 | The full-service network for Zope Plone D-72070 Tübingen| Produce Publish www.zopyx.com | www.produce-and-publish.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/ iEYEARECAAYFAkvysN8ACgkQCJIWIbr9KYyN4gCgxiKsnSZ9HjTv44S5cKPMbToo lRUAnjwxAVUMjyQ7remoURcKkvifZYpg =VhOB -END PGP SIGNATURE- attachment: lists.vcf___ 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 )
Re: [Zope-dev] ZTK release team - kickoff meeting - delayed summary
Hanno Schlichting wrote: - Look at Tres's list of packages in all three frameworks, decide on a way to drop things from the initial ZTK set and on a process for the future. As long as things are not dropped immediately. Even though Grok 1.2 might not need foo.bar, transition support might mean it requires it still for those people who are porting over existing projects. Note also that Tres' list is not exactly accurate as it comes to Grok, as Tres assumed that information about deprecation in Grok's setup.py was actually correct. :). Please be careful with that. I think Grok's upcoming 1.2 list will be better. - Look at and update http://docs.zope.org/zopetoolkit/about/coreextra.html for adding/removing policies, probably have a deprecated.cfg file A deprecated.cfg would be a way to support this. Most of zopeapp.cfg could eventually go into deprecated.cfg. The tricky question is what to do those things in zopeapp.cfg which won't be deprecated any time soon. An example is zope.app.wsgi. Should it stay in zopeapp.cfg? we could rename it to zope.wsgi and move it into the ztk.cfg too. You can then argue that since Zope 2 doesn't use it, it shouldn't be in the ZTK, but there are already packages in the ZTK that aren't used by Zope 2. If we moved the four to six things out of zopeapp.cfg over into ztk.cfg (and deprecated the rest) might that be an acceptable extra burden for those who don't use these packages? Eventually of course we'd even want to dump deprecated stuff completely so that we don't need to maintain it at all anymore. We can even move that code into a subdir in SVN and put markers in pypi. You'd need a clear procedure for that too. Regards, Martijn ___ 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 )
[Zope-dev] Removing URL-based suppression of SiteAccess controls
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 In lp:142868 [1], Jamie Heilmann makes what seems to me to be a good case for removing the current feature which allows suppression Zope2 access rules and site roots via adding tokens to the URL. I find the argument convincing, in spite of having used the feature to get passed a broken site access rule at more than one time in the past. In essence, the feature is a convenience for those who *could* get to the filessystem and restart the server with the equivalent environment variables, but a jailbreak for those who could not. Can anyone presetn a credible defense of the feature? If so, please follow up to the Launchpad issue. I plan to remove the URL based suppression (but ont the part based on os.environ) by the end of the week, unless folks point out issues I have mised. []1 https://bugs.launchpad.net/bugs/142878 Tres. - -- === Tres Seaver +1 540-429-0999 tsea...@palladion.com Palladion Software Excellence by Designhttp://palladion.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkvzPcwACgkQ+gerLs4ltQ6wFwCgtUwYRqXWp5FrBzHFM6lmN+1C IsIAoMd8Vrvxasef5JTcbRO3rsgehKS3 =1zlI -END PGP SIGNATURE- ___ 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 )
