commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ole Ersoy <>
Subject Re: [math] Name of the new TLP
Date Tue, 26 Jan 2016 00:22:30 GMT
Also if each module is very simple and isolated alphas, betas, etc. matter less (If at all).
 Most devs releasing to npm rely on semver only.


On 01/25/2016 02:27 PM, Gary Gregory wrote:
> On Jan 25, 2016 10:11 AM, "Emmanuel Bourg" <> wrote:
>> Le 25/01/2016 18:52, Gilles a écrit :
>>> AFAICT, the real issue is one of policy: Commons is supposed to be
> stable,
>>> stable, stable and stable (IIUC).
>>> And CM is far from being mature as a programming project, when
> considering
>>> design and scope, and not only the quality of its results and
> performance
>>> (which are both good in many cases).
>>> So stability (as in using JDK 5 only) is not a good perspective (surely
> not
>>> developers and probably not for users either IMO).
>>> If this does not change, what's the point indeed?
>> I hope that a motivation behind the TLP isn't to break the compatibility
>> on every release, otherwise this will quickly turn into a nightmare for
>> the users. Bouncycastle plays this game and it isn't really fun to follow
> :(
> WRT compatibility, the only thing that matters is not creating jar hell for
> users. You can break compatibility if you change package and maven
> coordinates. It's up to the project to create enough alphas and betas to
> get to a stable public API before a release. That's just basic project
> management IMO. Anything less will leave a lot users unhappy.
> Gary
>> Emmanuel Bourg
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail:
>> For additional commands, e-mail:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message