Comment 3 for bug 878102

I feel our document is always outdated if you look into the details. Monthly release cycle is tight, actually not even monthly because we have some frozen days. There is a gap between ideal and reality. About this document issue, we have discussed in our previous Connect session, but we don't have a completed solution until now. And we can't hire a document writer to do this because only the developers now what exactly it is. So far the best practice is we will update it when we find it's outdated. For example, there is a chance that I need to read some thing from our wiki site and I find it's outdated according to my experience or knowledge, then I will update. But we can't do this before every component release or RC date because the time is really really tight. :)