At least to some extent. I think Mozilla's trying to switch over to the fast release schedule because of serious version envy, as well as wanting to push out releases faster, but what I don't think they realized is the fundamental difference between how Google's Chrome engineers seem to view the version number.
A user downloads Chrome. That's it. They don't ever need to download updates, since once Chrome is launched, it patches the binary with newest updates automagically. It updates automagically in the background, only occasionally asking for a restart. The version number is buried in the "About Chrome" dialog box, and almost never referred to elsewhere. Extensions aren't tied to versioning, but rather, features. Chrome's fast release schedule works because they've taken some choices and options out of the equation. They're asking people not to support a specific version of Chrome, but rather the Chrome browser platform--which makes it easier: instead of asking what browser version someone's using, one asks what browser, and the supporter can be reasonably assured that the user has the most recent version, with all the most recent bug fixes and features. Whatever the version number is, at best, incidental.
Firefox, on the other hand, still requires some user interaction to download and install updates; updates still go through an installation/update process that's visible to the user, and worse yet, they give the option to the user to ignore them. Extensions are tied to versions, which is why there's frequent breakage on updates. Finally, on first launch, and whenever you visit the page, the version number is there, like it's important or something. Mozilla is still thinking with versions--which makes it important to ask what version of the browser someone's using, and leaving the supporter wondering what updates and what features have been installed and applied.
Mozilla's only gotten the fast releases half-right.