Thread: [gobo-eiffel-develop] Obsolete classes

SourceForge Headquarters 225 Broadway Suite 1600 San Diego, CA 92101 +1 (858) 422-6466

I just came upon an obsolete warning for DS_COMPARABLE_COMPARATOR.

I think these warnings are far past their sell-by date, and the old
classes should be removed.

Colin Adams wrote:
> I just came upon an obsolete warning for DS_COMPARABLE_COMPARATOR.
> 
> I think these warnings are far past their sell-by date, and the old
> classes should be removed.

In fact, I always wondered how long should a class or feature be
marked as obsolete before being able to remove it. Should it be
after some number of releases (2, 5, 10, ...?)? Should it be after
some number of years (2, 5, 10, ...?)? Never? A combination of these?

-- 
Eric Bezault
mailto:er...@go...
http://www.gobosoft.com

>>>>> "Eric" == Eric Bezault <er...@go...> writes:

    Eric> In fact, I always wondered how long should a class or feature
    Eric> be marked as obsolete before being able to remove it. Should
    Eric> it be after some number of releases (2, 5, 10, ...?)? Should
    Eric> it be after some number of years (2, 5, 10, ...?)? Never? A
    Eric> combination of these?

Difficult question. 5 years perhaps?

-- 
Cheers,

Berend de Boer

Hello Berend,

Friday, May 23, 2008, 11:46:42 AM, you wrote:

>>>>>> "Eric" == Eric Bezault <er...@go...> writes:

BdB>     Eric> In fact, I always wondered how long should a class or feature
BdB>     Eric> be marked as obsolete before being able to remove it. Should
BdB>     Eric> it be after some number of releases (2, 5, 10, ...?)? Should
BdB>     Eric> it be after some number of years (2, 5, 10, ...?)? Never? A
BdB>     Eric> combination of these?

BdB> Difficult question. 5 years perhaps?

Well there has to be at least a good stable release in between.
So slowly migration is possible.

I got fucked by SmartEiffel more then once because they had no
migration path just from now to an unstable broken CVS head version.

-- 
Best regards,
 Lothar                            mailto:ll...@we...