I keep looking at that Twitter exchange, and it’s not clear at all. First they say “56 is unsupported and we don’t anticipate providing a patch”. If not a patch, then something else, or nothing at all? Then, after protest “spoke too soon, discussing patching ESR 52” – huh? He asked about non- ESR 56, how does ESR 52 figure into that!? So again, he specifically asks what about non-ESR 56.0.2, and gets another cryptic reply: “Plan is to push an update to update versions older than 64…”. So, what is an “update version”, and how much older than 64?
Why, when clearly the plea is for a fix for all non-ESR versions of any age, can’t they just address that directly?
This was a massive failure of coding and certificate management in the first place, but they’re making it worse by not having someone out front that can provide clear and complete information, rather than developers tweeting half-baked, poorly phrased insider shorthand.
I shouldn’t have to try to learn the subtleties of the entire release history and all its branches, then read between the lines of random Mozilla-issued snippets, just to get some reassurance that a fix for my older install is coming soon, so that I know what steps to take. It’s like The Riddler is doing their damage control:
Hans Vader-Musterman: will this patch work for firefox 56.0.2 (64bit) too?
Mozilla Add-ons: No, and as Firefox 56 is currently unsupported we do not anticipate providing a patch for it.
Hans Vader-Musterman: if i DOWNGRADE to any firefox version higher than 56.0.2, i will LOOSE all-in-one gestures, i’ll loose classic theme restorer, i’ll loose status-4-evar and so on, that’s %%%ing UNACCEPTABLE!!!
Mozilla Add-ons: Sorry, I spoke too soon: there is currently discussion about patching ESR 52, I’ll provide an update as that continues.
Hans Vader-Musterman: as firefox 56.0.2 is not esr, will this update work for this version too?
Mozilla Add-ons: The current plan is to push an update to update versions older than 64, but the current ETA is sometime Monday.