The main part of the new schedule is that version releases are date driven now, vs the previous feature driven releases. If a feature is ready for release, it is included in a new release; if a feature needs more time to "percolate", it is postponed until it is ready - no more postponing a release date because a few features need more development time. Fewer new features and fewer changes per version release than in the past, with more frequent releases.
A page like this should appear for each new version after it is installed. It's just a matter of reading about "What's New in Firefox" to see what changes the new version has. No need for a developer to do anything if their extension was created properly to begin with and meet the current standard for security. Plus with a specific 6 week Beta testing period developers are assured that they won't need to re-do any fixes they may need to make to their add-ons due to last minute changes in the Beta version, as did happen in the past because of new features that were changed at the "last minute" to try to make the release date.
The Nightly, Aurora, and Firefox Beta testers do much of the "compatibility testing" for add-ons which are hosted at AMO, so the developers have less work to do if their add-on doesn't need any fixes and the "testers" can report specific problems to make it easier to know what a problem is and maybe help the developer work on a "fix". As far as add-ons that are self-hosted, that's a problem for those add-on developers to figure out for thenselves.
They need to re-think self hosting vs using AMO for distributing their add-ons, or they need to find a different line of endeavor if they can't keep up with the rapid release schedule. IMO, Norton with their Firefox extensions like secure password storage and anti-phishing for Firefox 3. I hate Norton for all the problems their software caused for me over the last 25 years, but I do have to commend them for "stepping up their game" with the new rapid release schedule and meeting the needs of their Firefox using customers by providing "just in time" updates.
But they still need to work on their method of delivering those updates in a more automatic method, other than users needing to download and install a "patch" or manually run a Live Update. That all said, probably with Firefox 10 early next year, there will be a major change with Firefox's handling of perceived add-on compatibility.
Currently the add-on has to meet or exceed the Firefox version number which is coded inside the add-on or on the AMO server for the particular add-on, or the add-on is automatically disabled as the new version of Firefox is installed.
The new way of handling it will assume that all add-ons are compatible - period. Not to sound overly negative, but if or when a user has a problem due to incompatible code in one or more add-ons, it will fall on the user's shoulders to figure out what is causing their problem.
I have seen too damn many poorly coded add-ons over that last 9 years of using this browser, which caused all sorts of problems for me, to think otherwise. I am surprised at the version numbers of firefox though. Hell, Google Chrome's version numbering system almost needs a calculator to decipher and Opera isn't much better when you consider the "build number" along with a somewhat logical version number, Mozilla is just joining the nonsensical pack. Some modifications to the version numbering system to give it more meaning have been discussed preliminarily, but nothing firm has been decided yet.
And the last three Firefox updates are living proof in this regard. Firefox 77 rollout suspended. Firefox 78 rollout suspended. Firefox 76 was the first major update that caused problems, including crashes on Windows 7. The Amazon Assistant and other add-ons also worked incorrectly after this update, so Mozilla decided to pause the rollout of the new browser version until a fix was developed. Firefox This thread was archived. Please ask a new question if you need help.
Is there a way to keep FF working in such situation? I usually have 3 FF profiles running, about tabs each and when it suddenly does this - I can restart them all but when it is suitable for me. The only solution I can see so far is disabling updates via group policies which is not well documented, where do i put this policies. I suggest: do not accept the download until you are ready for the restarts.
I suspect the unwanted pages are related to running multiple profiles at the same time. My main profile where I accept downloading the update understands that I want to wait, and I've never been forced to restart.
However, if I start Firefox in another profile during that time and the update actually installs right then, I think it's not safe to keep working in my main profile without doing the restart since the program files running in memory won't match what is on disk.
If I can't get help here, I'll probably just go under my desk and cry while eating glue and rocking back and forth until they either fire me or have me committed. I do not have old versions of Firefox on this machine so I can not check or confirm what is happening, but normally the problem is that people check the version using the menu. If you do that then Firefox will report the current version AND check for and initiate an update.
If you set Firefox to not update then as long as you do not do that it should not update. If you wish to check the version without updating Firefox key about:support in to the address bar so that you obtain the troubleshooting information. If Firefox is updating when it should not then please try to explain what happens and if others can reproduce the issue a bug should be filed. It updated again, so I've written a script that runs a loop every 5 minutes or so to delete the updates folder and create a log with the timestamp of when it does delete the folder.
So far, since re-installing this morning it has deleted the updates folder twice, and that's after I went in and deleted it right after re-installing. So much for "never check for updates. WriteLine now 'close logfile outfile. Close end if 'sleep for specified number of minutes wscript. ESR was first developed to meet the needs of large organizations that wanted Firefox to change much more slowly, but anyone can use it.
The main difference is that it gets security updates only, no feature changes for about a year at a time. FYI, the "b" in the version number indicates a beta test release. The final release version of Firefox While this is a nice workaround, it is not a solution. I told it not to update, it updated anyway. I refuse to accept anything less than having the application work as it displays it should.
Nobody should have to accept that a program asks a user what to do, and then goes and does whatever the developer wants instead. If they're going to force updates, they shouldn't give the illusion that you can opt out of them.
I turned off my script and did some testing, and it looks like you were right. As soon as I closed my browser and re-opened i was on v Turns out that "Never" doesn't really mean never and they think that when I want to look at my version number the easy way that I mean I want to update, regardless of what my preferences say. That's dumb.
0コメント