Traditionally add-ons have been set to be compatible by default, i.e. not needed an action from the add-on author to continue to function when Thunderbird does a major version update. Many times the add-ons haven't really worked and caused strange bug reports. For Thunderbird 59 it doesn't make sense to keep the compatible by default scheme. If the add-on hasn't been updated, it very likely will cause problems - and that's not in anybody's best interest. So let's change the scheme to not-compatible by default. Comments?  -Magnus

On 07-Dec-17 7:32 PM, Magnus Melin wrote: > Traditionally add-ons have been set to be compatible by default, i.e. > not needed an action from the add-on author to continue to function > when Thunderbird does a major version update. Many times the add-ons > haven't really worked and caused strange bug reports. For Thunderbird > 59 it doesn't make sense to keep the compatible by default scheme. If > the add-on hasn't been updated, it very likely will cause problems - > and that's not in anybody's best interest. > > So let's change the scheme to not-compatible by default. Comments? > >  -Magnus > I would support that, I would be happier if we provided a back out for the update if the user wants it following the notification that compatibility is unlikely without an update so these ones have been marked incompatible and disabled. Support is full up following updates of users that want to "roll back" the latest update.  This is normally due to problems with application firewalls and security software, or add-ons.  But I think we have to bite the bullet and actually offer a one click let me out of here option.  Regardless of the reason,  or how silly it is we are in the business of offering products to users and they have expectations.  One of them is that they can revert to yesterday when they were comfortable in their ignorance. Perhaps opt them out of automatic updates for a week or two.  Then their anti virus will have caught up and they will be happy campers that we fixed the bad release. Matt

On 07.12.17 10:02, Magnus Melin wrote: > Traditionally add-ons have been set to be compatible by default, i.e. > not needed an action from the add-on author to continue to function when > Thunderbird does a major version update. Many times the add-ons haven't > really worked and caused strange bug reports. For Thunderbird 59 it > doesn't make sense to keep the compatible by default scheme. If the > add-on hasn't been updated, it very likely will cause problems - and > that's not in anybody's best interest. > > So let's change the scheme to not-compatible by default. Comments? I think that's a required step. It's better to disable incompatible add-ons than to have add-ons that are broken and possibly disturb functionality in Thunderbird (and other add-ons). -Patrick

Going to do it in https://bugzilla.mozilla.org/show_bug.cgi?id=1451097  -Magnus On 07-12-2017 11:02, Magnus Melin wrote: > Traditionally add-ons have been set to be compatible by default, i.e. > not needed an action from the add-on author to continue to function > when Thunderbird does a major version update. Many times the add-ons > haven't really worked and caused strange bug reports. For Thunderbird > 59 it doesn't make sense to keep the compatible by default scheme. If > the add-on hasn't been updated, it very likely will cause problems - > and that's not in anybody's best interest. > > So let's change the scheme to not-compatible by default. Comments? > >  -Magnus > > > _______________________________________________ > Maildev mailing list > Maildev@lists.thunderbird.net > http://lists.thunderbird.net/mailman/listinfo/maildev_lists.thunderbird.net >

Does this mean add-on authors physically need to change their add-ons (e.g. update maxVersion in install.rdf) or only mark it compatible on amo? Onno > On 3 Apr 2018, at 21:45, Magnus Melin <mkmelin+mozilla@iki.fi> wrote: > > Going to do it in https://bugzilla.mozilla.org/show_bug.cgi?id=1451097 > > -Magnus > >> On 07-12-2017 11:02, Magnus Melin wrote: >> Traditionally add-ons have been set to be compatible by default, i.e. not needed an action from the add-on author to continue to function when Thunderbird does a major version update. Many times the add-ons haven't really worked and caused strange bug reports. For Thunderbird 59 it doesn't make sense to keep the compatible by default scheme. If the add-on hasn't been updated, it very likely will cause problems - and that's not in anybody's best interest. >> >> So let's change the scheme to not-compatible by default. Comments? >> >> -Magnus >> >> >> _______________________________________________ >> Maildev mailing list >> Maildev@lists.thunderbird.net >> http://lists.thunderbird.net/mailman/listinfo/maildev_lists.thunderbird.net > > _______________________________________________ > Maildev mailing list > Maildev@lists.thunderbird.net > http://lists.thunderbird.net/mailman/listinfo/maildev_lists.thunderbird.net

On 03/04/2018 23:13, Onno Ekker wrote: > only mark it compatible on amo? I re-uploaded three add-ons to AMO last night since I couldn't find a "mark as compatible" button. Jörg.

If the add-on is on AMO you just need to mark it compatible. To do that, go to AMO to the add-ons page, then Manage Status & Versions, then under Listed versions, click the link for a version and set its compatible versions.  -Magnus On 04-04-2018 00:13, Onno Ekker wrote: > Does this mean add-on authors physically need to change their add-ons (e.g. update maxVersion in install.rdf) or only mark it compatible on amo? > > Onno > >> On 3 Apr 2018, at 21:45, Magnus Melin <mkmelin+mozilla@iki.fi> wrote: >> >> Going to do it in https://bugzilla.mozilla.org/show_bug.cgi?id=1451097 >> >> -Magnus >> >>> On 07-12-2017 11:02, Magnus Melin wrote: >>> Traditionally add-ons have been set to be compatible by default, i.e. not needed an action from the add-on author to continue to function when Thunderbird does a major version update. Many times the add-ons haven't really worked and caused strange bug reports. For Thunderbird 59 it doesn't make sense to keep the compatible by default scheme. If the add-on hasn't been updated, it very likely will cause problems - and that's not in anybody's best interest. >>> >>> So let's change the scheme to not-compatible by default. Comments? >>> >>> -Magnus >>> >>> >>> _______________________________________________ >>> Maildev mailing list >>> Maildev@lists.thunderbird.net >>> http://lists.thunderbird.net/mailman/listinfo/maildev_lists.thunderbird.net >> _______________________________________________ >> Maildev mailing list >> Maildev@lists.thunderbird.net >> http://lists.thunderbird.net/mailman/listinfo/maildev_lists.thunderbird.net >> >> _______________________________________________ >> Maildev mailing list >> Maildev@lists.thunderbird.net >> http://lists.thunderbird.net/mailman/listinfo/maildev_lists.thunderbird.net

So that is only available to *author *of the addon ? On 4/5/2018 3:34 PM, Magnus Melin wrote: > > If the add-on is on AMO you just need to mark it compatible. > > To do that, go to AMO to the add-ons page, then Manage Status & > Versions, then under Listed versions, click the link for a version and > set its compatible versions. > >  -Magnus > > On 04-04-2018 00:13, Onno Ekker wrote: >> Does this mean add-on authors physically need to change their add-ons (e.g. update maxVersion in install.rdf) or only mark it compatible on amo? >> >> Onno >> >>> On 3 Apr 2018, at 21:45, Magnus Melin<mkmelin+mozilla@iki.fi> wrote: >>> >>> Going to do it inhttps://bugzilla.mozilla.org/show_bug.cgi?id=1451097 >>> >>> -Magnus >>> >>>> On 07-12-2017 11:02, Magnus Melin wrote: >>>> Traditionally add-ons have been set to be compatible by default, i.e. not needed an action from the add-on author to continue to function when Thunderbird does a major version update. Many times the add-ons haven't really worked and caused strange bug reports. For Thunderbird 59 it doesn't make sense to keep the compatible by default scheme. If the add-on hasn't been updated, it very likely will cause problems - and that's not in anybody's best interest. >>>> >>>> So let's change the scheme to not-compatible by default. Comments? >>>> >>>> -Magnus >>>> >>>> >>>> _______________________________________________ >>>> Maildev mailing list >>>> Maildev@lists.thunderbird.net >>>> http://lists.thunderbird.net/mailman/listinfo/maildev_lists.thunderbird.net >>> _______________________________________________ >>> Maildev mailing list >>> Maildev@lists.thunderbird.net >>> http://lists.thunderbird.net/mailman/listinfo/maildev_lists.thunderbird.net >>> >>> _______________________________________________ >>> Maildev mailing list >>> Maildev@lists.thunderbird.net >>> http://lists.thunderbird.net/mailman/listinfo/maildev_lists.thunderbird.net > > _______________________________________________ > Maildev mailing list > Maildev@lists.thunderbird.net > http://lists.thunderbird.net/mailman/listinfo/maildev_lists.thunderbird.net

Yes, this is the downside to doing it at all, unmaintained addons that still work would show up as not compatible. The user can change the install.rdf, but that is cumbersome. It also may mean we would need to reinstate the compatibility bumps on each release, which was a fair amount of work. Philipp > On 6. Apr 2018, at 5:44 PM, Wayne Mery <vseerror@lehigh.edu> wrote: > > So that is only available to author of the addon ? > > >> On 4/5/2018 3:34 PM, Magnus Melin wrote: >> If the add-on is on AMO you just need to mark it compatible. >> To do that, go to AMO to the add-ons page, then Manage Status & Versions, then under Listed versions, click the link for a version and set its compatible versions. >> >> -Magnus >>> On 04-04-2018 00:13, Onno Ekker wrote: >>> Does this mean add-on authors physically need to change their add-ons (e.g. update maxVersion in install.rdf) or only mark it compatible on amo? >>> >>> Onno >>> >>>>> On 3 Apr 2018, at 21:45, Magnus Melin <mkmelin+mozilla@iki.fi> wrote: >>>>> >>>>> Going to do it in https://bugzilla.mozilla.org/show_bug.cgi?id=1451097 >>>>> >>>>> -Magnus >>>>> >>>>> On 07-12-2017 11:02, Magnus Melin wrote: >>>>> Traditionally add-ons have been set to be compatible by default, i.e. not needed an action from the add-on author to continue to function when Thunderbird does a major version update. Many times the add-ons haven't really worked and caused strange bug reports. For Thunderbird 59 it doesn't make sense to keep the compatible by default scheme. If the add-on hasn't been updated, it very likely will cause problems - and that's not in anybody's best interest. >>>>> >>>>> So let's change the scheme to not-compatible by default. Comments? >>>>> >>>>> -Magnus >>>>> >>>>> >>>>> _______________________________________________ >>>>> Maildev mailing list >>>>> Maildev@lists.thunderbird.net >>>>> http://lists.thunderbird.net/mailman/listinfo/maildev_lists.thunderbird.net >>>> _______________________________________________ >>>> Maildev mailing list >>>> Maildev@lists.thunderbird.net >>>> http://lists.thunderbird.net/mailman/listinfo/maildev_lists.thunderbird.net >>>> >>>> >>>> _______________________________________________ >>>> Maildev mailing list >>>> Maildev@lists.thunderbird.net >>>> http://lists.thunderbird.net/mailman/listinfo/maildev_lists.thunderbird.net >> >> >> _______________________________________________ >> Maildev mailing list >> Maildev@lists.thunderbird.net >> http://lists.thunderbird.net/mailman/listinfo/maildev_lists.thunderbird.net > > _______________________________________________ > Maildev mailing list > Maildev@lists.thunderbird.net > http://lists.thunderbird.net/mailman/listinfo/maildev_lists.thunderbird.net

If the user knows the add-ons are ok, he can always set the extensions.strictCompatibility pref to false, and things would work like before. To the extent the add-on is not broken. No need to change the install.rdf  -Magnus On 06-04-2018 20:33, Philipp Kewisch wrote: > Yes, this is the downside to doing it at all, unmaintained addons that > still work would show up as not compatible. The user can change the > install.rdf, but that is cumbersome. > > It also may mean we would need to reinstate the compatibility bumps on > each release, which was a fair amount of work. > > Philipp > > On 6. Apr 2018, at 5:44 PM, Wayne Mery <vseerror@lehigh.edu > <mailto:vseerror@lehigh.edu>> wrote: > >> So that is only available to *author *of the addon ? >> >> >> On 4/5/2018 3:34 PM, Magnus Melin wrote: >>> >>> If the add-on is on AMO you just need to mark it compatible. >>> >>> To do that, go to AMO to the add-ons page, then Manage Status & >>> Versions, then under Listed versions, click the link for a version >>> and set its compatible versions. >>> >>>  -Magnus >>> >>> On 04-04-2018 00:13, Onno Ekker wrote: >>>> Does this mean add-on authors physically need to change their add-ons (e.g. update maxVersion in install.rdf) or only mark it compatible on amo? >>>> >>>> Onno >>>> >>>>> On 3 Apr 2018, at 21:45, Magnus Melin<mkmelin+mozilla@iki.fi> wrote: >>>>> >>>>> Going to do it inhttps://bugzilla.mozilla.org/show_bug.cgi?id=1451097 >>>>> >>>>> -Magnus >>>>> >>>>>> On 07-12-2017 11:02, Magnus Melin wrote: >>>>>> Traditionally add-ons have been set to be compatible by default, i.e. not needed an action from the add-on author to continue to function when Thunderbird does a major version update. Many times the add-ons haven't really worked and caused strange bug reports. For Thunderbird 59 it doesn't make sense to keep the compatible by default scheme. If the add-on hasn't been updated, it very likely will cause problems - and that's not in anybody's best interest. >>>>>> >>>>>> So let's change the scheme to not-compatible by default. Comments? >>>>>> >>>>>> -Magnus >>>>>> >>>>>> >>>>>> _______________________________________________ >>>>>> Maildev mailing list >>>>>> Maildev@lists.thunderbird.net >>>>>> http://lists.thunderbird.net/mailman/listinfo/maildev_lists.thunderbird.net >>>>> _______________________________________________ >>>>> Maildev mailing list >>>>> Maildev@lists.thunderbird.net >>>>> http://lists.thunderbird.net/mailman/listinfo/maildev_lists.thunderbird.net >>>>> >>>>> _______________________________________________ >>>>> Maildev mailing list >>>>> Maildev@lists.thunderbird.net >>>>> http://lists.thunderbird.net/mailman/listinfo/maildev_lists.thunderbird.net >>> >>> _______________________________________________ >>> Maildev mailing list >>> Maildev@lists.thunderbird.net >>> http://lists.thunderbird.net/mailman/listinfo/maildev_lists.thunderbird.net >> >> >> _______________________________________________ >> Maildev mailing list >> Maildev@lists.thunderbird.net <mailto:Maildev@lists.thunderbird.net> >> http://lists.thunderbird.net/mailman/listinfo/maildev_lists.thunderbird.net