commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Gary Gregory <>
Subject Re: [ALL] Alpha releases - how to stop them becoming a dependency of a released product
Date Fri, 05 Jul 2013 19:53:29 GMT
I really do not like the idea of putting a time-bomb in software,
especially coming from us!

This is not a problem for us to solve IMO.

All we need to decide is (1) whether we should release alphas and betas,
and if so, (2) where to release them.

After all, we do not prevent people from using Commons Lang 1.0.


On Fri, Jul 5, 2013 at 3:13 PM, sebb <> wrote:

> 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:
> For additional commands, e-mail:

E-Mail: |
Java Persistence with Hibernate, Second Edition<>
JUnit in Action, Second Edition <>
Spring Batch in Action <>

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message