On Sat, 7 Nov 2015 16:52:21 +0100, Emmanuel Bourg wrote:
A roughly equivalent alternative would be to release beta artifacts
until the API stabilizes and use a different base package and
different
Maven coordinates for each iteration.
For example, commons-math 4.0-beta1 is released with the
org.apache.commons:commons-math4-beta1 coordinates and the classes
living in the org.apache.commons.math4.beta1 package. Once we are
happy
with the state of the API we release org.apache.commons:commons-math4
with the org.apache.commons.math4 base package and we stop breaking
the
binary compatibility.
With this scheme, binary compatibility is in effect never broken since
the top-level package is different in each codebase:
org.apache.commons.math4.beta1
org.apache.commons.math4.beta2
etc.
In my opinion the "beta" qualifier better conveys the unstable nature
of the API than an arbitrary convention like "the whole 4.x line is
unstable".
"math4.beta1" would be fine too (although "math4u0" was a little
shorter).
Regards,
Gilles
This is a concept people are already familiar with.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org
