Closed
Bug 1392686
Opened 7 years ago
Closed 3 years ago
Releaseduty training and documentation for balrog
Categories
(Release Engineering :: General, defect, P2)
Release Engineering
General
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: sfraser, Assigned: sfraser)
References
Details
(Whiteboard: [releaseduty])
Write training documentation and run a recorded training session on the internal mechanics of balrog, how to use it, and what’s expected of each role.
1. Training/docs objectives, and topics to cover
2. Fill out wiki page
3. Run/record video training
4. Use feedback from video training to iterate wiki page
Assignee | ||
Updated•7 years ago
|
Assignee: nobody → sfraser
Updated•7 years ago
|
Priority: -- → P1
Assignee | ||
Comment 2•7 years ago
|
||
Slow. Would you be up for a short topic-storming session next week?
Flags: needinfo?(sfraser)
Comment 3•7 years ago
|
||
(In reply to Simon Fraser [:sfraser] ⌚️GMT from comment #2)
> Slow. Would you be up for a short topic-storming session next week?
Let's do it!
Updated•7 years ago
|
Whiteboard: [releaseduty]
Updated•7 years ago
|
Priority: P1 → P2
Updated•7 years ago
|
Component: Applications: Balrog (frontend) → Documentation
Comment 4•3 years ago
|
||
This is recorded in various demos and https://mozilla-balrog.readthedocs.io/. Closing unless I'm missing something.
Status: NEW → RESOLVED
Closed: 3 years ago
Resolution: --- → FIXED
Updated•3 years ago
|
Component: Documentation → General
You need to log in
before you can comment on or make changes to this bug.
Description
•