List Name: mozilla.dev.puppetagain List Admin: firstname.lastname@example.org, Short Description: Announcements and coordination of the development of PuppetAgain Long Description: What is PuppetAgain? https://wiki.mozilla.org/ReleaseEngineering/PuppetAgain This list is a means to announce and coordinate changes to PuppetAgain across the teams using the system. If you are interested in this list, you probably also want to follow the "Infrastructure & Operatoins :: RelOps: Puppet" component. Justification / Special Instructions:
I guess I shouldn't leave the justification blank :) This is becoming a cross-team tool, and sometimes requires some rather intricate processes to ugprade or land changes. So we'll need some more "push"-oriented means to announce and discuss those changes than Bugzilla.
Hi Dustin: bmo and other tools are in the mozilla.tools namespace - is mozilla.tools.puppetagain OK? Gerv
Sure, that's sounds better - I missed those on https://www.mozilla.org/about/forums/
OK. Over to server-ops. Gerv
Assignee: gerv → server-ops
Summary: Discussion Forum: mozilla.dev.puppetagain → Discussion Forum: mozilla.tools.puppetagain
Component: Discussion Forums → Server Operations
QA Contact: justdave → shyam
Status: NEW → ASSIGNED
Whiteboard: [waiting for Giganews and Google]
Whiteboard: [waiting for Giganews and Google] → [waiting for Google]
This has been completed.
Status: ASSIGNED → RESOLVED
Last Resolved: 5 years ago
Resolution: --- → FIXED
Whiteboard: [waiting for Google]
Product: mozilla.org → mozilla.org Graveyard
You need to log in before you can comment on or make changes to this bug.