Closed Bug 1452285 Opened 7 years ago Closed 7 years ago

Release Engineering BMO component major reorg

Categories

(bugzilla.mozilla.org :: Administration, task)

Product:
bugzilla.mozilla.org
Component:
Administration
Version:
Production
Type:
task
Priority:
Not set
Severity:
normal

Tracking

()

Status:
RESOLVED FIXED

People

(Reporter: mtabara, Assigned: dylan)

References

Details

User Story

Applications: Balrog (backend)
Triage owner: bhearsum
Short description: "Issues related to the core, business logic, and REST API of our update server (Balrog)."

Applications: Balrog (frontend)
Triage owner: bhearsum
Short description: "Issues related to the web admin interface of our update server (Balrog)."

Applications: MozharnessCore
Triage owner: jlund
Short description: "Issues related to mozharness's core, Mozilla's configuration-driven script harness should be filed here."

Applications: Shipit (backend)
Triage owner: rail
Short description: "Issues related to the core, business logic and REST API of our release dashboard (Ship-it)."

Applications: Shipit (frontend)
Triage owner: rail
Short description: "Issues related to the web admin interface of our release dashboard (Ship-it)."

Applications: TreeStatus
Triage owner: garbas
Short description: "Issues related to the core and business logic of our tool (TreeStatus) to toggle open/closed state of gecko-related development trees."

Applications: ToolTool
Triage owner: garbas
Short description: "Issues related to the core functionality of our client program that manipulates the generic binary artifacts (Tooltool)."

Applications: ServicesCore
Triage owner: garbas
Short description: "Issues related to the Services's core, RelEng's centrepoint to source, maintain and deploy various applications."

Documentation
Triage owner: sfraser
Short description: "Any documentation related item"

General
Triage owner: catlee
Short description: "This component is used for goals, tracking bugs, and any general RelEng work that spans across different RelEng components. Anything that doesn't fit in any other component goes here."

Release Automation:updates
Triage owner: mtabara
Short description: "Issues related to generation, submission and serving of updates (balrogworkers, tools, etc)"

Release Automation:signing
Triage owner: aki
Short description: "Issues related to signing within the release workflow"

Release Automation:uploading
Triage owner: mtabara
Short description: "Issues related to transferring artifacts from one place to another (beetmoverworkers)"

Release Automation:pushapk
Triage owner: jlorenzo
Short description: "Issues related to transferring mobile APKs to various cloud stores"

Release Automation:snap
Triage owner: jlorenzo
Short description: "Issues related to packaging and delivering Firefox in Ubuntu's app store"

Release Automation:l10n
Triage owner: Callek
Short description: "Issues related to localization within the release workflow"

Release Automation:other
Triage owner: sfraser
Short description: "Anything that doesn't fit in any of the sibling components"

Custom Release Requests
Triage owner: jlund
Short description: "Issues related to custom builds of Firefox produced by Mozilla, or updates to those builds"

Release Requests
Triage owner: jlund
Short description: "Issues related to specific releases, or updates to those releases"
We need to reorg our component from the ground. Will follow-up in a bit with more details.
User Story: (updated)
I've added our desired end state in the User Story as instructed. Following up with more instructions regarding our existing components: * "Balrog:Backend" component renamed to "Applications: Balrog (backend)" * "Balrog:Frontend" component renamed to "Applications: Balrog (frontend)" * "Mozharness" component renamed to "Applications: MozharnessCore" * "Releases" component renamed to "Release Requests" * "Releases: Custom builds" component renamed to "Custom Release Requests" * "Ship it" component renamed to "Applications: Shipit (backend)" * "Release Automation" component renamed to "Release Automation:other" * "Treestatus" component renamed to "Applications: TreeStatus" * no-op for "General component" * "General Automation" component is to be killed and any open bugs moved under "General" * "Buildduty" component moved from Release Engineering umbrella to Infrastructure & Operations, keeping its "Buildduty" name * "Platform Support" component is to be killed and any open bugs migrated to Infrastructure & Operations::Buildduty * "Loan Requests" component is to be killed and any open bugs migrated to Infrastructure & Operations::Buildduty * "Buildduty" component is to be killed and any open bugs migrated to Infrastructure & Operations::Buildduty
As confirmed over the email, any timing would be good for this, if a short heads-up is done in #releng. Thank you!
Assignee: nobody → dylan
Okay, this should be done. Mostly for my benefit is the export of the operations I performed for this. [+] "Balrog:Backend" component renamed to "Applications: Balrog (backend)" [+] "Balrog:Frontend" component renamed to "Applications: Balrog (frontend)" [+] "Mozharness" component renamed to "Applications: MozharnessCore" [+] "Releases" component renamed to "Release Requests" [+] "Releases: Custom builds" component renamed to "Custom Release Requests" [+] "Ship it" component renamed to "Applications: Shipit (backend)" [+] "Release Automation" component renamed to "Release Automation:other" [+] "Treestatus" component renamed to "Applications: TreeStatus" [+] Check Applications: Balrog (backend) [+] Check Applications: Balrog (frontend) [+] Check Applications: MozharnessCore [+] Check Applications: Shipit (backend) [+] Check Applications: Shipit (frontend) [+] Check Applications: TreeStatus [+] Check Applications: ToolTool [+] Check Documentation [+] Check Applications: ServicesCore [+] Check General [+] Check Release Automation:updates [+] Check Release Automation:signing [+] Check Release Automation:uploading [+] Check Release Automation:pushapk [+] Check Custom Release Requests [+] Check Release Requests [+] Check Release Automation:other [+] Check Release Automation:l10n [+] Check Release Automation:snap [+] "General Automation" component is to be killed and any open bugs moved under "General" [+] "Buildduty" component moved from Release Engineering umbrella to Infrastructure & Operations, keeping its "Buildduty" name [+] "Platform Support" component is to be killed and any open bugs migrated to Infrastructure & Operations::Buildduty [+] "Loan Requests" component is to be killed and any open bugs migrated to Infrastructure & Operations::Buildduty [+] "Buildduty" component is to be killed and any open bugs migrated to Infrastructure & Operations::Buildduty
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → FIXED
Thank you so much for taking this over the finish line!
Depends on: 1465577
See Also: → 1556946
You need to log in before you can comment on or make changes to this bug.