Re: [Zope3-dev] Re: Removed zope.security 3.4b4

2007-08-18 Thread Darryl Cousins
Hi, On Sat, 2007-08-18 at 09:16 -0400, Benji York wrote: > Darryl Cousins wrote: > > On Fri, 2007-08-17 at 19:24 +0200, Martijn Faassen wrote: > >> I think my next step is to fix some dependencies for Grok to hard > >> version numbers... > > > > I think that this is a good thing. I recently gave

[Zope3-dev] Re: SVN: zope.location/trunk/setup.py using pypi as homepage instead of svn.zope.org

2007-08-18 Thread Philipp von Weitershausen
Some notes on the release process here: * Please also don't forget to add a changelog entry in README.txt, especially if you're adding features. If there's no README.txt yet, this is a good time to give it one. It should start out with a simple paragraph and have at least one section called "C

[Zope3-dev] ZODB versions / and windows eggs

2007-08-18 Thread Martijn Faassen
Hi there, I noticed the following eggs need a newer binary release for windows: zope.hookable. There's a 3.4.0 release and binary egg is still at 3.4.0a1 zope.i18nmessageid. There's a 3.4.0 release and binary egg is still at 3.4.0a1. Then there's some ZODB confusion: I also noticed that the

[Zope3-dev] setting up application dependencies

2007-08-18 Thread Martijn Faassen
Benji York wrote: Darryl Cousins wrote: On Fri, 2007-08-17 at 19:24 +0200, Martijn Faassen wrote: I think my next step is to fix some dependencies for Grok to hard version numbers... I think that this is a good thing. I recently gave myself quite a bit grief with a careless bin/buildout which

[Zope3-dev] [zope.sendmail] added encryption support

2007-08-18 Thread Andreas Jung
I added encryption support (SSL/TLS) to zope.sendmail on a branch: I would appreciate it if someone could test it against their own SMTP servers since I could test it only against my own SMTP server. Tnx, Andreas pgpCpN92naa

Re: [Zope3-dev] Re: Removed zope.security 3.4b4

2007-08-18 Thread Benji York
Darryl Cousins wrote: On Fri, 2007-08-17 at 19:24 +0200, Martijn Faassen wrote: I think my next step is to fix some dependencies for Grok to hard version numbers... I think that this is a good thing. I recently gave myself quite a bit grief with a careless bin/buildout which broke my applicati