ReleaseEngineering/Breakout Sessions/Easing Handling of Network Flows

If you find yourself requesting flows, wondering if a flow is in place, or discovering undesirable flows, come along!

The proposal on the table is detailed in bug 1026102, but briefly the idea is to record *all* flows of interest to releng in the format of Python unit tests. Requested changes to the flows come with changes to the tests, and the unit tests are written clearly enough that it's relatively easy to see if a particular flow should be allowed or not. This should give us an accurate, human-readable, human-writable document describing *all* flows relevant to release engineering systems.

Questions to address:

• Does this address issues you've had with flow requests?
• Is the cost in extra work and brainpower worth the reward?