[cle-release-team] 2.9.x: branch management update
Steve Swinsburg
steve.swinsburg at gmail.com
Wed Mar 27 14:54:01 PDT 2013
What's the actual issue you are facing with JCL?
Cheers
S
Sent from my iPhone
On 28/03/2013, at 5:53, Aaron Zeckoski <azeckoski at unicon.net> wrote:
> For the EB uses, I cannot use the logger we normally use because of
> the issues with JCL and classloaders.
> http://articles.qos.ch/classloader.html
> Not sure about the other projects.
> -AZ
>
>
> On Wed, Mar 27, 2013 at 2:26 PM, Anthony Whyte <arwhyte at umich.edu> wrote:
>> Summary of 2.9.x branch management activities since Friday, 22 March.
>>
>> merged = 20
>> to merge = 13
>>
>> of these
>> merge conflicts encountered = 4
>> merge postponed until question is answered = 1
>> merge held up after code review = 1 [1]
>> ticket missing info (i.e., trunk revision number) = 1
>>
>> cheers,
>>
>> Anth
>>
>> [1] (SAK-22390 portal, log object vs System.err.println; we have a log
>> object although after grepping CLE source a few projects such as EB, LB,
>> portal, rwiki and samigo use System.err.println (174 instances) so I can
>> hardly claim to be enforcing a rule, perhaps not even a best practice with
>> respect to those projects.)
>>
>> _______________________________________________
>> 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
More information about the cle-release-team
mailing list