commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Paul Benedict <>
Subject Re: [ALL] Alpha releases - how to stop them becoming a dependency of a released product
Date Fri, 05 Jul 2013 19:27:26 GMT
Don't try to solve how to stop an alpha release from becoming integrated.
If someone does that, there's inherit risk involved. I don't see how this
is any different, per se, a beta or RC release. If you build on unstable
code, the only support advice I'd will get is: upgrade to the latest GA. :-)

On Fri, Jul 5, 2013 at 2: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:

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