[Shield] QA tracker for manual Testing

NEW
Unassigned

Status

2 years ago
6 months ago

People

(Reporter: adrian_sv, Unassigned)

Tracking

(Depends on: 8 bugs)

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

2 years ago
This is a meta bug that will collect all issues found during testing related to Shield System Addon: normandy control panel + FF - system addon / recipe integration.
(Reporter)

Updated

2 years ago
Depends on: 1342064

Updated

2 years ago
Depends on: 1342094
(Reporter)

Updated

2 years ago
Depends on: 1342140

Updated

2 years ago
Depends on: 1342399

Updated

2 years ago
Depends on: 1342444
(Reporter)

Updated

2 years ago
Depends on: 1342883
(Reporter)

Updated

2 years ago
Depends on: 1342906
(Reporter)

Updated

2 years ago
Depends on: 1342915
(Reporter)

Updated

2 years ago
Depends on: 1342920
Adrian: Are all the dependent bugs to this one blockers for QA approval? Some, like bug 1342140, are improvements that IMO shouldn't block the release.
Flags: needinfo?(adrian.florinescu)
(Reporter)

Comment 2

2 years ago
(In reply to Michael Kelly [:mkelly,:Osmose] from comment #1)
> Adrian: Are all the dependent bugs to this one blockers for QA approval?
> Some, like bug 1342140, are improvements that IMO shouldn't block the
> release.
In this particular case we're using block just to gather all the logged bugs under one meta bug, that being the QA metabug. If that is confusing and you use blocking as literally blocking, we can remove the block for the ones that we are not finding relevant for Shield to move further.
Flags: needinfo?(adrian.florinescu)
(In reply to Adrian Florinescu [:AdrianSV] from comment #2)
> (In reply to Michael Kelly [:mkelly,:Osmose] from comment #1)
> > Adrian: Are all the dependent bugs to this one blockers for QA approval?
> > Some, like bug 1342140, are improvements that IMO shouldn't block the
> > release.
> In this particular case we're using block just to gather all the logged bugs
> under one meta bug, that being the QA metabug. If that is confusing and you
> use blocking as literally blocking, we can remove the block for the ones
> that we are not finding relevant for Shield to move further.

Nah, how you're doing it now is fine. Just wanted to make sure we're both on the same page, and we are. Thanks!

Updated

2 years ago
Depends on: 1346160

Updated

2 years ago
Depends on: 1346198

Updated

2 years ago
Depends on: 1348885
(Reporter)

Updated

2 years ago
Depends on: 1349279
(Reporter)

Updated

2 years ago
Depends on: 1349574
(Reporter)

Updated

2 years ago
Depends on: 1349576
(Reporter)

Updated

2 years ago
Depends on: 1349596

Updated

2 years ago
Depends on: 1353741

Updated

2 years ago
Depends on: 1353747
(Reporter)

Updated

2 years ago
Depends on: 1354125
(Reporter)

Updated

2 years ago
Depends on: 1354151

Updated

2 years ago
Depends on: 1354176
No longer depends on: 1348885
Depends on: 1445938

Updated

8 months ago
Depends on: 1446002
Depends on: 1446007
(Reporter)

Updated

8 months ago
Depends on: 1446421
(Reporter)

Updated

8 months ago
Depends on: 1446438
(Reporter)

Updated

8 months ago
Depends on: 1446445
Depends on: 1447025
(Reporter)

Updated

8 months ago
Depends on: 1447254
(Reporter)

Updated

8 months ago
Depends on: 1447305
(Reporter)

Updated

8 months ago
Depends on: 1447324
Depends on: 1450690
Depends on: 1453619
Depends on: 1460893
(Reporter)

Updated

6 months ago
Depends on: 1462290
You need to log in before you can comment on or make changes to this bug.