Now I have Firefox 71.0 working ( https://forums.opensuse.org/showthread.php/538393-Firefox-71-0-crashes-on-launch ) it appears to have a bug relating to saving data into local storage:
https://bugzilla.mozilla.org/show_bug.cgi?id=1601365
I noticed it with Brief (an RSS feed reader), but it seems to be affecting several extensions…
Looks like a fix is on the way…
https://build.opensuse.org/package/rdiff/mozilla/firefox71?linkrev=base&rev=11
As a general afterthought… :\
I can’t help but wonder if in the future Firefox is going to be slightly less stable with Mozilla’s decision to move to a rapid release cycle.
https://hacks.mozilla.org/2019/09/moving-firefox-to-a-faster-4-week-release-cycle/
As is usually the case, likely “It Depends…”
It’s do-able but relies greatly on the expertise and effort by Project Management, and the steps outlined in the article sound reasonable.
No doubt, minimizing issues related to the accelerated cycle will require a tremendous effort focused on prevention, but done carefully and with care is probably possible.
I’d also expect that there will be differences between types of changes, primarily break/fix (including imperative security patches) and features.
Break/fix may or may not be affected if they are already give the highest priority and effort.
Features development may require modifications to accelerate their development, divide into smaller “sprints” (using one of those Agile terms) or risk extending to the next release cycle 4 weeks later. Or, maybe there will be internal attitudes of “It’ll happen when it happens, regardless of release deadlines”
In any case,
The world of technology is on an ever-accelerating curve so to remain competitive and relevant everyone must always be looking at ways to accelerate what they do. 4 weeks may even be considered “slow” by some Agile schools of thought which instead eliminate deadlines altogether in favor of weekly or better incremental releases which effectively puts parts of a project forever in “alpha or beta testing” mode.
TSU
Indeed, time will tell no doubt.
Fixed in Firefox => 71.0-4.1