768
edits
SeaMonkey/StatusMeetings/2017-04-02: Difference between revisions
Jump to navigation
Jump to search
status meeting notes
(status meeting notes) |
|||
| Line 11: | Line 11: | ||
== Agenda == | == Agenda == | ||
* Who's taking minutes? -> ''' | * Who's taking minutes? -> '''frg''' | ||
* Nominees for Friends of the Fish Tank: | * Nominees for Friends of the Fish Tank: | ||
** ''' | ** '''frg for not being nominated in a few weeks :) ''' | ||
=== Action Items === | === Action Items === | ||
| Line 20: | Line 20: | ||
'''NEW''' | '''NEW''' | ||
* Something needs to be done about the lack of developers and support staff or SeaMonkey will be no more in the near future. '''frg''' will prepare an "asking for help" draft for the council. When final it will be posted in the various SeaMonkey newsgroups. | |||
* — | * — | ||
'''OPEN''' | '''OPEN''' | ||
| Line 27: | Line 28: | ||
** In 2.51+ additional preferences are needed. The blocklist interface will also be changed. You now see errors in a new 2.51 profile. No bug has been filed for this as of now. | ** In 2.51+ additional preferences are needed. The blocklist interface will also be changed. You now see errors in a new 2.51 profile. No bug has been filed for this as of now. | ||
* Google API key for Safe Browsing. Ewong/Callek about getting it loaded onto the build machines. | * Google API key for Safe Browsing. Ewong/Callek about getting it loaded onto the build machines. | ||
** Per {{bug|903439#c10}}, ewong confirmed that he has the Google API key. Safe Browsing keys are on the builders according to ewong. The build config config changes are not yet checked in. Ewong contacted Mozilla for a geolocation key. | ** Per {{bug|903439#c10}}, ewong confirmed that he has the Google API key. Safe Browsing keys are on the builders according to ewong. The build config config changes are not yet checked in. Ewong contacted Mozilla for a geolocation key. The Google API key can be used instead of the Mozilla key with some pref changes. rsx11m will open a bug to use the Google key for now in all trees ({{bug|1352850}} created after meeting). | ||
* '''IanN''' has spoken to mcsmurf about members list. Members mailing-list and council appointments are ready to be reviewed. | * '''IanN''' has spoken to mcsmurf about members list. Members mailing-list and council appointments are ready to be reviewed. | ||
** TODO: Add Adrian Kalla to RelEng team. Overall no change as of today | ** TODO: Add Adrian Kalla to RelEng team. Overall no change as of today | ||
| Line 40: | Line 41: | ||
** Depending on the outcome builder software would also need to be selected. Adrian is in favor of Jenkins because buildbot expertise is rare. | ** Depending on the outcome builder software would also need to be selected. Adrian is in favor of Jenkins because buildbot expertise is rare. | ||
** Due to cost and availability the generation of daily builds would need to be cut back. The team doesn't see much problems here and a new schedule could be worked out. | ** Due to cost and availability the generation of daily builds would need to be cut back. The team doesn't see much problems here and a new schedule could be worked out. | ||
** '''IanN''' mentioned taskcluster as an alternative to buildbot. | ** '''IanN''' mentioned taskcluster as an alternative to buildbot. According to '''ewong''' and '''frg''' it looks complex and Mozilla specific. | ||
*** The Thunderbird project plans to hire a designer for a new build infrastructure in the near future. | |||
** There are plans by Mozilla to do cross compiles on Linux for Windows and macOS. Not finalized yet. | |||
* — | * — | ||
'''CLOSED''' | '''CLOSED''' | ||
* — | * — | ||
| Line 85: | Line 87: | ||
*** '''Callek:''' Regarding the windows systems, sadly no progress yet. I'm hopeful we can get done sooner than later, I'm realistic expecting it won't be any time soon. | *** '''Callek:''' Regarding the windows systems, sadly no progress yet. I'm hopeful we can get done sooner than later, I'm realistic expecting it won't be any time soon. | ||
** Langpacks aren't updated when auto-updating SeaMonkey because they aren't uploaded to AMO. The solution requires changes in SeaMonkey RelEng (and possibly AMO). | ** Langpacks aren't updated when auto-updating SeaMonkey because they aren't uploaded to AMO. The solution requires changes in SeaMonkey RelEng (and possibly AMO). | ||
** wrt {{bug|1155011}}, we already have a Soccoro token. | ** wrt {{bug|1155011}}, we already have a Soccoro token. The patches on {{bug|1155013}} require approval and then pushed and the work-around patches backed out. | ||
* See [[SeaMonkey/StatusMeetings/RelEng|RelEng]] page for the RelEng status history. | * See [[SeaMonkey/StatusMeetings/RelEng|RelEng]] page for the RelEng status history. | ||
<!-- Comment out this section if nothing new fixed --> | <!-- Comment out this section if nothing new fixed --> | ||
| Line 96: | Line 98: | ||
* SeaMonkey 2.46 was released December 22, 2016, tracked in {{Bug|1294433}} | * SeaMonkey 2.46 was released December 22, 2016, tracked in {{Bug|1294433}} | ||
* SeaMonkey 2.48 will be the next release tracked in {{Bug|1336310}} (general beta issues in {{bug|1328886}}) | * SeaMonkey 2.48 will be the next release tracked in {{Bug|1336310}} (general beta issues in {{bug|1328886}}) | ||
** | ** SeaMonkey 2.48 beta 1 is in candidates [https://archive.mozilla.org/pub/seamonkey/candidates/2.48b1-candidates/build7/]. | ||
'''ewong''' wants to figure out if updates from 2.39b1 can be made to work so that the 2.48 release will upgrade from 2.46 without problems. | |||
** l10n problems from 2.46 are still not solved. Extensions again can not be shipped bundled with this release. A removal patch has been checked in. DOMi and cZ tags have nevertheless been updated for a future release. | ** l10n problems from 2.46 are still not solved. Extensions again can not be shipped bundled with this release. A removal patch has been checked in. DOMi and cZ tags have nevertheless been updated for a future release. | ||
*** l10n problem is tracked in ({{bug|1231349}}). | *** l10n problem is tracked in ({{bug|1231349}}). | ||
| Line 117: | Line 120: | ||
* ewong: Suggests the following: | * ewong: Suggests the following: | ||
** Officially release a linux64 build (incl. tests) | ** Officially release a linux64 build (incl. tests) | ||
*** Start with | *** Start with comm-central trunk. | ||
*** Not entirely sure what is needed to make it official. Need to correspond with Callek. | *** Not entirely sure what is needed to make it official. Need to correspond with Callek. | ||
** Build an unofficial (contributed build) Win64 build. [akin to the status that Linux64 has now.] | ** Build an unofficial (contributed build) Win64 build. [akin to the status that Linux64 has now.] | ||
*** Start with | *** Start later with comm-central we need to iron out the build issues, though right now, having just finished a W64 build; but I don't know how the tests are going to work though this will need to wait). | ||
*** Currently tracked by {{bug|482143}}. | *** Currently tracked by {{bug|482143}}. | ||
| Line 142: | Line 145: | ||
* The [http://addonconverter.fotokraina.com/amo-browsing/ AMO Browsing for SeaMonkey] extension, which makes AMO pages a lot more SeaMonkey-friendly, is mature. It was developed by LemonJuice (of Add-on Converter fame), and Tonymec, who tested it and now uses it, supports it enthusiastically. The author proposes to add it as a "built-in extension" besides ChatZilla, DOMi and the like. What do you think? (See also {{bug|1145026|Bug 1145026: AMO Add-On-Descriptions: Add link function leading to SeaMonkey add-on-converter and filling URL input pane}}; the extension actually does much more than the bug's Summary implies: for instance it gets rid of the stupid "You need Firefox 10 or later" popups. | * The [http://addonconverter.fotokraina.com/amo-browsing/ AMO Browsing for SeaMonkey] extension, which makes AMO pages a lot more SeaMonkey-friendly, is mature. It was developed by LemonJuice (of Add-on Converter fame), and Tonymec, who tested it and now uses it, supports it enthusiastically. The author proposes to add it as a "built-in extension" besides ChatZilla, DOMi and the like. What do you think? (See also {{bug|1145026|Bug 1145026: AMO Add-On-Descriptions: Add link function leading to SeaMonkey add-on-converter and filling URL input pane}}; the extension actually does much more than the bug's Summary implies: for instance it gets rid of the stupid "You need Firefox 10 or later" popups. | ||
* The [https://addons.mozilla.org/addon/html-validator/ HTML Validator] adds HTML validation to SeaMonkey. [https://addons.mozilla.org/en-US/firefox/addon/html-validator/versions/0.9.7.5.beta The Beta version] is no more Windows-only: it boasts support for W32/64, L32/64 and Mac 32/64 Universal in a single XPI. It does not officially support trunk builds but in Tonymec's experience it worked with them last year. It offers a choice of validators: Tidy, SGML (same algorithm as [https://validator.w3.org the W3C validator] but client-side) or both. Caveat: The toolbar button gives no results for HTML5, you need View Source for that. See [http://users.skynet.be/mgueury/mozilla/index.html the developer's site] for details. | * The [https://addons.mozilla.org/addon/html-validator/ HTML Validator] adds HTML validation to SeaMonkey. [https://addons.mozilla.org/en-US/firefox/addon/html-validator/versions/0.9.7.5.beta The Beta version] is no more Windows-only: it boasts support for W32/64, L32/64 and Mac 32/64 Universal in a single XPI. It does not officially support trunk builds but in Tonymec's experience it worked with them last year. It offers a choice of validators: Tidy, SGML (same algorithm as [https://validator.w3.org the W3C validator] but client-side) or both. Caveat: The toolbar button gives no results for HTML5, you need View Source for that. See [http://users.skynet.be/mgueury/mozilla/index.html the developer's site] for details. | ||
* In Gecko 52 obsolete toolkit parts were removed in {{bug|1312143}}. This may cause problems with older add-ons when SeaMonkey 2.49 hits the road. The 2.49 release notes should mention it. Chatzilla and DOMi were affected and | * In Gecko 52 obsolete toolkit parts were removed in {{bug|1312143}}. This may cause problems with older add-ons when SeaMonkey 2.49 hits the road. The 2.49 release notes should mention it. Chatzilla and DOMi were affected and were fixed. | ||
=== 2.x (Last, Current, Next) === | === 2.x (Last, Current, Next) === | ||
| Line 275: | Line 278: | ||
==== IanN ==== | ==== IanN ==== | ||
==== Rainer Bielefeld ==== | ==== Rainer Bielefeld ==== | ||
==== Ratty ==== | ==== Ratty ==== | ||
| Line 296: | Line 292: | ||
* End-user information and discussion on [http://forums.mozillazine.org/viewforum.php?f=51 MozillaZine]. | * End-user information and discussion on [http://forums.mozillazine.org/viewforum.php?f=51 MozillaZine]. | ||
==== stefanh ==== | ==== stefanh ==== | ||
==== tonymec ==== | ==== tonymec ==== | ||