Thunderbird 60.2.1 updates are DISABLED
vseerror at lehigh.edu
Fri Oct 5 00:01:45 UTC 2018
On 10/4/2018 7:43 PM, Óvári wrote:
> Hi Wayne,
> When an add-on author asks for approval for their add-on, would be be
> worthwhile to check and ask the add-on author the following:
> 1. If max version is "60.0", do they want to change it to "60.*"?
> This will enable their add-on to support the complete ESR lifecycle
> and hopefully not have the current situation on the tb-planning list
> with add-ons not working as the user intends (even though it is
> working correctly). This can create a better user experience.
The majority of add-ons were "correct" so I don't know what happen with
the ones that didn't get wildcarded. In fact, I found examples that are
not wildcarded that predate the version 60 era . But yes, addon
reviewers will want to look for this in the future.
 not wildcarded
> 2. Can the add-ons on ATN be checked for verions "60.0" and authors of
> these add-on be contacted regarding changing their add-on maximum
> version to "60.*".
Sancus has already resolved the issue server side on ATN, and we will be
reenabling version 60.2.1 updates
> What do you think?
> On 5/10/18 5:14 am, Wayne Mery wrote:
>> filed Bug 1496535 - Add-on install/update failure - " could not be
>> installed because it is not compatible with Thunderbird 60.2.1"
>> Blocks 60.2.1 updates, so needs some eyes from the add-ons community.
>> On 10/4/2018 2:40 PM, Wayne Mery wrote:
>>> Thunderbird 60.2.1 updates have been enabled for about a day, for
>>> users already on version 60.0. But some add-on are not staying
>>> enabled when user updates from 60.0 to 60.2.1. Therefore, we have
>>> disabled background updates until we sort it out.
>>> Manual updates are enabled, but users do so at their own risk.
>>> tb-planning mailing list
>>> tb-planning at mozilla.org
>> tb-planning mailing list
>> tb-planning at mozilla.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the tb-planning