It is logical to remove all old API when we *assume* that everyone who used
them has migrated. If 3.1 cycle will again be several years, then we should
remove everything :) If half a year or less - who knows. BTW I've seen users
asking about 1.2 version, which had last release years ago and I think it
was recommended to migrate to 2.0.
Anyways, feel free to remove that DataContext method as well.
2009/11/16 Andrus Adamchik <andru..bjectstyle.org>
>
> On Nov 16, 2009, at 3:14 PM, Andrey Razumovsky wrote:
>
> Sun JDK still contains some
>> methods, deprecated ages ago.
>>
>
> I know. Sun is insane with their deprecation policies. The point of
> deprecation is to give people a warning that something's going away soon.
> Not to keep it forever.
>
> Historically in Cayenne the deprecation timespan was between major
> releases. I.e. the promise is that if something is "deprecated since 3.0",
> it won't be in 3.1. Anything more conservative than that would just result
> in an unbelievable code mess.
>
> In fact I am in favor of shorter major release cycles in large part because
> we'll be able to evolve the framework faster (still giving users a proper
> warning of course).
>
> Andrus
>
>
-- Andrey
This archive was generated by hypermail 2.0.0 : Mon Nov 16 2009 - 08:31:31 EST