Thunderbird 60.2.1 updates are DISABLED

Óvári ovari123 at zoho.com
Thu Oct 4 23:43:39 UTC 2018


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.

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.*".

What do you think?

Óvári

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" 
> <https://bugzilla.mozilla.org/post_bug.cgi?flag_type-931=X&keywords=&blocked=&bug_ignored=0&qa_contact=&bug_severity=blocker&flag_type-737=X&flag_type-799=X&flag_type-768=X&attach_text=&description=&flag_type-800=X&cf_fx_iteration=---&cf_tracking_thunderbird_64=---&flag_type-203=X&flag_type-37=X&contenttypeentry=&cf_fx_points=---&data_base64=&defined_groups=1&form_name=enter_bug&bug_file_loc=http%3A%2F%2F&cf_status_thunderbird_62=---&cf_user_story=&cf_tracking_thunderbird_60=---&status_whiteboard=&version=60&cf_status_thunderbird_64=---&contenttypemethod=list&contenttypeselection=text%2Fplain&cf_tracking_thunderbird_61=---&filename=&dependson=&needinfo_done=1&priority=--&cf_status_thunderbird_esr60=---&flag_type-803=X&flag_type-915=X&flag_type-787=X&flag_type-4=X&cc=ryan%40thunderbird.net&cc=sancus%40pobox.com&cc=unicorn.consulting%40gmail.com&cc=jsabash%40bellatlantic.net&cc=mkmelin%2Bmozilla%40iki.fi&cf_tracking_thunderbird_esr60=---&assigned_to=nobody%40mozilla.org&see_also=&short_desc=Add-on%20install%2Fupdate%20failure%20-%20%22%3Caddon%3E%20could%20not%20be%20installed%20because%20it%20is%20not%20compatible%20with%20Thunderbird%2060.2.1%22&cf_status_thunderbird_63=---&data=&cf_tracking_thunderbird_63=---&alias=&op_sys=All&flag_type-767=X&cf_crash_signature=&rep_platform=Unspecified&flag_type-607=X&token=9HC6CHBuRjf4HPRMOEPqe9&flag_type-5=X&bug_status=NEW&cf_tracking_thunderbird_62=---&cf_status_thunderbird_61=---&flag_type-721=X&component=Add-Ons%3A%20General&comment=This%20is%20effectively%20blocking%20release%2060.2.1.%20%20So%20we%20need%20to%20quickly%20determine%20the%20cause%20and%20fix%20it.%0D%0A%0D%0ASome%20support%20reports%20today%20of%20incompatible%20addons%20when%20updating%20from%20version%2060.0%20to%2060.2.1.%20%20Two%20examples%2C%20where%20both%20add-ons%20have%20MaxVersion%2060.0%20and%20in%20all%20other%20respects%20the%20.rdf%20configuration%20of%20these%20two%20addons%20is%20similar%3A%0D%0A%2A%20https%3A%2F%2Faddons.thunderbird.net%2Fen-US%2Fthunderbird%2Faddon%2Ftheme-font-size-changer-fixed%2F%20failed%20to%20install%20per%20https%3A%2F%2Fsupport.mozilla.org%2Fen-US%2Fquestions%2F1235630%23answer-116%0D%0A%2A%20https%3A%2F%2Faddons.thunderbird.net%2Fen-US%2Fthunderbird%2Faddon%2Funread-badge%2F%20failed%20to%20install%20per%20https%3A%2F%2Fsupport.mozilla.org%2Fen-US%2Fquestions%2F1236088%23answer-1161116%0D%0A%0D%0AHowever%2C%20the%20results%20for%20other%20users%20are%20mixed.%20Myself%20and%20at%20least%20one%20other%20person%20successfully%20installed%20these%20add-ons%20in%2060.2.1.%20On%20the%20other%20hand%2C%20in%20a%20totally%20NEW%20profile%2C%20a%29%20unread-badge%20consistently%20fails%20to%20install%20b%29%20heme-font-size-changer-fixed%20consistently%20installs.%20If%20I%20bump%20unread-badge%20maxversion%20to%2060.%2A%20then%20it%20installs.%0D%0A%0D%0ANo%20attempt%20has%20been%20made%20to%20determine%20how%20badly%20users%20are%20affected.%0D%0A%0D%0APerhaps%20we%20are%20seeing%20bug%20505167%20-%20maxversion%20x.y%20should%20be%20interpreted%20as%20x.y.%2A%20not%20x.y.0.%20%20But%20I%20don%27t%20understand%20why%20the%20add-on%20with%20MaxVersion%2060.0%20succeeds%20in%20installing%20in%2060.2.1.%0D%0A%0D%0AIs%20the%20solution%20a%20fix%20in%20add-ons%20manager%3F%20%20%0D%0AOr%20must%20we%20bump%20maxversion%20for%20version%2060%20compatible%20addons%20to%20be%2060.%2A%20%3F&product=Thunderbird&target_milestone=---&flag_type-929=X&flag_type-933=X&cf_status_thunderbird_60=---&flag_type-791=X>
>
> 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
>> https://mail.mozilla.org/listinfo/tb-planning
>
>
>
> _______________________________________________
> tb-planning mailing list
> tb-planning at mozilla.org
> https://mail.mozilla.org/listinfo/tb-planning
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.mozilla.org/pipermail/tb-planning/attachments/20181005/e87a1946/attachment-0001.html>


More information about the tb-planning mailing list