Confirmed users
2,078
edits
SeaMonkey/StatusMeetings/2011-05-03: Difference between revisions
→Callek
(→KaiRo) |
(→Callek) |
||
| (16 intermediate revisions by 4 users not shown) | |||
| Line 9: | Line 9: | ||
* Who's taking minutes? -> '''Ratty''' | * Who's taking minutes? -> '''Ratty''' | ||
* Nominees for Friends of the Fish Tank? | * Nominees for Friends of the Fish Tank? | ||
** thebot nominates KaiRo. Seconded and Thirded. | |||
=== Action Items === | === Action Items === | ||
| Line 15: | Line 16: | ||
'''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. | * '''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. | |||
** '''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''' | ||
| Line 24: | Line 28: | ||
'''K.I.V.''' | '''K.I.V.''' | ||
* Get permission from Google to use their geolocation JSON service '''[KaiRo]'''. We can still only wait on the Google front right now. Didn't hear anything about open Geolocation service yet. No easy solution in sight. | * Get permission from Google to use their geolocation JSON service '''[KaiRo]'''. We can still only wait on the Google front right now. Didn't hear anything about open Geolocation service yet. No easy solution in sight. | ||
=== SeaMonkey 2.0.14 === | === SeaMonkey 2.0.14 === | ||
| Line 45: | Line 48: | ||
* Don't fear being aggressive with blocker triage, If it isn't needed it doesn't block. By that same token, if you are able to fix a blocker please try and work on them before tackling any other bugs. | * Don't fear being aggressive with blocker triage, If it isn't needed it doesn't block. By that same token, if you are able to fix a blocker please try and work on them before tackling any other bugs. | ||
* Help patches can go in at anytime. | * Help patches can go in at anytime. | ||
* 2.1 looks quite good, Callek said he might want to cut it as early as today if possible. But we have 5 open blockers. IanN is working on the modern theme now for add-on manager after InvisibleSmiley's initial work. | |||
Further 2.1 scheduling: | Further 2.1 scheduling: | ||
| Line 73: | Line 77: | ||
* {{Bug|570004}} Popup/"doorhanger" notifications [Neil]. | * {{Bug|570004}} Popup/"doorhanger" notifications [Neil]. | ||
** Implementation moved to {{Bug|595810}}. | ** Implementation moved to {{Bug|595810}}. | ||
** | ** Branch work on doorhangers is now '''complete'''. lwtheme doorhangers has been moved to 2.2. | ||
* 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 | ** 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. | ||
** 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. | ||
==== 2.next ==== | ==== 2.next ==== | ||
| Line 108: | Line 109: | ||
===== Active ===== | ===== Active ===== | ||
* {{Bug|570004}} Popup/"doorhanger" notifications [Neil]. | |||
** Implementation moved to {{Bug|595810}}. | |||
** Only lwthemes doorhangers are left to do. | |||
* {{Bug|606683}} Allow customization of toolbar in Composer and MailNews Composition [IanN]. | * {{Bug|606683}} Allow customization of toolbar in Composer and MailNews Composition [IanN]. | ||
| Line 122: | Line 127: | ||
==== asrail ==== | ==== asrail ==== | ||
==== Callek ==== | ==== Callek ==== | ||
* Fixed: | * Release Engineering | ||
** {{Bug|646723}} Install kypM-ssh on windows slaves. | ** Fixed: | ||
** {{Bug|651349}} tools/buildbot-helpers/force_build.py should work for buildbot-0.8.x masters. | *** {{Bug|646723}} Install kypM-ssh on windows slaves. | ||
** {{Bug|652391}} Install {*} OPSI packages manually into Windows Slaves. | *** {{Bug|651349}} tools/buildbot-helpers/force_build.py should work for buildbot-0.8.x masters. | ||
** {{Bug|646725}} Deploy Java 6u14 (Development Kit and Runtimes) to windows slaves. | *** {{Bug|652391}} Install {*} OPSI packages manually into Windows Slaves. | ||
* Working on: | *** {{Bug|646725}} Deploy Java 6u14 (Development Kit and Runtimes) to windows slaves. | ||
** {{Bug|633397}} Automatic partial update from 2.1b1 to 2.1b2 build 2 misses extensions. | ** Working on: | ||
** {{Bug|647107}} snippet details URL is not secure, can spoof major updates. | *** {{Bug|633397}} Automatic partial update from 2.1b1 to 2.1b2 build 2 misses extensions. | ||
*** {{Bug|647107}} snippet details URL is not secure, can spoof major updates. | |||
==== ewong ==== | ==== ewong ==== | ||
| Line 261: | Line 267: | ||
*Fixed Core bugs: | *Fixed Core bugs: | ||
**{{bug|650699}} Sort out MSVC DLLs packaging in Debug builds | **{{bug|650699}} Sort out MSVC DLLs packaging in Debug builds | ||
**{{bug|652862}} Remove disable-svg references in tests | |||
==== stefanh ==== | ==== stefanh ==== | ||
| Line 274: | Line 281: | ||
=== Any other business? === | === Any other business? === | ||
* Organize another Triage Event [tonymec]. | * Organize another Triage Event [tonymec]. | ||
** Proposed name ''Operation Nugzilla''. | |||
** Tonymec suggests 18-20 May, 2000-2400 CEST, but ungodly time for East-Asian members. Perhaps one additional session from 1400-1800 CEST (2000-2400 HKT/SGT/MYT) on either 19th or 20th depending on availability. | |||
*** ''I'll be there 1400-2400 CEST all three days. I suggest Asians use the early part of the sessions, Americans (from Alaska to Tierra del Fuego ;-) ) the late part, so there'll be at least a couple of hours for everyone. —[[User:Tonymec|Tonymec]] 07:23, 3 May 2011 (PDT) '' | |||
** Tonymec to come up with a loose framework around what is to be achieved so that it can be passed on to whoever is running the Asian sessions. | |||
** Framework to be posted to MozWiki and possibly an announcement to the newsgroups/forums this Sunday. | |||
* Future meetings - organising, chairing, etc. Who should do what? [IanN] | * Future meetings - organising, chairing, etc. Who should do what? [IanN] | ||
** IanN to continue to chair the meetings and Ratty to take the minutes/meeting notes. | |||
** KaiRo usually tried to get agenda and announcement out on the Saturday or Sunday before the meeting. | |||
** InvisibleSmiley to prepare the meeting agendas and to make the announcements. | |||
* '''SeaMonkey RoadMap'''. | |||
** If we use FF's release schedule, then the roadmap will not be feature-based as we won't have decided which features will be able to be in any of the releases. | |||
** Our roadmap will be very much dependent on both FF's and TB's roadmaps but we can try and slot in any features we are porting / creating as we get closer to milestones. | |||
** Future discussions will be needed once Callek makes the announcement and 2.1 is out. So that would be at the next meeting. | |||
* What doesn "tl;dr;" mean? | |||
** [http://en.wiktionary.org/wiki/tl;dr "Too long; Didn't read"]. | |||