Bug 1747360 Comment 23 Edit History

Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.

(In reply to EarlgreyTea from comment #22)
> I have tried Thunderbird 91.6.0, but the issue reported by Savior13 has not been fixed. Double-clicking on a cab file does not respond at all.
> Please reopen this bug.

(no need to respond to this learning point)

A learning point ... please see the fields in the `Tracking` section at the top of this bug report:
* Status = `FIXED` indicates the problem is fixed in the **development (daily) branch**.  `Target Milestone` = 98 Branch indicates the first version that is fixed. This happened in comment 8. Note, `FIXED` does not mean this is fixed in the main public release.  
* `thunderbirdnn` tracking flag on the right indicates any **beta branch** that might have also gotten the patch. This happened in comment 10.
* `thunderbird_esr91` tracking flag on the right indicates the status of the **version 91 branch**.  It is currently `affected`, meaning the patch has not yet reached that branch.  
In short, it takes time for a "FIXED" patch to get into a release.
(In reply to EarlgreyTea from comment #22)
> I have tried Thunderbird 91.6.0, but the issue reported by Savior13 has not been fixed. Double-clicking on a cab file does not respond at all.
> Please reopen this bug.

(no need to respond to this learning point)

A learning point ... please see the fields in the `Tracking` section at the top of this bug report:
* Status = `FIXED` indicates the problem is fixed in the **development (daily) branch**.  `Target Milestone` = 98 Branch indicates the first version that is fixed. This happened in comment 8. Note, `FIXED` does not mean this is fixed in the main public release.  
* `thunderbirdnn` tracking flag on the right indicates any **beta branch** that might have also gotten the patch. This happened in comment 10.
* `thunderbird_esr91` tracking flag on the right indicates the status of the **version 91 branch**.  It is currently `affected`, meaning the patch has not yet reached that branch.  

In short, it takes time for a "FIXED" patch to get into a release.

Back to Bug 1747360 Comment 23