On 11.03.2006 00:20, Antonio Gallardo wrote:
I'm reopening this issue just for trunk:
AbstractCachingProcessingPipeline locking feature *must* be ported to
trunk, and this bugfix as well.
IMHO given the current code base, the bug has already been fixed
everywhere. The bug was introduced with the newly "locking feature".
Note the bug was only for 2.1.x-dev and since the code has not been
merged in 2.2 yet, actually it does not apply for 2.2. When the trunk
will be synchronized, this bug will be automatically fixed there too,
hence the bug has never been nor will appear in 2.2.
wdyt?
+1 I agree. There is another "to be synced" document somewhere.
Jörg
