Bugzilla

Thanks @yulia

Re https://bugzilla.mozilla.org/show_bug.cgi?id=1711872#c12 and tracking shipping/docs, I will ask Ruth to have a look at this as she's currently running the process and might already have this in hand.

That said, my 2 bits:
- I "believe" that docs process is simply to look for bugs that have dev-docs-needed and/or that have the appropriate release tagged in the tracking section. 
- I would love tag(s) in the tracking section that immediately let me know release status of a particular fix. Some of the useful things to know
  - shipped (in a release build) or not. 
  - if not shipped, in which releases - nightly, beta, etc?
  - intent to ship target release (if not released). Just an indicator.
  - if protected by a preference or not. 
- Further, it would also save a lot of time if authors summarised what delivered, in particular if it differs in any way from the description. That is not relevant to this particular issue which has a really excellent spec. Often though there is a large chain of discussion and evolution for bug fixes, and what finally delivered is pretty unclear.

Hope that makes sense.

Thanks @yulia

Re https://bugzilla.mozilla.org/show_bug.cgi?id=1711872#c12 and tracking shipping/docs, I will ask Ruth to have a look at this as she's currently running the process and might already have this in hand.

That said, my 2 bits:
- I "believe" that docs process is simply to look for bugs that have dev-docs-needed and/or that have the appropriate release tagged in the tracking section. 
- IMO it should be clear from a bug report which releases any fix ships to. 
- I would love tag(s) in the tracking section that perhaps let me know
  - shipped (in a release build) or not. 
  - if not shipped, in which releases - nightly, beta, etc?
  - intent to ship target release (if not released). Just an "guess" is fine for planning, not a committment.
  - if protected by a preference or not, and ideally what that is.
- Further, it would also save a lot of time if authors summarised what delivered, in particular if it differs in any way from the description. That is not relevant to this particular issue which has a really excellent spec. Often though there is a large chain of discussion and evolution for bug fixes, and what finally delivered is pretty unclear.

Hope that makes sense.