[FEAT] Consider a separate Thunderbird 153 ESR release channel
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 28/100
Research direction
Start by reviewing the project's version-tag convention and supported container-image release process. Determine whether an opt-in Thunderbird 153 ESR channel can be maintained without changing latest, including its security-update expectations; completion would require an agreed implementation or documented guidance if it is out of scope.
Written by the indexing model from the issue text.
Description
Is this a new feature request?
- I have searched the existing issues
Wanted change
Would you consider adding a separate, opt-in release channel for Thunderbird 153 ESR?
The new channel would be optional and would not be included in or change latest. I am not proposing a particular tag name or implementation; please use whichever version-tag convention fits the project.
Reason for change
Thunderbird 153 ESR is available upstream, and a separate channel could be useful for users who would like to evaluate it while remaining on a supported container image.
I understand that maintaining an additional release stream and its security updates may not fit the project's scope. If it is not feasible, no problem at all — I would appreciate any guidance on the supported way to run 153 ESR with the Selkies image.
Proposed code change
No response
- Dominant language
- Dockerfile
- Stars
- 11
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
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.
Similar issues
-
kind/bug needs-triage
Difficulty 1/5 Under an hour Newbie friendliness 72/100
matrixorigin/matrixone#29223 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
copse-dev/agent-pane#2953 ·
-
bug ci-failure high priority
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
vllm-project/vllm-omni#7972 · 1 comment ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
simonw/sqlite-utils#872 ·
-
bug good first issue
Difficulty 1/5 Under an hour Newbie friendliness 88/100
amponce/archive-movie-browser#166 ·