[Building Sakai] Deprecation Notice: kernel static covers

[Berg, Alan]

Hi,

I beg to disagree, I believe that there should be a clear predictable time between start of depreciation and end. The whole process is supposed to give time to transition from depreciated API to better API. The static covers make for complex dependencies and make unit testing difficult and so are a good case for depreciation. Therefore the question is do disagree with depreciation or the TTL.

Alan

Alan Berg
Interim QA Director - The Sakai Foundation

Senior Developer / Quality Assurance
Group Education and Research Services
Central Computer Services
University of Amsterdam

http://home.uva.nl/a.m.berg




-----Original Message-----
From: sakai-dev-bounces at collab.sakaiproject.org on behalf of Stephen Marquard
Sent: Wed 3/17/2010 11:03
To: sakai-dev
Subject: Re: [Building Sakai] Deprecation Notice: kernel static covers
 
As a local implementer and kernel team member, I object and vote -1 on eventual removal of the static covers, as this imposes an unnecessary code maintenance burden on local sites, especially wrt third-party code (for example locally maintained webservices and other code).

I have no problem with these being deprecated, but they should be left in place indefinitely.

Regards
Stephen

>>> David Horwitz <david.horwitz at uct.ac.za> 3/17/2010 10:04 AM >>>
Deprecation Notice: In the next scheduled release in the 1.1 kernel series (1.1.2) all the Static covers of kernel services will be marked as deprecated. Developers are urged to review their code and replace the use of static covers with spring injection or lookup from the component manager in line with stated Sakai best practices [http://confluence.sakaiproject.org/display/SAKDEV/Best+Practices+for+Kernel+code#BestPracticesforKernelcode-Nousageofstaticcovers]. The covers are scheduled for removal in Kernel 2.0.0

Regards

David

_______________________________________________
sakai-dev mailing list
sakai-dev at collab.sakaiproject.org 
http://collab.sakaiproject.org/mailman/listinfo/sakai-dev 

TO UNSUBSCRIBE: send email to sakai-dev-unsubscribe at collab.sakaiproject.org with a subject of "unsubscribe"


 
______________________________________________________________________________________________ 

UNIVERSITY OF CAPE TOWN 

This e-mail is subject to the UCT ICT policies and e-mail disclaimer published on our website at http://www.uct.ac.za/about/policies/emaildisclaimer/ or obtainable from +27 21 650 4500. This e-mail is intended only for the person(s) to whom it is addressed. If the e-mail has reached you in error, please notify the author. If you are not the intended recipient of the e-mail you may not use, disclose, copy, redirect or print the content. If this e-mail is not related to the business of UCT it is sent by the sender in the sender's individual capacity.

_____________________________________________________________________________________________________
 
_______________________________________________
sakai-dev mailing list
sakai-dev at collab.sakaiproject.org
http://collab.sakaiproject.org/mailman/listinfo/sakai-dev

TO UNSUBSCRIBE: send email to sakai-dev-unsubscribe at collab.sakaiproject.org with a subject of "unsubscribe"

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://collab.sakaiproject.org/pipermail/sakai-dev/attachments/20100317/6bdd3019/attachment.html