WeeklyUpdates/2008-11-03: Difference between revisions

m
Line 23: Line 23:
*Alex Faaborg wrote, "I would like to nominate Markus Stange mstange@themasta.com for helping us make sure Firefox is polished [[https://bugzilla.mozilla.org/buglist.cgi?query_format=advanced&resolution=FIXED&emailassigned_to1=1&emailtype1=exact&email1=mstange%40themasta.com&chfieldto=Now | buglist]]"
*Alex Faaborg wrote, "I would like to nominate Markus Stange mstange@themasta.com for helping us make sure Firefox is polished [[https://bugzilla.mozilla.org/buglist.cgi?query_format=advanced&resolution=FIXED&emailassigned_to1=1&emailtype1=exact&email1=mstange%40themasta.com&chfieldto=Now | buglist]]"


*Benjamin Smedberg writes, "Jim significantly refactored the spidermonkey build system so that we use the same build system for standalone spidermonkey and the mozilla build, and landed it on Tuesday with minimal disruption."
*Benjamin Smedberg writes, "I'd like to nominate Jim Blandy as a friend of the tree. Jim significantly refactored the spidermonkey build system so that we use the same build system for standalone spidermonkey and the mozilla build, and landed it on Tuesday with minimal disruption."


*Murali Nandigama wrote, "I wish to nominate Ed Kelly from Siliconforks for providing help above and beyond his call of duty. Ed is the maintainer of the famous JSCoverage tool which instruments  javascript files. For more information on the tool , please visit http://siliconforks.com/jscoverage/ Ed has worked with me over the entire last week and over the week end to modify the code base of JSCoverage tool so that it can instrument the javascript files in Firefox. The javascript notations used inside Firefox are not in strict ECMA 262 conformance. So, none of the standard plugins like Firebug, FirebugcodeCoverage, Venkman  etc., would be able to instrument the Firefox javascript files. Ed not only made the required tweaks to the jscoverage source but also added the custom flag that I wanted him to provide '--mozilla' that helps me to automate the instrumentation as well as data collection from the instrumented Firefox test run.
*Murali Nandigama wrote, "I wish to nominate Ed Kelly from Siliconforks for providing help above and beyond his call of duty. Ed is the maintainer of the famous JSCoverage tool which instruments  javascript files. For more information on the tool , please visit http://siliconforks.com/jscoverage/ Ed has worked with me over the entire last week and over the week end to modify the code base of JSCoverage tool so that it can instrument the javascript files in Firefox. The javascript notations used inside Firefox are not in strict ECMA 262 conformance. So, none of the standard plugins like Firebug, FirebugcodeCoverage, Venkman  etc., would be able to instrument the Firefox javascript files. Ed not only made the required tweaks to the jscoverage source but also added the custom flag that I wanted him to provide '--mozilla' that helps me to automate the instrumentation as well as data collection from the instrumented Firefox test run.
Confirmed users, Bureaucrats and Sysops emeriti
2,974

edits