SeaMonkey/StatusMeetings/2010-02-23: Difference between revisions

m
 
(8 intermediate revisions by 3 users not shown)
Line 66: Line 66:
* {{bug|460953}} kill-rdf port [sgautherie].
* {{bug|460953}} kill-rdf port [sgautherie].
** Postponed until mcsmurf (or sgautherie) can resume work on it.
** Postponed until mcsmurf (or sgautherie) can resume work on it.
** status/progress?
** No progress.
* {{bug|436794}} Enable Mac OS X system address book per default and add UI.
* {{bug|436794}} Enable Mac OS X system address book per default and add UI.
** SM UI needed, unowned, helpwanted.
** SM UI needed, unowned, helpwanted.
Line 90: Line 90:
** status/progress?
** status/progress?
* {{Bug|545110}} Add/port about:support (Troubleshooting Information page) to SeaMonkey
* {{Bug|545110}} Add/port about:support (Troubleshooting Information page) to SeaMonkey
** status/progress?
** Depends on {{Bug|518607}} Move the Troubleshooting Information page into toolkit so other apps like Thunderbird and SeaMonkey can use it.


We also should take a look at the other items on [https://bugzilla.mozilla.org/buglist.cgi?resolution=---&field0-0-0=flagtypes.name&type0-0-0=equals&value0-0-0=wanted-seamonkey2.1%2B  wanted-seamonkey2.1+]
We also should take a look at the other items on [https://bugzilla.mozilla.org/buglist.cgi?resolution=---&field0-0-0=flagtypes.name&type0-0-0=equals&value0-0-0=wanted-seamonkey2.1%2B  wanted-seamonkey2.1+]


* Decision made to [http://home.kairo.at/blog/2010-02/dropping_1_9_2_going_1_9_3_for_seamonkey drop 1.9.2 and go for 1.9.3 as a base]
* The Decision was made to [http://home.kairo.at/blog/2010-02/dropping_1_9_2_going_1_9_3_for_seamonkey drop 1.9.2 and go for 1.9.3 as a base].
** Creates some problems with staying behind Firefox 3.6 and Thunderbird 3.1 for a bit, but makes us be right at the front when Firefox.next comes.
** This creates some problems with staying behind Firefox 3.6 and Thunderbird 3.1 for a bit, but it puts us right at the front when Firefox.next comes.
** Need to find a solution for Lightning, which is targeting Thunderbird 3.1 now.
** We need to find a solution for Lightning, which is targeting Thunderbird 3.1 now.
** Could remove all branch ifdefs from suite/ trunk code.
** We can now remove all branch ifdefs from suite/ trunk code.


=== Roundtable ===
=== Roundtable ===
Line 124: Line 124:


==== KaiRo  ====
==== KaiRo  ====
*As usual, [http://home.kairo.at/blog/ my blog] has more detailed status about my work, and [http://benjamin.smedbergs.us/weekly-updates.fcgi/user/KaiRo/posts Mozilla Status Board Posts] also tell about my next planned steps.
* Prepared and shipped SeaMonkey 2.0.3
* Looked into graphs server ({{bug|492406}}) data pushing.
* More progress window work ({{bug|513691}}, {{bug|515053}}) before I threw the towel because of too much stop energy on that topic.
* Filed {{bug|545716}} on OOPP for SeaMonkey.
* Started Council / SeaMonkey dev discussion about dropping 1.9.2 and going for 1.9.3, drove it to a conclusion / decision and posted about it: http://home.kairo.at/blog/2010-02/dropping_1_9_2_going_1_9_3_for_seamonkey .
* Worked on getting pushlog metadata onto my server so I can subscribe to useful pushlogs in the feed reader, for testing this now runs at http://dev.seamonkey.at/pushlog .
* Introduced a temporary website glitch and fixed it again ({{bug|546997}}).
* Turned off experimental 1.9.2 build and instead turned on debug builds on trunk, found a slight buildbotcustom issue there and put up a patch ({{bug|547540}}).
* Got the new Mac machines integrated into build pools ({{bug|526208}}).
* Turned on first few tests for Mac on trunk.
* Checked in patch for async places expiration ({{bug|536374}}).
* Started work on places bookmarks support ({{bug|498596}}), found that HTML import/export should live in toolkit instead of browser ({{bug|546942}}).
* Filed {{bug|546484}} and {{bug|546487}} for unsupporting 1.9.2, which Serge did, reviewed patch for OS/2 packaging that did parts of that as well ({{bug|545534}}).
* Checked in another fix for de help from Michael Opitz ({{bug|546343}}).
*As usual, [http://home.kairo.at/blog/ my blog][http://www.casinoenligne555.net/ casino en ligne francais] has more detailed status about my work, and [http://benjamin.smedbergs.us/weekly-updates.fcgi/user/KaiRo/posts Mozilla Status Board Posts] also tell about my next planned steps.


==== mcsmurf ====
==== mcsmurf ====
* {{Bug|471346}} Port GetDefaultFeedReader to SeaMonkey shell service.
* {{Bug|471346}} Port GetDefaultFeedReader to SeaMonkey shell service (waiting for review)


==== Misak  ====
==== Misak  ====
Line 243: Line 257:
** [Ratty] How about pruning the entries. There are some contributors who just drop by specifically  to implement ''one'' feature they are interested in and then disappear forever afterwards (asrail, wladow). MReimer appears to have [http://en.wiktionary.org/wiki/gafiated GAFIAted] and is highly unlikely to return. Aqualon does bug triage regularly so perhaps he could update us on his QA activities.
** [Ratty] How about pruning the entries. There are some contributors who just drop by specifically  to implement ''one'' feature they are interested in and then disappear forever afterwards (asrail, wladow). MReimer appears to have [http://en.wiktionary.org/wiki/gafiated GAFIAted] and is highly unlikely to return. Aqualon does bug triage regularly so perhaps he could update us on his QA activities.
** [sgautherie] We can do both/either: I just wanted to make a "1st step" suggestion ;-)
** [sgautherie] We can do both/either: I just wanted to make a "1st step" suggestion ;-)
* ?
** KaiRo suggests moving the whole roundtable to the status board but that would require active developers to sign-up.
* KompoZer: Kaze says that independent of getting KompoZer into comm-central, he could still backport most of KompoZer features to SM Composer: just send him a list of the most wanted ones (or ask our users).
** [Ratty] will start a new thread in the Mozillazine SeaMonkey forums to that effect.