chocolatey-community/chocolatey-packages

(Thunderbird) outdated

Closed this issue · 5 comments

Checklist

  • I have checked the moderation queue that no new version has been submitted (only visible when logged in), or the submitted package version has failed the automated checks.

Please navigate to the following link to view the moderation queue.

  • I have verified that the new version is a stable release.
  • I have looked to see if there are any Bug reports that prevents a new version being submitted and that no existing Outdated Reports have been created.
  • I have verified the new version has a Windows binary (EXE or MSI installer, Zip or other archive, etc).
  • I have verified that this is the correct repository, and the package is maintained by the chocolatey-community user.

New Software Version

128.1.0esr

Download location

https://download.mozilla.org/?product=thunderbird-128.1.0esr-SSL&os=win64&lang=en-US

Package Page

https://community.chocolatey.org/packages/thunderbird

I am not sure if the current package Thunderbird should be updated. Or a new one should be created for the ESR releases. As the auto update of Thunderbird now goes to the 128 esr version i think that may be the best thing to update it. But i dislike the idea a bit somehow.

@TheCakeIsNaOH @AdmiringWorm

Well, at least, MozTb should be updated to 115.14.0 which includes security fixes.

Releases — Thunderbird

If this Chocolatey package stays in v115 or moves to v128 can be discussed, maybe. But it actually should be up-to-date in its last path (i.e. 115, so 115.14.0), at least.

I personally would like the move to v128 because this is to become the new recent regular version. I wouldn't like to change Choco packages just to due the move 115 → 128. And besides, both are ESR (look at the links). Well, I am a bit confused by the naming recently…

Is this still relevant? If so, what is blocking it? Is there anything you can do to help move it forward?
This issue will be closed in 14 days if it continues to be inactive.

Please do not add a comment to circumvent automatic closure unless you plan to help move it forward.
Doing this may lead to the issue being closed immediately instead.

Issue has linked PR waiting for review, issue should remain open.

Thank you guys!