Hi.
> +! Unreleased code is subject to change, including deletion or
> incompatible API change.
There is a "checkOrder" method in "util.MathUtils" throwing an
"IllegalArgumentException". I'll create the more specific
NotIncreasingSequenceException
NotStrictlyIncreasingSequenceException
that
On Tue, Jun 29, 2010 at 9:18 PM, Phil Steitz wrote:
> +! Unreleased code is subject to change, including deletion or
> incompatible API change.
>
What he said!
-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For ad
James Carman wrote:
> On Tue, Jun 29, 2010 at 7:46 PM, Gilles Sadowski
> wrote:
>> Not in an official release since 2.2 isn't out yet.
>>
>
> Well, since the code hasn't been released (it's a new
> method/constructor I presume?), I would think that anything new that's
> in SVN should be considere
On Tue, Jun 29, 2010 at 7:46 PM, Gilles Sadowski
wrote:
> Not in an official release since 2.2 isn't out yet.
>
Well, since the code hasn't been released (it's a new
method/constructor I presume?), I would think that anything new that's
in SVN should be considered a work-in-progress. So, I don't
> Is it part of a public API that went out in a release already? [...]
>
> > Is it OK to perform non backward-compatible changes in code that wasn't
> > offcially released yet (i.e. in code tagged with the "@since 2.2" javadoc
> > comment)?
Not in an official release since 2.2 isn't out yet.
>
Is it part of a public API that went out in a release already? What
method do you have in mind?
On Tue, Jun 29, 2010 at 7:12 PM, Gilles Sadowski
wrote:
> Hi.
>
> Is it OK to perform non backward-compatible changes in code that wasn't
> offcially released yet (i.e. in code tagged with the "@since
Hi.
Is it OK to perform non backward-compatible changes in code that wasn't
offcially released yet (i.e. in code tagged with the "@since 2.2" javadoc
comment)?
Best regards,
Gilles
-
To unsubscribe, e-mail: dev-unsubscr...@comm
