Bugzilla

Greetings, as you know, we're running a fork of Thunderbird and therefore we're following your release activities. Our project benefits greatly from the good work you're doing and therefore we're more than happy to give back to Thunderbird.

Let's look at the basics of release management. TB is released in three versions from three(six) separate HG repositories:
Daily (mozilla/comm-central), Beta (mozilla/comm-beta) and ESR, now at ESR 102 (mozilla/comm-esr102).

In general, if a bug is found in ESR (102) and fixed in Daily (currently at 104), the patch with the fix needs to be backported, also called "uplifted", to ESR. Before that happens, the patch is backported to Beta (currently at 103). Therefore in comment #8 we said that you need to request beta approval, either before or together with ESR approval. ESR approval is generally granted later.

The case of this bug is a little more complicated. The bug was reported for Beta (103) and therefore a beta request must be made.

Let's look at whether ESR 102 is affected. If you try it out, you will see that it is **not** affected. What happened is this: The Firefox team fixed in bug in FF 103, bug 1766030, something with a download link inside a PDF. While fixing the bug in FF 103, they changed an API (adding another parameter) and that API change broke TB 103 so beta users complained. The Firefox team also marked FF 102 ESR as affected by the original download link bug. If you look at bug 1766030, they haven't backported the fix to FF 102 ESR yet, so no API change has happened in the Mozilla 102 ESR code base. Therefore TB 102 ESR is **not yet** affected, but it will be affected as soon as the Firefox team also make the change in the Mozilla 102 ESR code base.

A prudent release manager would follow bug 1766030 and as soon as that is fixed in ESR 102, also apply the corresponding TB fix to comm-esr102.

Hopefully this is clear now, don't hesitate so ask if there are further questions.

Greetings, as you know, we're running a fork of Thunderbird and therefore we're following your release activities. Our project benefits greatly from the good work you're doing and therefore we're more than happy to give back to Thunderbird.

Let's look at the basics of release management. TB is released in three versions from three(six) separate HG repositories:
Daily (mozilla/comm-central), Beta (mozilla/comm-beta) and ESR, now at ESR 102 (mozilla/comm-esr102).

In general, if a bug is found in ESR (102) and fixed in Daily (currently at 104), the patch with the fix needs to be backported, also called "uplifted", to ESR. Before that happens, the patch is backported to Beta (currently at 103). Therefore in comment #8 we said that you need to request beta approval, either before or together with ESR approval. ESR approval is generally granted later.

The case of this bug is a little more complicated. The bug was reported for Beta (103) and therefore a beta request must be made.

Let's look at whether ESR 102 is affected. If you try it out, you will see that it is **not** affected. What happened is this: The Firefox team fixed in bug in FF 103, bug 1766030, something with a download link inside a PDF. While fixing the bug in FF 103, they changed an API (adding another parameter) and that API change broke TB 103 so beta users complained. The Firefox team also marked FF 102 ESR as affected by the original download link bug. If you look at bug 1766030, they haven't backported the fix to FF 102 ESR yet, so no API change has happened in the Mozilla 102 ESR code base. Therefore TB 102 ESR is **not yet** affected, but it will be affected as soon as the Firefox team also make the change in the Mozilla 102 ESR code base.

A prudent release manager would follow bug 1766030 and as soon as that is fixed in ESR 102, also apply the corresponding TB fix to comm-esr102.

Hopefully this is clear now, don't hesitate to ask if there are further questions.