Re: Major enhancements to pearweb
| From: | Jeff Moore | Date: | Wed, 06 Dec 2006 15:50:04 +0000 |
| Subject: | Re: Major enhancements to pearweb | ||
| References: | 1 2 3 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-45128@lists.php.net to get a copy of this message | ||
On Dec 5, 2006, at 11:58 PM, Greg Beaver wrote:
Jeff Moore wrote:I didn't see that. Do you mean release date? because I meant something like: "1.5.0RC1 (beta) was released 8 days ago on 2006-11-28" This makes it easier to correlate with the bug summary: Average age of open bugs: 6 days Oldest open bug: 20 daysDays since last releaseThis is already available in the Downloads tab
I was just looking for more visibility for the documentation and the ability to get a better idea if it is being kept up to date. On the package info summary page, the "Current Release" section is like a summary of the downloads tab and the "Bug Summary" is a summary of the Bugs tab. Perhaps there should be another section, "Documentation summary." This could have a link to the End User documentation and the API documentation of the current release. That would make it easier to see if "No end-user documentation is available for this package." It would also make the documentation much more visible and save clicking on the tab for the most common case. Along those lines, maybe a "Trackback Summary" would help highlight that feature. What do you think? Best Regards, JeffDays since documentation updateThis would be astronomically difficult to implement, as each doc file would need to be checked individually in CVS, I'm not sure I want to go this route :).