On Fri Apr 06 2018 14:35:16 GMT-0400 (Eastern Standard Time), Magnus Melin <mkmelin+mozilla@iki.fi> wrote: > 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 But that is a global change (cold cause breakage if other Addons are really not compatible). Changing the RDF only affects that one Addon.

Also, it is something power users can do, but others may have difficulties with. Philipp > On 6. Apr 2018, at 9:00 PM, Tanstaafl <tanstaafl@libertytrek.org> wrote: > > On Fri Apr 06 2018 14:35:16 GMT-0400 (Eastern Standard Time), Magnus > Melin <mkmelin+mozilla@iki.fi> wrote: >> 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 > > But that is a global change (cold cause breakage if other Addons are > really not compatible). Changing the RDF only affects that one Addon. > > _______________________________________________ > Maildev mailing list > Maildev@lists.thunderbird.net > http://lists.thunderbird.net/mailman/listinfo/maildev_lists.thunderbird.net

It looks like the change was also applied to dictionaries (which I thought were not affected). Was this intended? -Patrick On 03.04.18 21:45, Magnus Melin 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

No, dictionaries should be fine, at least in general.  -Magnus On 08-04-2018 12:00, Patrick Brunschwig wrote: > It looks like the change was also applied to dictionaries (which I > thought were not affected). Was this intended? > > -Patrick > > > On 03.04.18 21:45, Magnus Melin 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

What do you mean by "in general"? https://discourse.mozilla.org/t/dictionaries-will-break-if-60-0-ships-soon/ suggests there may still be a problem. (Though details in the initial posting are lacking) On 4/8/2018 3:21 PM, Magnus Melin wrote: > No, dictionaries should be fine, at least in general. > >  -Magnus > > On 08-04-2018 12:00, Patrick Brunschwig wrote: >> It looks like the change was also applied to dictionaries (which I >> thought were not affected). Was this intended? >> >> -Patrick >> >> >> On 03.04.18 21:45, Magnus Melin 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 >

As I wrote, most dictionaries cannot be installed. The error message is always: "Dictionary X cannot be installed because it is not compatible with Thunderbird 60.0." I tried many dictionaries and I got that message for most of them. -Patrick On 24.04.18 17:36, Wayne Mery wrote: > What do you mean by "in general"? > > https://discourse.mozilla.org/t/dictionaries-will-break-if-60-0-ships-soon/ > suggests there may still be a problem. (Though details in the initial > posting are lacking) > > > On 4/8/2018 3:21 PM, Magnus Melin wrote: >> No, dictionaries should be fine, at least in general. >> >>  -Magnus >> >> On 08-04-2018 12:00, Patrick Brunschwig wrote: >>> It looks like the change was also applied to dictionaries (which I >>> thought were not affected). Was this intended? >>> >>> -Patrick >>> >>> >>> On 03.04.18 21:45, Magnus Melin 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

I'm not familiar with the internals of the dictionaries. The specify the min/max versions, but was there ever any breaking changes?  -Magnus On 24-04-2018 18:36, Wayne Mery wrote: > What do you mean by "in general"? > > https://discourse.mozilla.org/t/dictionaries-will-break-if-60-0-ships-soon/ > suggests there may still be a problem. (Though details in the initial > posting are lacking) > > > On 4/8/2018 3:21 PM, Magnus Melin wrote: >> No, dictionaries should be fine, at least in general. >> >>  -Magnus >> >> On 08-04-2018 12:00, Patrick Brunschwig wrote: >>> It looks like the change was also applied to dictionaries (which I >>> thought were not affected). Was this intended? >>> >>> -Patrick >>> >>> >>> On 03.04.18 21:45, Magnus Melin 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