1 |
Hi guys. I dunno about you, but I'm getting tired of folks bashing our |
2 |
docs as being "out of date", "stale", "old", or "inaccurate" just |
3 |
because of the displayed date of the last update. |
4 |
|
5 |
I propose that we keep the date inside the document code, for our own |
6 |
internal purposes, but remove it from the final rendered page. |
7 |
|
8 |
As you know, the date displayed has little relevance to when we last |
9 |
actually touched-up the document, given our internal date bump policy. |
10 |
|
11 |
The only possible downside I can see to this is that we might get fewer |
12 |
patches/bug reports from users who see an "old" date and feel the need |
13 |
to send in stuff based on it. Anyone know if this is a common |
14 |
occurrence? Is there otherwise really a *need* to display the date? |
15 |
|
16 |
I look at it like this . . . sometimes, our docs are okay because |
17 |
they're feature-complete. They don't *need* any further updating. Just |
18 |
like gamin, which hasn't had an upstream release since 2007....it's |
19 |
because it "just works." I like to think our docs are this way, too. |
20 |
Mostly. :) |
21 |
|
22 |
So. There's my proposal. Thoughts? |