Why don't we just turn off MOZ_BLOCK_PROFILE_DOWNGRADE?

Nomis101 🐝 Nomis101 at web.de
Thu Jul 4 07:30:21 UTC 2019


Am 04.07.19 um 02:59 schrieb Ben Bucksch:
>
> Mark Banner wrote on 02.07.19 13:31:
>> was once basically "downgrades are nice but not really supported" is
>> now a definite "downgrades are not supported"
>
>
> FWIW, downgrades have always works. I've moved between versions of
> Firefox since decades. I've never ever had any notable corruption
> (modulo very very rare bugs like bug 1530660 which were then fixed).
>
> This is definitely new and very inconvenient for development, of which
> testing (also with real data and old time-battered profiles) is an
> integral part.
>
> Ben
>
> _______________________________________________
> tb-planning mailing list
> tb-planning at mozilla.org
> https://mail.mozilla.org/listinfo/tb-planning
>

I see this exacly the same. I never found any problem while downgrading Thunderbird. The first real issue after downgrading I ever
had was MOZ_BLOCK_PROFILE_DOWNGRADE. For a test I downgraded from TB 68 to 60 and even to 45.8, but could't see anything broken.
For beta testing and regression finding you often have to downgrade, which is now very frustrating. And it also happens very often
that a normal user is downgrading. I'm in a Mac user forum and a lot of support questions there are regarding downgrading to an older version
of any given software (because of dislike the new UI, missing features in the new version or whataver reason). For my oppinionen
MOZ_BLOCK_PROFILE_DOWNGRADE will give a lot of support questions an a lot of angry users. At least we should give the users a possibility
to switch MOZ_BLOCK_PROFILE_DOWNGRADE off by there own risk and defenitely warn the user before launching the new version, that he
would not be able to downgrade afterwards.


More information about the tb-planning mailing list