What else would I need to praise the blessings of DrupalEd?

I do sing and praise the blessings of DrupalEd, but, but, but...
Ah, at the risk of being considered ungrateful (something unthinkable, by all means), and since of course I would love to use it in a real, live, well populated project for a local institution, here's what I'd need to praise DrupalEd's blessings without my present reservations, purely egotistical, naturally:

• An upgrade to the latest core and modules code (the package does not include the latest of the core and certainly not the latest of many modules). Also, of course, a list of all the versions.
• Documentation that lists the many features included instead of making the user figure them out by exploring everything. Sigh.
• Documentation that lists the way every included feature works. In other words: how is it that you combine this module and that module with this view to get this result. By the way, I think this is what Drupal sorely needs to be number one.
• Documentation on how to remove a module without trashing the whole enchilada. What tables do I drop? What fields? What permissions? Also, on how to add a role.
• Documentation on what each user role sees, in order to be able to move the blocks fearlessly.

Don't get me wrong. I do think DrupalEd is a great effort and a very powerful showcase singing the goodness of Drupal, and I can't thank its developers enough. But it does need better documentation to be really a treasure. Or rather a more perfect treasure.