[cle-release-team] [cle-kernel-team] Removal of some kernel utils

[Aaron Zeckoski]

I don't know how to generate a report like that. If you have any ideas
then I am open to suggestions. The way I handled the utils change was
to change it, see what broke in the build and fix it. That won't
really work to make a report though. There might be some maven trick
but I don't know what it is.

-AZ


On Tue, Dec 13, 2011 at 5:31 PM, Steve Swinsburg
<steve.swinsburg at gmail.com> wrote:
> Could you give a report of the tools that are using those classes that will be removed, so we can see the extent of the work required for the other tools, and divvy it up?
>
> cheers,
> Steve
>
>
> On 14/12/2011, at 9:26 AM, Aaron Zeckoski wrote:
>
>> Well, if I were the only member of the community then I would probably
>> agree to all those points and rename Sakai to "Aaronkai", however, I
>> am proposing this as a group effort since that is not the case (and
>> since I get only a handful of hours a week to work on Sakai stuff). If
>> you rely on me to get this done then we may as well not do it. I
>> simply don't have the time available to do it all myself.
>> Either way, I can't guarantee there will be no breakage nor would I
>> but I am sure we will all do our best as a community to keep trunk
>> working while we move the platform forward and avoid obsolescence.
>>
>> -AZ
>>
>>
>> On Tue, Dec 13, 2011 at 5:15 PM, csev <csev at umich.edu> wrote:
>>> Aaron,
>>>
>>> I would suggest that it means that you will go through and fix and test anything that the change would break in the core release and check in those fixes as well at the same time.  (i.e. we won't have you do a commit removing this stuff and then have trunk broken for a few weeks).
>>>
>>> Actually you should make all the changes to switch to the use of the preferred libraries across the whole source tree and *then* remove the utils.
>>>
>>> You will make sure trunk works before and after the change across the whole product.
>>>
>>> If you don't consider fixing any / all breakage in the core caused by the change "in your scope" than I am -1 on the change.
>>>
>>> Of course contrib folks are more on their own.  Although a simple scan of contrib tools and email message to the dev-list pointing out tools that need changing would be neighborly.
>>>
>>> /Chuck
>>> _______________________________________________
>>> cle-release-team mailing list
>>> cle-release-team at collab.sakaiproject.org
>>> http://collab.sakaiproject.org/mailman/listinfo/cle-release-team
>>
>>
>>
>> --
>> Aaron Zeckoski - Software Architect - http://tinyurl.com/azprofile
>> _______________________________________________
>> cle-release-team mailing list
>> cle-release-team at collab.sakaiproject.org
>> http://collab.sakaiproject.org/mailman/listinfo/cle-release-team
>
> _______________________________________________
> cle-release-team mailing list
> cle-release-team at collab.sakaiproject.org
> http://collab.sakaiproject.org/mailman/listinfo/cle-release-team



-- 
Aaron Zeckoski - Software Architect - http://tinyurl.com/azprofile