I suppose the long term view is - what's the economic health of the organization responsible for ongoing maintenance as well as R&D, features, engineering of the software? And also what's the risk of Firefox being "orphaned" or falling behind technologically to Chrome/Webkit. although the comment below is true; there is a time and place for long term strategic comments, vs. technical release notes...
Usually release notes exhibit the state and changes of the software, not the workings and changes of the maintainers. What were you expecting, something like this?
New:
- Firefox can now be set as the default system PDF viewer.