I agree, strongly, with Stephen on this for [math] and commons in
general.  That's why I asked so many times if we had the API right
before releasing 1.0.  In retrospect, the linear stuff should probably
have been held back, but we released it so we need to maintain
comapability.

I also agree with Mark that the linear API is less flexible than the
rest of math and I would like to provide a way for Rodrigo and others
to extend naturally to make the whole package more useful.  I am sure
that we can find creative ways to do this without breaking binary or
source compatibility.
 
> Again, I stress this point. Commons has many interfaces that we would
> like to change after the fact (eg. MultiMap in [collections], or
> DynaProperty in [beanutils]). AFAIN, none have been changed even over a
> major release version (awaiting someone to prove me wrong...).
> 
> If this were code within a company, then it wouldn't matter. 

Actually, if the company is large and there are lots of projects that
depend on the component, the same situation applies ;-)

> But this is
> a publicly available, fully released, API. Open source is sometimes a
> pain to work with. This is one of those occasions. And IMHO, all commons
> would suffer were the change to happen.
> 
> For the record (and in accordance with informing people at the earliest
> point possible), I will -1 a 1.x release that changes an interface. I
> will -0/-1 a 2.0 release that changes an interface depening on further
> discussion. (Bearing in mind that my vote is non-binding, as a non-math
> committer)

Your release votes *are* binding.  Thanks for the feedback and thanks
in advance for reviewing the RC(s) ;-)

Phil

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to