Probably more like no one is taking care of updating the documentation.  Many factors that contribute to this lack of updates including resources available to actually review the various subjects and keep up with the documentation.  This has always been an issue in ALL development projects.  Bringing solutions to the community seems to follow the rule - code it then try to document it before the next release makes your doc out of date.  It's the last thing programmers want to do.  I've had program developers tell me that the documentation is in the code.   Ok, it's sort of like saying 'the check is in the mail'.

I don't dismiss the question, nor do I really have an official answer.  This is just a comment about a criticism that has always been around, and despite the best efforts and intentions is never quite handled in timely fashion.  There have been loads of improvements and corrections to the code and methods since 2005, but the basics are still the same.  It's not a great deal of help if you do not read the code source and test the methods documented in a test area, and make adjustments to the doc yourself.  It's the reality we endure for the other work that is being done.

I agree that it would be nice to have the latest versions updated, but many find 'writing' books and charging subscriptions to help sites fill that void, if only for snapshots in time, like every other application.  The good news - you can usually get clarification on a piece of outdated doc by asking a question on the relevant thread here in these forums.  Most knowlegeable folks will respond in time.

Cheers

They spend all the money you paid for your copy for documentation ;)

Open Source Software needs to work different than commercially licenced products: it requires the community to contribute. Write down your experiences and publish it! There is currently a documentation team working on setting up a new documentation repository, where all available pieces of documentation will be made available.