Hi Gustav,
it's case by case.
For API, which is used widely - we may want to keep backwards
compatibility. Otherwise - we can just delete.
WBR,
Alexey.
On Jan 11, 2009, at 6:55 , gustav trede wrote:
> Salut ,
>
> The commit rule that never delete a class, but move it to grizzly-
> compat.
>
> Is that a hard rule or is it case by case ?
>
> Like for my cachetest, i redesign it some.
>
> --
> your servant
> gustav trede
>
> coding is art - not only something that bring food on the table,
> everybody should be able to feel proud about their code,
> that they have performed their best considering the given conditions.
>