Confirmed users
2,416
edits
(→frg: status) |
(→Action Items: per mailing-list discussion) |
||
| Line 22: | Line 22: | ||
'''OPEN''' | '''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. | * 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 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. | * Google API key for Safe Browsing. Ewong/Callek about getting it loaded onto the build machines. | ||
| Line 31: | Line 32: | ||
** '''IanN''' suggests doing small patches which are easier to review. | ** '''IanN''' suggests doing small patches which are easier to review. | ||
* '''frg''' thinks we should try to get our own builders. | * '''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''' | '''CLOSED''' | ||