Hey, Am Mittwoch, den 02.05.2007, 09:00 +0200 schrieb Uwe Oestermeier: > Hi All, > > I'm still working on zope.fssync and zope.app.fssync.
Yay! > When I started, I > had the hope to finish this work before the 3.4 release, but as always it > took longer than expected. Now I'm unsure how to proceed. > > I have refactored zope.fssync and zope.app.fssync into two clearly > separated packages: > > - zope.fssync contains now a Python API that has no critical dependencies > on Zope, the ZODB, and the security machinery. > > - zope.app.fssync contains a protected web-based API and special > synchronizers for zope.app content types. > [...] > Therefore I propose to postpone the release of zope.fssync until the > next > release cycle. > > Any comments? This is an excellent example of independent products IMHO. As we approach egg releases you could just go ahead and maintain your own release schedule and your own version numbering with those eggs. I think two eggs, one for zope.fssync and one for zope.app.fssync would be best. 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
Description: Dies ist ein digital signierter Nachrichtenteil
_______________________________________________ Zope3-dev mailing list Zope3email@example.com Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com