343
edits
Release Management/Release Process: Difference between revisions
Jump to navigation
Jump to search
Release Management/Release Process (view source)
Revision as of 01:03, 11 February 2026
, 11 Februarytypo
Diannasmith (talk | contribs) (spacing) |
Diannasmith (talk | contribs) (typo) |
||
| Line 60: | Line 60: | ||
* Once the patch is ready set the approval flag appropriately depending on which branches are affected | * Once the patch is ready set the approval flag appropriately depending on which branches are affected | ||
2) Members of Release Management go through all the bugs nominated for tracking and if in agreement that this bug needs to be investigated in that release we will go ahead and set '''tracking- | 2) Members of Release Management go through all the bugs nominated for tracking and if in agreement that this bug needs to be investigated in that release we will go ahead and set '''tracking-FirefoxXX: +'''. Once we track a bug for a particular release we will make sure to follow-up on the progress or help with any road blockers till you have a patch nominated for approval. | ||
'''Note:''' Bugs denied for ''tracking-FirefoxXX'' are still important. It merely means based on the information we have now,we do not feel the bug would prevent us from shipping a release. If new information comes to light, you need help getting more data before you can make the case for us to track, or you disagree with our assessment feel free to renominate again with additional justification. | '''Note:''' Bugs denied for ''tracking-FirefoxXX'' are still important. It merely means based on the information we have now,we do not feel the bug would prevent us from shipping a release. If new information comes to light, you need help getting more data before you can make the case for us to track, or you disagree with our assessment feel free to renominate again with additional justification. | ||