873663 - Need review/scheduling for pushlog affecting hook change via bug 873643

Status: RESOLVED FIXED

(Infrastructure & Operations :: Change Requests, task)

Description

[hwine]

Yes, this is a "new" use of CAB, but we'd like to discuss. :joduinn has confirmed with :gps that this hook change is not urgent.

While this is a dev initiated change, and historically IT's role has been to only deploy hooks. However recent examples have shown how impacting "simple" changes to tbpl can be. This change impacts tbpl by changing how one of the input sources to tbpl is handled.

Ideally, there would be a staging environment to demonstrate the change is harmless. (In fact, the dev assumed there was one.) We may not have that luxury yet, but we can at least coordinate notification and timing of the deployment.

Major consumers of pushlog include:
 - tbpl
 - releng build machinery
 - l10n machinery

Comment 1

[hwine]

Per CAB meeting, want to find a good time when all major customers of pushlog can quickly double check after update.

If coordination becomes too difficult, we'll have to hold for a staging server (bug to be filed, but mostly in place from bug 781955).

Comment 2

[hwine]

Coordinated in bug 873643 and done successfully