Current stability of M8

[Andre Paradis <an...@versalys.com>]

Hi,

I'd like to know what is the level of stability of the 
current slide release (M8).

Also, when moving files between two collections, the files 
are logically moved from one collection to the other.  But 
physically on disk, the source file remains there.

So when one try to put the same file name in the source 
collection, we get an error because the file is present on disk.

Is this a correct behavior?  do we have to explicitly delete 
the file after a move command?

Thanks

Andre Paradis

Re: Current stability of M8

[Remy Maucherat <re...@apache.org>]

> I'd like to know what is the level of stability of the
> current slide release (M8).

As a whole, it's not feature complete, so it can be considered alpha
software.

> Also, when moving files between two collections, the files
> are logically moved from one collection to the other.  But
> physically on disk, the source file remains there.
>
> So when one try to put the same file name in the source
> collection, we get an error because the file is present on disk.
>
> Is this a correct behavior?  do we have to explicitly delete
> the file after a move command?

I've reproduced that problem using the file content store. It appears to be
quite random, and it could come from file locking issues.
The JDBC content store seems to run fine.

Remy