SeaMonkey/StatusMeetings/2017-02-07: Difference between revisions

m
no edit summary
mNo edit summary
Line 13: Line 13:
* Nominees for Friends of the Fish Tank:
* Nominees for Friends of the Fish Tank:
** '''TBD'''
** '''TBD'''
=== Action Items ===
(who needs to do what that hasn't been recorded in a bug)
We should assign people to the open items.
'''NEW'''
* —
'''OPEN'''
* Mozilla plans to check in l20n early in the Firefox 53 release cycle. Unclear what this means for comm-central and the build configs. Needs to be monitored.
** in light of this and [[#Release_Train|other changes in 52+]], releasing 2.49.x off 52 ESR becomes an increasingly attractive option
* Google announced V4 of the safebrowsing api. No actions currently needed. Firefox adds support for it in {{bug|1167038}}.
* Google API key for Safe Browsing. Ewong/Callek about getting it loaded onto the build machines.
** Per {{bug|903439#c10}}, ewong has a Google API key (stating that for Geolocation service). Safe Browsing keys are on the builders according to ewong. The build configs are currently being 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
* '''IanN''' [http://www.seamonkey-project.org/dev/project-areas SeaMonkey project areas] is very outdated. '''IanN''' plans to prepare the final draft of the project areas this week.
* '''frg''' suggests a tabbrowser.xml overhaul because it's becoming harder to backport fixes from Firefox.
** '''IanN''' suggests doing small patches which are easier to review.
* '''frg''' thinks we should try to get our own builders.
** where, which build environment, how to cover associated costs?
** 2.46 release: improvise with contributed builds?
* —
'''CLOSED'''
* —


=== Special agenda from the last meeting (for reference) ===
=== Special agenda from the last meeting (for reference) ===
Confirmed users
2,595

edits