SeaMonkey/StatusMeetings/2011-05-17: Difference between revisions

Jump to navigation Jump to search

SeaMonkey/StatusMeetings/2011-05-17 (view source)

Revision as of 09:41, 16 May 2011

92 bytes added ,  16 May 2011
→‎Agenda
Line 14: Line 14:


'''NEW'''
'''NEW'''
* '''IanN''' to email Fallen to get some cooperation for getting a version of Lightning that is compatible with SeaMonkey 2.1 out on AMO.
* '''Ratty''' to see if he can round up some Lightning testers from the various SeaMonkey forums. comm-miramar builds are now available [https://ftp.mozilla.org/pub/mozilla.org/calendar/lightning/nightly/latest-comm-miramar/ here]. q.v. {{Bug|653507}} Lightning nightly builds for Miramar (Thunderbird 3.3 / Gecko 5.0) (comm-central + mozilla-aurora)
** Fallen said that he would rather we put our efforts into testing against the 1.0b4 release from comm-aurora than try and do anything from comm-2.0 there would be issues around L10n from comm-2.0. If enough decent testing can be done then he would be happy to mark it as compatible with 2.1 on AMO.
** '''Ratty''' to see if he can round up some testers from the various SeaMonkey forums. But first we need to find out from Fallen where our testers can get a Lightning 1.0b4 release from comm-aurora to test with.
** q.v. {{Bug|653507}} Lightning nightly builds for Miramar (Thunderbird 3.3 / Gecko 5.0) (comm-central + mozilla-aurora)


'''OPEN'''
'''OPEN'''


'''CLOSED'''
'''CLOSED'''
* '''IanN''' to email Fallen to get some cooperation for getting a version of Lightning that is compatible with SeaMonkey 2.1 out on AMO.
** Fallen said that he would rather we put our efforts into testing against the 1.0b4 release from comm-aurora than try and do anything from comm-2.0 there would be issues around L10n from comm-2.0. If enough decent testing can be done then he would be happy to mark it as compatible with 2.1 on AMO.


'''K.I.V.'''
'''K.I.V.'''
Line 28: Line 27:
=== SeaMonkey 2.1 ===
=== SeaMonkey 2.1 ===


[https://bugzilla.mozilla.org/buglist.cgi?resolution=---&&field0-0-0=cf_blocking_seamonkey21&type0-0-0=equals&value0-0-0=final%2B open blockers] (3)
[https://bugzilla.mozilla.org/buglist.cgi?resolution=---&&field0-0-0=cf_blocking_seamonkey21&type0-0-0=equals&value0-0-0=final%2B open blockers] (1)
[https://bugzilla.mozilla.org/buglist.cgi?&field0-0-0=cf_blocking_seamonkey21&type0-0-0=equals&value0-0-0=%3F blocker requests] (0)
[https://bugzilla.mozilla.org/buglist.cgi?&field0-0-0=cf_blocking_seamonkey21&type0-0-0=equals&value0-0-0=%3F blocker requests] (0)
[https://bugzilla.mozilla.org/buglist.cgi?resolution=---&target_milestone=seamonkey2.1final targeted] (0)
[https://bugzilla.mozilla.org/buglist.cgi?resolution=---&target_milestone=seamonkey2.1final targeted] (0)
Line 40: Line 39:


* Please help updating the [[SeaMonkey:Features:2.1|New 2.1 Features]] page as we go.
* Please help updating the [[SeaMonkey:Features:2.1|New 2.1 Features]] page as we go.
** comm-2.0 is not used/supported by TB so '''InvisibleSmiley''' and '''Ratty''' take care of transplanting MailNews Core bugs they see fit.
** comm-2.0 is not used nor supported by Thunderbird so '''InvisibleSmiley''' and '''Ratty''' have taken the responsibility for transplanting MailNews Core bugs from trunk as appropriate.
* There might not be any more official security updates to the 1.9.1 branch after the upcoming one, so we should get a stable release based on Mozilla 2.0 out as soon as we can.
* There might not be any more official security updates to the 1.9.1 branch after the upcoming one, so we should get a stable release based on Mozilla 2.0 out as soon as we can.


=== Feature List, Planning ===
=== Feature List, Planning ===


[http://dev.seamonkey.at/#bugstats Bug statistics] for last two (full) weeks: 36 new, 34 fixed, 29 triaged.
[http://dev.seamonkey.at/#bugstats Bug statistics] for last two (full) weeks: 46 new, 37 fixed, 30 triaged.
* Good further triage targets could come out of looking at the [https://bugzilla.mozilla.org/report.cgi?query_format=report-table&format=table&action=wrap&x_axis_field=bug_status&y_axis_field=component&product=SeaMonkey&resolution=--- component bug counts], pick yours!
* Good further triage targets could come out of looking at the [https://bugzilla.mozilla.org/report.cgi?query_format=report-table&format=table&action=wrap&x_axis_field=bug_status&y_axis_field=component&product=SeaMonkey&resolution=--- component bug counts], pick yours!


[https://bugzilla.mozilla.org/chart.cgi?category=-All-&subcategory=-All-&name=1183&label0=SM-with-review%3F-requests&line0=1928&label1=SM-with-superreview%3F-requests&line1=1929&gt=1&labelgt=Grand+Total&datefrom=2009-07-15&dateto=&action-wrap=Chart+This+List Open reviews/flags]:
[https://bugzilla.mozilla.org/chart.cgi?category=-All-&subcategory=-All-&name=1183&label0=SM-with-review%3F-requests&line0=1928&label1=SM-with-superreview%3F-requests&line1=1929&gt=1&labelgt=Grand+Total&datefrom=2009-07-15&dateto=&action-wrap=Chart+This+List Open reviews/flags]:
[https://bugzilla.mozilla.org/buglist.cgi?cmdtype=dorem&namedcmd=SeaMonkey%20%282%29%20/%20-All-%20/%20SM-with-review%3F-requests&series_id=1928&remaction=runseries 29 review]
[https://bugzilla.mozilla.org/buglist.cgi?cmdtype=dorem&namedcmd=SeaMonkey%20%282%29%20/%20-All-%20/%20SM-with-review%3F-requests&series_id=1928&remaction=runseries 29 review]
[https://bugzilla.mozilla.org/buglist.cgi?cmdtype=dorem&namedcmd=SeaMonkey%20%282%29%20/%20-All-%20/%20SM-with-superreview%3F-requests&series_id=1929&remaction=runseries 13 super-review]
[https://bugzilla.mozilla.org/buglist.cgi?cmdtype=dorem&namedcmd=SeaMonkey%20%282%29%20/%20-All-%20/%20SM-with-superreview%3F-requests&series_id=1929&remaction=runseries 12 super-review]
[https://bugzilla.mozilla.org/buglist.cgi?product=SeaMonkey&field0-0-0=flagtypes.name&type0-0-0=equals&value0-0-0=ui-review%3F 0 ui-review]
[https://bugzilla.mozilla.org/buglist.cgi?product=SeaMonkey&field0-0-0=flagtypes.name&type0-0-0=equals&value0-0-0=ui-review%3F 0 ui-review]
[https://bugzilla.mozilla.org/buglist.cgi?product=SeaMonkey&field0-0-0=flagtypes.name&type0-0-0=equals&value0-0-0=feedback%3F 5 feedback]
[https://bugzilla.mozilla.org/buglist.cgi?product=SeaMonkey&field0-0-0=flagtypes.name&type0-0-0=equals&value0-0-0=feedback%3F 5 feedback]
Line 59: Line 58:
===== Active =====
===== Active =====
* We will need to take a close look at Lightning, which is mainly targeting Thunderbird.
* We will need to take a close look at Lightning, which is mainly targeting Thunderbird.
** Lightning 1.0b4 from comm-aurora needs to be tested against SeaMonkey 2.1. But first we need to find out from Fallen where our testers can get a Lightning 1.0b4 release from comm-aurora to test with.
** Lightning 1.0b4 from comm-aurora needs to be tested against SeaMonkey 2.1. comm-miramar Lightning builds are now available at the [https://ftp.mozilla.org/pub/mozilla.org/calendar/lightning/nightly/latest-comm-miramar/ ftp site].
** Due to recent Lightning patches/fixes, Lightning nightlies are now working again on SM trunk.
** Due to recent Lightning patches/fixes, Lightning nightlies are now working again on SM trunk.


Philip Chee
Confirmed users
2,595

edits

Retrieved from "https://wiki.allizom.org/Special:MobileDiff/308866"

Navigation menu