On May 2, 2007, at 9:36 AM, Uwe Oestermeier wrote:
Jim Fulton <[EMAIL PROTECTED]> on Mittwoch, 2. Mai 2007 at 14:34 Uhr +0100
wrote:
fssync isn't included in releases, so I don't think it matters. I
suggest you *move* these two packages out of the Zope 3 tree to their
own projects. There's n
Jim Fulton <[EMAIL PROTECTED]> on Mittwoch, 2. Mai 2007 at 14:34 Uhr +0100
wrote:
>fssync isn't included in releases, so I don't think it matters. I
>suggest you *move* these two packages out of the Zope 3 tree to their
>own projects. There's no need, IMO, to leave externals behind.
There ar
On May 2, 2007, at 3:00 AM, Uwe Oestermeier wrote:
...
Therefore I propose to postpone the release of zope.fssync until
the next
release cycle.
fssync isn't included in releases, so I don't think it matters. I
suggest you *move* these two packages out of the Zope 3 tree to their
own pro
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 pro
Hi All,
I'm still working on zope.fssync and zope.app.fssync. 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
