SeaMonkey/StatusMeetings/2016-03-29: Difference between revisions

Jump to navigation Jump to search
m
Line 139: Line 139:
=== Feature List, Planning ===
=== Feature List, Planning ===
[http://dev.seamonkey.at/#bugstats Bug statistics] for the last two (full) weeks: 36 new, 6 fixed, 6 triaged.
[http://dev.seamonkey.at/#bugstats Bug statistics] for the last two (full) weeks: 36 new, 6 fixed, 6 triaged.
* low triaging effort, higher than average number of new bugs filed.
* good triaging effort, Rainer Bielefeld has been busy filing and verifying bugs.
* '''Ratty has a SeaMonkey build with a working Firefox Devtools!!!!''' For relevant patches see previous meeting notes.
** Unfortunately changes in DevTools keep bit-rotting my patch and it's a P.I.T.A. to keep up.
* Mozilla wants to '''separate Firefox and Thunderbird, in infrastructure and organizationally''', which will likely affect SeaMonkey as well
* Mozilla wants to '''separate Firefox and Thunderbird, in infrastructure and organizationally''', which will likely affect SeaMonkey as well
** discussions in [https://groups.google.com/d/msg/mozilla.governance/kAyVlhfEcXg/Eqyx1X62BQAJ mozilla.governance], [https://groups.google.com/forum/#!topic/mozilla.dev.apps.seamonkey/MvmEOIOXPxE mozilla.dev.apps.seamonkey], [https://groups.google.com/forum/#!topic/tb-planning/bigvCJtidHE tb-planning], [https://blog.lizardwrangler.com/2015/12/03/thunderbird-update/ blog.lizardwrangler.com]
** discussions in [https://groups.google.com/d/msg/mozilla.governance/kAyVlhfEcXg/Eqyx1X62BQAJ mozilla.governance], [https://groups.google.com/forum/#!topic/mozilla.dev.apps.seamonkey/MvmEOIOXPxE mozilla.dev.apps.seamonkey], [https://groups.google.com/forum/#!topic/tb-planning/bigvCJtidHE tb-planning], [https://blog.lizardwrangler.com/2015/12/03/thunderbird-update/ blog.lizardwrangler.com]
Line 148: Line 146:
* '''Fundamental core features''' Firefox/Mozilla plans to remove:
* '''Fundamental core features''' Firefox/Mozilla plans to remove:
** {{Bug|1222546}} Product plan: remove support for heavyweight themes
** {{Bug|1222546}} Product plan: remove support for heavyweight themes
*** if effective for all Toolkit applications, would render most 3rd-party themes disfunct
*** If effective for all Toolkit applications, would render most 3rd-party themes disfunct
*** no sufficiently plausible specifics provided 'why' full themes 'must' no longer be supported
*** No sufficiently plausible specifics provided 'why' full themes 'must' no longer be supported
**** no clear statements by the Firefox drivers, bug has been restricted for comments since
*** No clear statements by the Firefox drivers, bug has been restricted for comments since
**** discussion diverted to https://discourse.mozilla-community.org/t/planning-the-future-of-complete-themes/
*** Discussion diverted to https://discourse.mozilla-community.org/t/planning-the-future-of-complete-themes/
***** see bsmedberg's post [https://discourse.mozilla-community.org/t/planning-the-future-of-complete-themes/5306/14 #14], targeted for Gecko 49 (April 2016).
*** See bsmedberg's post [https://discourse.mozilla-community.org/t/planning-the-future-of-complete-themes/5306/14 #14], targeted for Gecko 49 (April 2016).
*** may prohibit Modern theme being shipped with or installed in SeaMonkey
*** may prohibit Modern theme being shipped with or installed in SeaMonkey
*** removal is "decided" without any clear alternative envisioned
*** removal is "decided" without any clear alternative envisioned
** The toolkit help viewer is going away. Neil is working on resuscitating the old XPFE help viewer which apparently has more features.  
** The toolkit help viewer is going away. Neil is working on resuscitating the old XPFE help viewer which apparently has more features.  
* '''IanN''' thinks it would be useful to remind people on the newsgroups / forums that they can contribute by triaging. '''Tonymec''' will post a reminder to newsgroups / forums. See {{Bug|1092632}} <tt>(Sm_tri_HowTo) Document how to triage SeaMonkey bugs</tt>.
 
** The HowTo page has been moved to [[SeaMonkey/QA/Triage HowTo]]. No one having objected (or even reacted), {{bug|1092632}} is now RESOLVED FIXED. See its comment #18 for the announcement URLs.
[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 64 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 64 review]
Line 170: Line 167:
*** more work appears to be needed to download necessary 3rd-party Content Decryption Modules, some UI can probably be ported from Firefox
*** more work appears to be needed to download necessary 3rd-party Content Decryption Modules, some UI can probably be ported from Firefox


* '''What about declaring linux-x86_64 builds found at seamonkey-project.org and at ftp.m.o as "official"&nbsp;?'''
* '''What about declaring linux-x86_64 builds found at seamonkey-project.org and at ftp.m.o as "official"&nbsp;?''' — [[User:Tonymec|Tonymec]] ([[User talk:Tonymec|talk]]) 13:56, 7 October 2015 (PDT)
On October 7 two people asked in #seamonkey at a few minutes' interval when there would be "official" 64-bit SM builds for Linux. I pointed them to the x86_64 release at the bottom of the "Other languages" release page for 2.38 and to the x86_64 2.40a2 aurora &amp; 2.41a1 trunk builds at the bottom of the ftp.m.o nightly/latest-comm-* pages but they said these were not "official".
** On October 7 two people asked in #seamonkey at a few minutes' interval when there would be "official" 64-bit SM builds for Linux. I pointed them to the x86_64 release at the bottom of the "Other languages" release page for 2.38 and to the x86_64 2.40a2 aurora &amp; 2.41a1 trunk builds at the bottom of the ftp.m.o nightly/latest-comm-* pages but they said these were not "official".
 
** How are we going to get out of the following vicious circle? 64-bit builds are not "official" because too few users, and users don't install them (some even prefer compiling their own) because they aren't "official".
So — how are we going to get out of the following vicious circle? 64-bit builds are not "official" because too few users, and users don't install them (some even prefer compiling their own) because they aren't "official".
** Maybe change the online documentation? (perhaps as part of {{bug|1208822}} "System Requirements page needs update"?)
 
** [ewong:] what's the prerequisites of making the Linux64 builds 'official' aside for the issue of getting the tests done for Linux64; but our testing infrastructure is busted. {{bug|1209378}}
Maybe change the online documentation? (perhaps as part of {{bug|1208822}} "System Requirements page needs update"?)
 
— [[User:Tonymec|Tonymec]] ([[User talk:Tonymec|talk]]) 13:56, 7 October 2015 (PDT)
 
* [ewong:] what's the prerequisites of making the Linux64 builds 'official' aside for the issue of getting the tests done for Linux64; but our testing infrastructure is busted. {{bug|1209378}}
--- Discussion on locale translations for DOMi and Chatzilla ---
--- Discussion on locale translations for DOMi and Chatzilla ---
* [frg] More or less obsolete items removed 03/27. One l10n bug remaining but hopefully fixed soon.
* [frg] More or less obsolete items removed 03/27. One l10n bug remaining but hopefully fixed soon.
Confirmed users
2,595

edits

Navigation menu