Add FAQ docs for releaseduty

RESOLVED FIXED

Status

Release Engineering
Releases
RESOLVED FIXED
2 years ago
5 months ago

People

(Reporter: mtabara, Assigned: mtabara)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Assignee)

Description

2 years ago
We should build up a draft of FAQ releaseduty-related. This could better enhance the context that already exists in the wikis and help people understand part of the rough edges while grasping this role for the first time.
(Assignee)

Comment 1

2 years ago
Created first draft of it at[1]. I've linked it up under RelEng/releaseduty at [2] as well as in Releng/RelengChecklist at [3]. Will start completing the missing bits as soon as I get knowledge on each section.


[1]: https://wiki.mozilla.org/ReleaseEngineering/Releaseduty/FAQ
[2]: https://wiki.mozilla.org/ReleaseEngineering/Releaseduty
[3]: https://wiki.mozilla.org/Releases/RelEngChecklist#General
(Assignee)

Comment 2

2 years ago
Iterated over it several times to complete with information. As far as it looks it's an ongoing process that will last during my entire releaseduty and after that. There are still fields that need to be completed but the first draft is looking good. We have a skeleton to build on.

Am closing this for now, will reopen if needed.
(Assignee)

Updated

2 years ago
Status: NEW → RESOLVED
Last Resolved: 2 years ago
Resolution: --- → FIXED
(Assignee)

Comment 3

2 years ago
I'm reopening this. At a second thought, it'd be great if someone else from the releaseduty team would take a glance at it to do a logic-sanity check.  

@rail: this is not urgent and has low-priority.
Status: RESOLVED → REOPENED
Flags: needinfo?(rail)
Resolution: FIXED → ---
I read the FAQ a couple of times and haven't found anything controversial.
Flags: needinfo?(rail)
(Assignee)

Comment 5

2 years ago
Thanks Rail for double-checking the docs. I also pinged some people about some of the remaining questions. The process of adding/improving will be an ongoing one so I'll close this bug for now.
Status: REOPENED → RESOLVED
Last Resolved: 2 years ago2 years ago
Resolution: --- → FIXED
(Assignee)

Updated

5 months ago
See Also: → bug 1381472
You need to log in before you can comment on or make changes to this bug.