We're doing another non-downtime today (Fri), as soon as FF3.5rc1 start
signing.

Notes about timing:
1) This non-downtime does *not* in any way impact RelEng doing rc1
builds. It will be different people, working on different systems. By
keeping the talos change to m-c only, developers working on 191/TM are
not impacted either, so even a surprise need to respin during the
non-downtime would be fine.
2) Doing these changes is easiest while the code is stable. If there are
developers landing lots of changes, and possibly destabilizing code,
that makes it hard for us to tell if our RelEng changes broke something.
Yesterday, the number of dev checkins is already up significantly from
day before, and I expect this trend to continue next week. The sooner we
can land these infrastructure changes, the better.

This non-downtime would allow us to rollout the following changes to
production:

bug#488367 convert talos slaves to pooled (part fix; only do m-c today)
bug#497691 Fix quoting on Tinderboxprint statements
bug#492808 Improve clobber messages
bug#448047 Fix symbol unpacking and have talos print slavename
bug#496510 Buildbot sendchanges should include revision where appropriate

These can all be done with no actual downtime, and have already been
running in staging, so we *think* they're safe. Obviously, if anything
breaks we'll revert it immediately. Lukas, our buildduty person tomorrow
will work with today's sheriff and devs if there are any questions.
Also, we'll update the tinderbox notes while this work is in progress,
just as fyi.

Obviously, if anything changes with the FF3.5rc1 work, then we'll stop
and figure out what rescheduling is needed. Assuming all goes well,
we'll watch for a day/two, and then plan another set of backlogged
changes to rollout early next week.

Questions/comments/concerns, let me know...

John.