One issue we have with the current method of closing Gaia is disseminating that information to the various stakeholders (since we can't use commit hooks to strictly enforce it). In the past, we've resorted to emailing dev-b2g and dev-gaia for every closure. However, we've received feedback from numerous devs that this isn't scaling well. Nor is relying on someone with ops to change the #gaia topic every time the status changes.
In order to try to make it easier for people to find out the current status of Gaia, I've added it to Treestatus. Note that this is a "toothless" change in that opening/closing doesn't actually do anything by itself - it still needs to be closed on GitHub via the usual methods. Bug 1145244 has been filed for investigating whether we can enable Treestatus to do the actual work rather than just acting as a proxy for that information. It is my intent that this change replace sheriffs emailing dev-b2g and dev-gaia in favor of allowing API consumers to track the status on their own (via browser extensions, IRC bots, etc). If anybody objects, let me know now. Also, Gaia's status page can be seen at https://treestatus.mozilla.org/Gaia Thanks, Ryan
_______________________________________________ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g
