IMHO, for the benefit of the users, if deprecation and obsoleting
policies are defined, it would be great.
I mean, say you define a time period for obsoleting a deprecated
feature, rather than obsoleting in an ad-hoc manner, so that all know
how long a deprecated feature would be there before th
Deepal ..I think you should ask the user list is lot of people using
it. If people had moved to service client you do not need to move them
to scracth .. just delete them. (But judging by the work I had to do
in moving to service client .. I belive there are lot still using it)
Srinath
On 3/9/06
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi all;
As you know in the current SVN we have our old client side codes (Call
, InOutMEPClient etc..) and no body is using those, in fact they are
marked as deprecated.
So what if we move them to scratch area , keeping them in the main
source tree m