commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From henrib <hen...@apache.org>
Subject Re: [RELEASE PROCESS] Stability versus usability
Date Sat, 03 Dec 2011 20:17:25 GMT
Since it may need clarification;

The idea would be to allow a clirr report to give accurate analysis of
whether the external / stable API has been modified.
Methods or classes annotated as @stable, could not change from one version
to another before they are @deprecated.
Methods or classes annotated as @unstable (rather than @usable) could change
between versions.

The net result would be a good sense of whether the actual stable API is
broken by a version and avoid lengthy discussions like the one we just
had...

Wouldn't this be possible to add to our toolbox as a clirr plugin of some
kind?



--
View this message in context: http://apache-commons.680414.n4.nabble.com/RELEASE-PROCESS-Stability-versus-usability-tp4150322p4154703.html
Sent from the Commons - Dev mailing list archive at Nabble.com.

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


Mime
View raw message