microsoft / microsoft/winget-pkgs
[Package Issue]: Mozilla.Thunderbird needs to be split up into ESR and normal
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 11.1k
- Forks
- 9.7k
- Avg merge
- 1h 32m
- Merged PRs (30d)
- 376
Description
Please confirm these before moving forward
- I have searched for my issue and not found a work-in-progress/duplicate/resolved issue.
- I have not been informed if the issue is resolved in a preview version of the winget client.
Category of the issue
Installation issue.
Brief description of your issue
With the recent release of Thunderbird 128.8.0 and 136.0.0, the project now follows Firefox's development schedule of releasing an ESR version (128.x) and a normal release (136 ff).
The current Mozilla.Thunderbird package updates a current 128.8.0 ESR installation to 136, which is somewhat unexpected and probably unintended.
May I suggest creating two separate Mozilla.Thunderbird.ESR and Mozilla.Thunderbird branch es for Winget, as it is already implemented for Firefox?
Steps to reproduce
see current behavior
Actual behavior
A current Thunderbird 128.8.0 ESR installation will be updated to 136.0.
Expected behavior
Thunderbird ESR installations should stay on ESR, thus updating to 128.x.
Thunderbird 136 ff should be updated in a seperate Winget-package and only if that release channel is in use by the local installation.
Environment
-+-
Screenshots and Logs
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing how Firefox is split into ESR and normal packages, then read the issue's comment thread for any decisions or constraints. Done means Thunderbird ESR installations remain on the ESR release line while normal-release installations update through a separate package.
Written by the indexing model from the issue text.
Assessment
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100