Just a reminder to front-end application developers that fx-team has been transformed into an inbound-alternate, intended for shepherding front-end code into mozilla-central. The same check-in policies, support from sheriffs, tree hooks, and (lack of) "watching" requirements are in place, such that you should be able to switch to landing things on fx-team without any other changes in your routine.
That means that if you're working on code that could reasonably be described as "on top of Gecko" (e.g. code in browser/, toolkit/, mobile/, etc.), you should feel free to land things on fx-team instead of on inbound. The goal is to help distribute the landing load across multiple branches, to avoid too many inbound bottlenecks. Some additional information is available in my original post: https://mail.mozilla.org/pipermail/firefox-dev/2013-July/000618.html Gavin
_______________________________________________ mobile-firefox-dev mailing list [email protected] https://mail.mozilla.org/listinfo/mobile-firefox-dev
