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 Co
Am 05.07.2013 21:27, schrieb Paul Benedict:
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'
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. :-)
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
