This is a very specific and commonly-asked question, so we really should have an article specifically devoted to the problems after updating to 5.0. Updating Common questions after upgrading from Firefox 3.6 is good and will be useful for future updates, but a focused article on breakage caused by the new versioning scheme could be much more targeted than that, linking to the more general article for other update issues.
Since the questions asked about this issue vary but nearly all mention the version change to 5.0, the article needs to include the version number. This could be a different article name for each problem (eg. "A website doesn't work after upgrading to Firefox 5", "Add-ons missing in Firefox 5") or a single generic article (eg. "Update to Firefox 5" or "Questions after updating to Firefox 5")
Since we're telling people that Firefox 4.0 is no longer an option, and no easy fixes exist other than going back to 3.6 or using a competing browser, I do think a brief explanation of the version scheme change is justified. If we don't mention this in the article, users won't understand why going back to 4.0 is impossible.
This is a very specific and commonly-asked question, so we really should have an article specifically devoted to the problems after updating to 5.0. Updating [[Common questions after updating Firefox]] is good and will be useful for future updates, but a focused article on breakage caused by the new versioning scheme could be much more targeted than that, linking to the more general article for other update issues.
Since the questions asked about this issue vary but nearly all mention the version change to 5.0, the article needs to include the version number. This could be a different article name for each problem (eg. "A website doesn't work after upgrading to Firefox 5", "Add-ons missing in Firefox 5") or a single generic article (eg. "Update to Firefox 5" or "Questions after updating to Firefox 5")
Since we're telling people that Firefox 4.0 is no longer an option, and no easy fixes exist other than going back to 3.6 or using a competing browser, I do think a brief explanation of the version scheme change is justified. If we don't mention this in the article, users won't understand why going back to 4.0 is impossible.