The thread about Collections Alpha release to Maven Central got me thinking.

So long as an Alpha release is only used for testing/local use, it
does not matter where it is published.

The problem comes if the Alpha release becomes a dependency of another
product which is then released.

So how do we stop that from happening?

Documentation helps, but some people ignore documentation.

Just wondering if it would be possible to incorporate some kind of
time-limit in the library, so that it stops working after a certain
date?

I've no idea if that is feasible - and it might cause too much of an
overhead - but perhaps worth investigating.

Obviously it would have to be well documented.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org

Reply via email to