-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi all,
The CMF eggs, even on trunk, still advertise compatibility with Zope
2.10. I believe we had agreed to target Zope 2.12 with trunk - please
correct me if that's wrong. If we do want Zope 2.12 I would like to go
through before the first
Previously Jens Vagelpohl wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi all,
The CMF eggs, even on trunk, still advertise compatibility with Zope
2.10. I believe we had agreed to target Zope 2.12 with trunk - please
correct me if that's wrong. If we do want Zope 2.12 I
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On May 26, 2009, at 10:21 , Wichert Akkerman wrote:
Previously Jens Vagelpohl wrote:
The CMF eggs, even on trunk, still advertise compatibility with Zope
2.10. I believe we had agreed to target Zope 2.12 with trunk - please
correct me if that's
Jens Vagelpohl wrote:
On May 26, 2009, at 10:21 , Wichert Akkerman wrote:
Previously Jens Vagelpohl wrote:
The CMF eggs, even on trunk, still advertise compatibility with Zope
2.10. I believe we had agreed to target Zope 2.12 with trunk - please
correct me if that's wrong. If we do want Zope
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On May 26, 2009, at 11:20 , Hanno Schlichting wrote:
I'm guessing you are not aware that there already is a hard
dependency
in CMFDefault. In essence, I would not be setting a new policy, I
would document the current situation.
Why doesn't
Previously Jens Vagelpohl wrote:
However, I'd still like to bring up the question of officially
supported Zope releases for CMF 2.2.x. Speaking for me personally, I
develop CMF trunk against Zope trunk (there's that nifty CMF.buildout
package that makes this easy), and it's becoming a
