Account confirmers, Anti-spam team, canmove, Confirmed users, Bureaucrats and Sysops emeriti
4,083
edits
SeaMonkey/StatusMeetings/2009-12-15: Difference between revisions
SeaMonkey/StatusMeetings/2009-12-15 (view source)
Revision as of 01:16, 21 January 2011
, 21 January 2011moved SeaMonkey:StatusMeetings:2009-12-15 to SeaMonkey/StatusMeetings/2009-12-15: / is a much nicer separator :)
Philip Chee (talk | contribs) |
m (moved SeaMonkey:StatusMeetings:2009-12-15 to SeaMonkey/StatusMeetings/2009-12-15: / is a much nicer separator :)) |
||
| (2 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
<small>[[SeaMonkey:StatusMeetings:2009-12-01|« last meeting]] | [[SeaMonkey:StatusMeetings|index]]</small> | <small>[[SeaMonkey:StatusMeetings:2009-12-01|« last meeting]] | [[SeaMonkey:StatusMeetings|index]] | [[SeaMonkey:StatusMeetings:2010-01-12|next meeting »]]</small> | ||
'''SeaMonkey Meeting Details''' | '''SeaMonkey Meeting Details''' | ||
| Line 36: | Line 36: | ||
** This has been traced to the McAfee Site Advisor component of the McAfee Internet Security Suite. A regression range has been identified (2007110103/2007103102). This regression range corresponds to a similar cut and paste problem in Thunderbird 3.0a but not involving McAfee. Neil has looked at the changeset involved and has a tentative patch proposed. | ** This has been traced to the McAfee Site Advisor component of the McAfee Internet Security Suite. A regression range has been identified (2007110103/2007103102). This regression range corresponds to a similar cut and paste problem in Thunderbird 3.0a but not involving McAfee. Neil has looked at the changeset involved and has a tentative patch proposed. | ||
** The McAfee techs would like a developer from the SeaMonkey side to assist them in tracking down the problem. Do we have someone with the required skillset? Perhaps Neil. | ** The McAfee techs would like a developer from the SeaMonkey side to assist them in tracking down the problem. Do we have someone with the required skillset? Perhaps Neil. | ||
* Possible bug | * Possible bug: MailNews reported as high CPU being caused by having news downloaded without bounds, i.e. no purging. This could explain some people reporting 2.0 is slow as well due to large email or news folders causing blocked main threads when getting messages. Allegedly {{bug|311774}} introduced the slowness. | ||
=== SeaMonkey 2.0.1 === | === SeaMonkey 2.0.1 === | ||