cvs: qaweb / handling-bugs.php howtohelp.php index.php links.php members.php projects.php running-tests.php stats.php styles.css /include
functions.php
| From: | Derick Rethans | Date: | Sat, 18 Jan 2003 22:33:15 +0000 |
| Subject: | cvs: qaweb / handling-bugs.php howtohelp.php index.php links.php members.php projects.php running-tests.php stats.php styles.css /include functions.php |
||
| Groups: | php.qa | ||
| Request: | Send a blank email to php-qa+get-8233@lists.php.net to get a copy of this message | ||
derick Sat Jan 18 17:33:15 2003 EDT
Added files:
/qaweb handling-bugs.php stats.php
Removed files:
/qaweb links.php members.php
Modified files:
/qaweb howtohelp.php index.php projects.php running-tests.php
styles.css
/qaweb/include functions.php
Log:
- Upgrade PHP QA website
Index: qaweb/howtohelp.php diff -u qaweb/howtohelp.php:1.14 qaweb/howtohelp.php:1.15 --- qaweb/howtohelp.php:1.14 Wed Nov 27 14:16:33 2002 +++ qaweb/howtohelp.php Sat Jan 18 17:33:14 2003 @@ -3,11 +3,11 @@ $TITLE = "How To Help [PHP-QAT: Quality Assurance Team]"; $SITE_UPDATE = date("D M d H:i:s Y T", filectime($SCRIPT_FILENAME))."<br> -/* $Id: howtohelp.php,v 1.14 2002/11/27 19:16:33 derick Exp $ */"; +/* $Id: howtohelp.php,v 1.15 2003/01/18 22:33:14 derick Exp $ */"; common_header(); ?> - <table width="70%" border="0" cellspacing="0" cellpadding="0"> + <table width="70%" border="0" cellspacing="0" cellpadding="0"> <tr> <td width="10"><img src="gfx/spacer.gif" width="10" height="1"></td> <td width="100%"> @@ -17,8 +17,8 @@ </tr> <tr> <td width="10"> </td> - <td width="100%">You can help the QA effort in several ways: <br> - <br> + <td width="100%">You can help the QA effort in several ways:<br /> + <br /> </td> <td width="10"> </td> </tr> @@ -26,18 +26,26 @@ <td width="10"> </td> <td width="100%"> <ul> - <li class="lihack">If you have some spare time, why not join the - PHP/QA team? Follow the members link to find out how. </li> - <li class="lihack">Submit a bug report. If you find what you think - is a problem, drop by <a href="http://bugs.php.net/" target="_blank">http://bugs.php.net/</a> and submit a report. - Just make sure to read the Dos and Dont's of bug submission before - posting a bug. </li> - <li class="lihack">Give a PHP/QA Team member space on a server that - you administrate. To do this, please send mail to the PHP/QA email - list (<a href="mailto:php-qa@lists.php.net">php-qa@lists.php.net</a>) with the subject 'Guest Account for - PHP/QA Team Member'. In the body of the message, please list the - specifications on the machine (hardware, operating system, installed - software, etc...). </li> + <li class="lihack">Write testcases: + <ul> + <li class="lihack">to reproduce bugs</li> + <li class="lihack">for PHP functions for which no testcase exist</li> + </ul> + </li> + <li class="lihack"> + Run our <a href="/running-tests.php">test suite</a> on a + regular schedule, we're currently setting up a system to do + this all automatically.<br /><br /> + </li> + <li class="lihack">Give a PHP/QA Team member access to a server that + you administrate, especially on ones running some of the more + exotic Operation Systems. <br /><br /> To do this, please send + mail to the PHP/QA email list (<a + href="mailto:php-qa@lists.php.net">php-qa@lists.php.net</a>) + with the subject 'Guest Account for PHP/QA Team Member'. In the + body of the message, please list the specifications on the + machine (hardware, operating system, installed software, + etc...). </li> </ul> </td> <td width="10"> </td> Index: qaweb/index.php diff -u qaweb/index.php:1.59 qaweb/index.php:1.60 --- qaweb/index.php:1.59 Sat Dec 21 16:02:45 2002 +++ qaweb/index.php Sat Jan 18 17:33:14 2003 @@ -2,8 +2,8 @@ include("include/functions.php"); $TITLE = "PHP-QAT: Quality Assurance Team"; -$SITE_UPDATE = date("D M d H:i:s Y T", filectime($SCRIPT_FILENAME))."<br> -/* $Id: index.php,v 1.59 2002/12/21 21:02:45 edink Exp $ */"; +$SITE_UPDATE = date("D M d H:i:s Y T", filectime($SCRIPT_FILENAME)); +/* $Id: index.php,v 1.60 2003/01/18 22:33:14 derick Exp $ */ common_header(); ?> @@ -11,33 +11,24 @@ <tr> <td width="10"><img src="gfx/spacer.gif" width="10" height="1"></td> <td width="100%"> - <h1>Welcome to the<br> - PHP Quality Assurance Team Web Page.</h1> - </td> - <td width="10"><img src="gfx/spacer.gif" width="10" height="1"></td> - </tr> - <tr> - <td width="10"> </td> - <td width="100%"> - <p>The team is currently focused on:</p> - <ul> - <li> - <span class="lihack">Providing QA for the PHP 4.3.0RC4 (<a href="http://www.php.net/~andrei/php-4.3.0RC4.tar.gz">source</a>, <a href="http://snaps.php.net/~edink/php-4.3.0RC4-Win32.zip">windows binaries</a>) release.</span><br /> - </li> - </ul> + <h1>Welcome to the<br />PHP Quality Assurance Team Web Page</h1> + <p> - You can help us by running the test framework, see:<br /> - <a href="http://qa.php.net/running-tests.php">http://qa.php.net/running-tests.php</a> + The PHP Quality Assurance Team is supporting to the PHP + Development Team by means of providing them with information on + compatibility and stability issues. + </p> + <p> + The team is currently focused on upgrading the testsuite. This + includes extending the testsuites with tests for every function, + collecting test data in a different way then mailing all output + to the QA mailinglist. + </p> + <p> + If you would like to contribute to this effort, please visit our + <a href="howtohelp.php">How To Help</a> page. </p> </td> - <td width="10"> </td> - </tr> - <tr> - <td width="10"> </td> - <td width="100%"> - <p>If you would like to contribute to this effort, please - visit our <a href="howtohelp.php">How To Help</a> page.</p> - </td> <td width="10"> </td> </tr> <tr> Index: qaweb/projects.php diff -u qaweb/projects.php:1.4 qaweb/projects.php:1.5 --- qaweb/projects.php:1.4 Fri Mar 15 19:14:14 2002 +++ qaweb/projects.php Sat Jan 18 17:33:14 2003 @@ -3,7 +3,7 @@ $TITLE = "Projects & Goals [PHP-QAT: Quality Assurance Team]"; $SITE_UPDATE = date("D M d H:i:s Y T", filectime($SCRIPT_FILENAME))."<br> -/* $Id: projects.php,v 1.4 2002/03/16 00:14:14 imajes Exp $ */"; +/* $Id: projects.php,v 1.5 2003/01/18 22:33:14 derick Exp $ */"; common_header(); ?> @@ -64,8 +64,7 @@ <tr> <td width="10"> </td> <td width="100%"> - <h3><a class="h3_link" href="http://bugs.php.net" target="_blank">Bug - Hunting</a></h3> + <h3>Bug Hunting</h3> </td> <td width="10"> </td> </tr> @@ -73,7 +72,7 @@ <td width="10"> </td> <td width="100%"> <ul> - <li><span class="lihack">analysing/closing existing bug reports at bugs.php.net </span></li> + <li><span class="lihack"><a href="handling-bugs.php">analysing/closing existing bug reports</a> at bugs.php.net </span></li> <li><span class="lihack">analysing new bugs posted on the php-dev list </span></li> <li><span class="lihack">actively seeking and tracking bugs on available platforms </span></li> <li><span class="lihack">monitoring/reviewing information from existing PHP mailing lists</span></li> @@ -84,38 +83,6 @@ <tr> <td width="10"> </td> <td width="100%"> - <h1>Finish PHP-QAT Website</h1> - </td> - <td width="10"> </td> - </tr> - <tr> - <td width="10"> </td> - <td width="100%"> - <h3>QA Team Roster Application</h3> - </td> - <td width="10"> </td> - </tr> - <tr> - <td width="10"> </td> - <td width="100%"> - <ul> - <li><span class="lihack">Finish how to help page </span></li> - <li><span class="lihack">Archive and condense important threads from the php-qa list - à la perl.com</span></li> - <li><span class="lihack">Expand projects/goals page: - <ul> - <li>add additional information on projects. </li> - <li>build simple interface to allow project managers to update - goals, status, members, etc... for projects</li> - </ul> - </span></li> - </ul> - </td> - <td width="10"> </td> - </tr> - <tr> - <td width="10"> </td> - <td width="100%"> <h3>Provide Client-Side Bug Reporting via PHP Interpreter</h3> </td> <td width="10"> </td> @@ -147,4 +114,4 @@ <?php common_footer(); -?> \ No newline at end of file +?> Index: qaweb/running-tests.php diff -u qaweb/running-tests.php:1.6 qaweb/running-tests.php:1.7 --- qaweb/running-tests.php:1.6 Tue Dec 17 14:29:11 2002 +++ qaweb/running-tests.php Sat Jan 18 17:33:14 2003 @@ -2,8 +2,8 @@ include("include/functions.php"); $TITLE = "Submit Build Test [PHP-QAT: Quality Assurance Team]"; -$SITE_UPDATE = date("D M d H:i:s Y T", filectime($SCRIPT_FILENAME))."<br> -/* $Id: running-tests.php,v 1.6 2002/12/17 19:29:11 derick Exp $ */"; +$SITE_UPDATE = date("D M d H:i:s Y T", filectime($SCRIPT_FILENAME)); +/* $Id: running-tests.php,v 1.7 2003/01/18 22:33:14 derick Exp $ */ common_header(); ?> @@ -11,7 +11,7 @@ <tr> <td width="10"><img src="gfx/spacer.gif" width="10" height="1"></td> <td width="100%"> -<h2>Test framework tests</h2> +<h1>Test framework tests</h1> <p> Please run the tests from our test framework. You can do this by typing <code>make test</code> after you compiled PHP with <code>make</code>. You Index: qaweb/styles.css diff -u qaweb/styles.css:1.2 qaweb/styles.css:1.3 --- qaweb/styles.css:1.2 Sat Mar 16 14:58:33 2002 +++ qaweb/styles.css Sat Jan 18 17:33:14 2003 @@ -1,10 +1,27 @@ -body, ul, td, th { +body, ul, th, p, dd, dt { font-family: Arial, Helvetica, sans-serif; font-size: 11pt; text-decoration: none; color: #000000 } +dt { + font-weight: bold; + color: #FF9900; +} + +dd { + margin-bottom: 11px; +} + +ul { + font-family: Arial, Helvetica, sans-serif; + font-size: 11pt; + text-decoration: none; + color: #000000; + padding-bottom: 6pt; +} + input.small { font-size: 75%; } @@ -15,6 +32,7 @@ font-size: 18px; font-style: italic; font-weight: bold; + padding-bottom: 18px; } h2 { @@ -30,6 +48,7 @@ text-decoration: none; font-size: 14px; font-weight: bold; + padding-bottom: 7px; } h4 { Index: qaweb/include/functions.php diff -u qaweb/include/functions.php:1.8 qaweb/include/functions.php:1.9 --- qaweb/include/functions.php:1.8 Tue Jan 7 12:56:51 2003 +++ qaweb/include/functions.php Sat Jan 18 17:33:15 2003 @@ -3,7 +3,7 @@ (c)'2001 by Marco Kaiser (bate@php.net) and the PHP Group Read an Learn. Any Questions so ask. -Version: $Id: functions.php,v 1.8 2003/01/07 17:56:51 derick Exp $ +Version: $Id: functions.php,v 1.9 2003/01/18 22:33:15 derick Exp $ */ function common_header() { @@ -11,29 +11,29 @@ <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> <html> <head> - <title><?= $GLOBALS["TITLE"]; ?></title> + <title><?php echo $GLOBALS["TITLE"]; ?></title> <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1"> <meta name="MSSmartTagsPreventParsing" content="TRUE"> <link rel="stylesheet" href="styles.css" type="text/css"> </head> <body bgcolor="#ffffff" text="#000000" link="#000000" vlink="#000000" alink="#000000" topmargin="0" leftmargin="0" marginheight="0" marginwidth="0"> -<table width="100%" border="0" cellspacing="0" cellpadding="0" height="102"> +<table width="100%" border="0" cellspacing="0" cellpadding="0"> <tr> <td bgcolor="#ffcc66"><img src="gfx/spacer.gif" width="5" height="1"> <a href="http://qa.php.net/"><img src="gfx/logo_qa.jpg" width="111" height="58" border="0"></a></td> <td bgcolor="#ffcc66" align="right" valign="bottom"> <table border="0" cellspacing="0" cellpadding="0" height="70"> <tr> - <td align="right" valign="top" class="headline_white"><?= date("l, F d, Y", time()); ?></td> + <td align="right" valign="top" class="headline_white"><?php echo date("l, F d, Y"); ?></td> <td align="right" valign="top" class="headline_white"><img src="gfx/spacer.gif" width="5" height="1"></td> </tr> <tr> <td valign="bottom" align="right"><a href="/" class="head_links">Home</a> | <a href="projects.php" class="head_links">Projects and Goals</a> - | <a href="links.php" class="head_links">Links & Resources</a> - | <a href="members.php" class="head_links">Members</a> - | <a href="howtohelp.php" class="head_links">How to help</a> + | <a href="howtohelp.php" class="head_links">How to Help</a> + | <a href="stats.php" class="head_links">Statistics</a> + | <a href="handling-bugs.php" class="head_links">Handling Bug Reports</a> | <a href="running-tests.php" class="head_links">Submit a build test</a> </td> <td valign="bottom" align="right" class="head_links"> </td> @@ -45,20 +45,14 @@ <td colspan="2" bgcolor="#000000" height="1"><img src="gfx/spacer.gif" width="1" height="1" border="0"></td> </tr> <tr> - <form method="get" action="http://bugs.php.net/search.php" target="_blank"> - <td colspan="2" bgcolor="#ff9900" align="right" class="head_links"> search - qa for - <input type="hidden" name="cmd" value="display"> - <input type="text" name="search_for" value="" size="30" class="small"> - <input type="image" src="gfx/submit.gif" border="0" width="11" height="11" alt="search" align="bottom" name="image"> <img src="gfx/spacer.gif" width="3" height="8" border="0"></td> - </form> + <td colspan="2" bgcolor="#ff9900" align="right" class="head_links"> </td> </tr> <tr> <td colspan="2" bgcolor="#000000" height="1"><img src="gfx/spacer.gif" width="1" height="1"></td> </tr> </table> -<table width="100%" border="0" cellspacing="0" cellpadding="0"> +<table width="100%" border="0" cellspacing="0" cellpadding="0" height="70%"> <tr> <td width="200" bgcolor="#eeeeee" align="center" valign="top"> <table width="95%" border="0" cellspacing="0" cellpadding="0"> @@ -87,39 +81,23 @@ </tr> <tr> <td class="sidebox"> - <h2>Links & Resources</h2> - </td> - </tr> - <tr> - <td class="sidebox"> - Visit the PHP|QAT <a href="links.php">Links & Resources</a> page. - We have links to web based resources for ... - </td> - </tr> - <tr> - <td class="sidebox"> - <h2>Members</h2> - </td> - </tr> - <tr> - <td class="sidebox"> - View the PHP-QAT <a href="members.php">Member register</a>. - </td> - </tr> - <tr> - <td class="sidebox"> <h2>Contact Information</h2> </td> </tr> <tr> <td class="sidebox"> - - <p>Questions about the PHP-QAT should be sent to the <a href="mailto:php-qa@lists.php.net">PHP/QAT - Mailing List</a></p> - <p> Bug Reports should be submitted to the official PHP bug list - (<a href="http://bugs.php.net/" target="_blank">http://bugs.php.net</a>)</p> - <p> All other questions should be directed to the appropriate <a href="http://www.php.net/support.php" target="_blank">PHP - mailing list.</a> </p> + Questions about the PHP-QAT should be sent to the + <a href="mailto:php-qa@lists.php.net">PHP/QAT Mailing List</a> + <br /> + <br /> + + Bug Reports should be submitted to the official PHP bug list + (<a href="http://bugs.php.net/" target="_blank">http://bugs.php.net</a>) + <br /> + <br /> + + All other questions should be directed to the appropriate + <a href="http://www.php.net/support.php" target="_blank">PHP mailing list.</a> </td> </tr> </table> @@ -134,7 +112,7 @@ ?> </tr> </table> -<table width="100%" border="0" cellspacing="0" cellpadding="0" height="22"> +<table width="100%" border="0" cellspacing="0" cellpadding="0"> <tr> <td bgcolor="#000000"><img src="gfx/spacer.gif" width="1" height="1"></td> </tr> @@ -158,7 +136,7 @@ </table> </td> <td bgcolor="#cccccc" nowrap align="right" class="footer">Last - update: <?= $GLOBALS["SITE_UPDATE"]; ?></td> + update: <?php echo $GLOBALS["SITE_UPDATE"]; ?></td> <td bgcolor="#cccccc" nowrap align="right" class="footer"><img src="gfx/spacer.gif" width="10" height="1"></td> </tr> </table> Index: qaweb/handling-bugs.php +++ qaweb/handling-bugs.php <?php include("include/functions.php"); $TITLE = "How To Help [PHP-QAT: Quality Assurance Team]"; $SITE_UPDATE = date("D M d H:i:s Y T", filectime($SCRIPT_FILENAME))."<br> /* $Id: handling-bugs.php,v 1.1 2003/01/18 22:33:14 derick Exp $ */"; common_header(); ?> <table width="70%" border="0" cellspacing="0" cellpadding="0"> <tr> <td width="10"><img src="gfx/spacer.gif" width="10" height="1"></td> <td width="100%"> <h1>Handling bug reports?</h1> </td> <td width="10"><img src="gfx/spacer.gif" width="10" height="1"></td> </tr> <tr> <td width="10"> </td> <td width="100%"> <h2>Introduction</h2> <p> Welcome to the HOWTO on managing PHP bugs via <a href="http://bugs.php.net/">bugs.php.net</a>. PHP is a large project with many bugs being submitted daily. Bug topics range from the PHP website itself, various PHP extensions, PEAR, etc. This document is for all PHP developers using the bug system. Because there are so many members using the system it's important we act in a consistent manner. This HOWTO is created to solve this. </p> <p>If you're going to edit a bug be sure that you know the topic. Don't make assumptions. If you've read the bug carefully and think of a solution or related questions, post your answer/comments. If you know of the solution, solve and close the bug.</p> <h2>Acting on a bug</h2> <p>Never change a status if you're not sure. If you close a bug because you think it's not really a bug and in fact it is, this makes the bug system useless and doesn't benefit anyone. Never close a bug because it's too old, unless your name is Jani. If a bug is in "feedback" status it will close automatically if the bug reporter doesn't answer after two weeks.</p> <p>If you want to view a bug report, enter the bug id into the url like so (with 20406 being an example):</p> <ul> <li> <a href="http://bugs.php.net/20406">http://bugs.php.net/20406</a> </li> </ul> <p>Which redirects to:</p> <ul> <li> <a href="http://bugs.php.net/bug.php?id=20406">http://bugs.php.net/bug.php?id=20406</a> </li> </ul> <p>At that point you'll see a set of options. Because you're a developer you will choose the developer option which will then put you here:</p> <ul> <li> <a href="http://bugs.php.net/bug.php?id=20406&edit=1">http://bugs.php.net/bug.php?id=20406&edit=1</a> </li> </ul> <h2>Automatic answers (quickfix)</h2> <p>There are a set of quickfix options each of which will both insert text into the bug report and change the bug status. Please understand what text and status will be used and only choose a quickfix option if an appropriate quickfix exists. Choosing a quickfix that's not 100% correct will confuse and sometimes irritate the reporter. The following table lists them (see also <a href="http://bugs.php.net/quick-fix-desc.php">quick-fix-desc.php</a>):</p> <h2>Manual answers</h2> <p>If no quickfix is available you will manually choose the new status and write some feedback. Select the best status that corresponds to the bug. Here are descriptions for each status:</p> <p> <dl> <dt>Open</dt> <dd> The bug still exists and you want to comment on it. </dd> <dt>Closed</dt> <dd> It has been fixed. If you choose this please make sure it's also been documented. Also, explain why it's closed. </dd> <dt>Duplicate</dt> <dd> If this almost the same bug, both bugs are found 'duplicate' later on and have both useful information. Also mention what bug it's a duplicate of with a full url to the report this is duplicate of. </dd> <dt>Critical</dt> <dd> Only bugs that affect most/all users and/or are in the engine or ext/standard. Only Verified and reproduced bugs in the latest CVS can be marked critical. </dd> <dt>Assigned</dt> <dd> If a specific person, such as yourself, will take of this bug then assign it. If you know someone else is or will take care of it then assign it to them but be sure to ask them first. </dd> <dt>Analyzed</dt> <dd> If you've analyzed why this bug is here and know why the bug exists, you have just analyzed it. Also, add a comment. If you are unsure why it exists then use 'verified' instead. </dd> <dt>Verified</dt> <dd> If you're able to reproduce this bug with the information given. Be sure to test with the latest CVS. Typically you aren't sure why it exists you just know it does and have confirmed it. </dd> <dt>Suspended</dt> <dd> Usually used when there might be a fix in future and/or it relies on something external to be fixed first. </dd> <dt>Wont fix</dt> <dd>When something is not considered a bug or the bug is not fixable.</dd> <dt>No feedback</dt> <dd> If no answer have been given by the reporter after we've asked them something. Sometimes you will ask for an example script or ask the reporter to test using CVS or the latest snap. </dd> <dt>Feedback</dt> <dd> You're asking the reporter for more information such as please use CVS/snap, and/or the smallest possible test script to reproduce the error, and/or a value for a certain PHP directive. </dd> <dt>Bogus</dt> <dd> This bug is not a bug, support related or just an assumed bug. Be 100% it's really bogus and also be sure it's not a documentation bug. </dd> </dl> <h2>Reclassification</h2> <p>Sometimes you'll also want to reclassify a bug. For example, a reporter marks a bug as Apache2 related when really it's a MySQL bug. Just change the category but be 100% sure it's related to the new category. Another example would be changing the type to a documentation bug. If you're changing it to a documentation bug it will help the documentation team if you add specific information that is to be documented including what version the changes will take place.</p> <p>Also note that all bugs are sent to various mailing lists with php-bugs@lists.php.net being the default (most go here). Here's a list:</p> <dl> <dt>Default</dt> <dd><a href="http://news.php.net/group.php?group=php.bugs">php-bugs@lists.php.net</a></dd> <dt>Documentation</dt> <dd><a href="http://marc.theaimsgroup.com/?l=phpdoc">phpdoc@lists.php.net</a></dd> <dt>PEAR</dt> <dd><a href="http://marc.theaimsgroup.com/?l=pear-dev">pear-dev@lists.php.net</a></dd> <dt>PHP.net Website</dt> <dd><a href="http://news.php.net/group.php?group=php.mirrors">php-mirrors@lists.php.net</a></dd> </dl> <p>Reclassifying will immediatly change which mailing list is used. If you reclassify a bug and don't leave a comment then no email is sent to the mailing list. So, be sure to leave a comment.</p> <h2>Tips and links</h2> <ul> <li> The Jani Javascript bug popup window (right click to bookmark): <a href='javascript:void(t=prompt("Get BUG report # ..",""));if(t){ void(top.location.href="http://bugs.php.net/bug.php?edit=1&id="+t);}'>here</a> </li> <li> Look at the <a href="http://bugs.php.net/bugstats.php">raw bug stats</a> OR a <a href="http://www.php.net/~jani/bugs-graph.php">graph</a>. </li> <li> Not leaving a comment means no email will be sent to the mailing list. (all quickfix options leave comments) </li> <li> If a version involves CVS or a snapshot be sure to label it in the form: <b>4.x.y-dev</b> An example is: 4.3.0-dev. </li> <li> If you have a question either email the <a href="mailto:php-dev@lists.php.net">php-dev@lists.php.net</a> mailing list or check out the #php.bugs channel in IRC on <a href="http://www.irchelp.org/irchelp/networks/efnet.txt">EFNET</a>. </li> </ul> <h2>Conclusion</h2> <p>If everyone maintains the bug system in a consistent manner then PHP will be better for it. Also, bug reporters will not get their feelings hurt through miscommunication (e.g. a wrong quickfix or bogus status) Thank you for reading this HOWTO and helping make PHP better.</p> <br /> </td> <td width="10"> </td> </tr> </table> <?php common_footer(); ?> Index: qaweb/stats.php +++ qaweb/stats.php <?php include("include/functions.php"); $TITLE = "How To Help [PHP-QAT: Quality Assurance Team]"; $SITE_UPDATE = date("D M d H:i:s Y T", filectime($SCRIPT_FILENAME))."<br> /* $Id: stats.php,v 1.1 2003/01/18 22:33:14 derick Exp $ */"; common_header(); ?> <table width="70%" border="0" cellspacing="0" cellpadding="0"> <tr> <td width="10"><img src="gfx/spacer.gif" width="10" height="1"></td> <td width="100%"> <h1>Statistics</h1> </td> <td width="10"><img src="gfx/spacer.gif" width="10" height="1"></td> </tr> <tr> <td width="10"> </td> <td width="100%"><img src="http://www.php.net/~jani/count-<?php echo date ('Y-m'); ?>.png"><br /><br /> </td> <td width="10"> </td> </tr> </table> <?php common_footer(); ?>
Index: qaweb/howtohelp.php diff -u qaweb/howtohelp.php:1.14 qaweb/howtohelp.php:1.15 --- qaweb/howtohelp.php:1.14 Wed Nov 27 14:16:33 2002 +++ qaweb/howtohelp.php Sat Jan 18 17:33:14 2003 @@ -3,11 +3,11 @@ $TITLE = "How To Help [PHP-QAT: Quality Assurance Team]"; $SITE_UPDATE = date("D M d H:i:s Y T", filectime($SCRIPT_FILENAME))."<br> -/* $Id: howtohelp.php,v 1.14 2002/11/27 19:16:33 derick Exp $ */"; +/* $Id: howtohelp.php,v 1.15 2003/01/18 22:33:14 derick Exp $ */"; common_header(); ?> - <table width="70%" border="0" cellspacing="0" cellpadding="0"> + <table width="70%" border="0" cellspacing="0" cellpadding="0"> <tr> <td width="10"><img src="gfx/spacer.gif" width="10" height="1"></td> <td width="100%"> @@ -17,8 +17,8 @@ </tr> <tr> <td width="10"> </td> - <td width="100%">You can help the QA effort in several ways: <br> - <br> + <td width="100%">You can help the QA effort in several ways:<br /> + <br /> </td> <td width="10"> </td> </tr> @@ -26,18 +26,26 @@ <td width="10"> </td> <td width="100%"> <ul> - <li class="lihack">If you have some spare time, why not join the - PHP/QA team? Follow the members link to find out how. </li> - <li class="lihack">Submit a bug report. If you find what you think - is a problem, drop by <a href="http://bugs.php.net/" target="_blank">http://bugs.php.net/</a> and submit a report. - Just make sure to read the Dos and Dont's of bug submission before - posting a bug. </li> - <li class="lihack">Give a PHP/QA Team member space on a server that - you administrate. To do this, please send mail to the PHP/QA email - list (<a href="mailto:php-qa@lists.php.net">php-qa@lists.php.net</a>) with the subject 'Guest Account for - PHP/QA Team Member'. In the body of the message, please list the - specifications on the machine (hardware, operating system, installed - software, etc...). </li> + <li class="lihack">Write testcases: + <ul> + <li class="lihack">to reproduce bugs</li> + <li class="lihack">for PHP functions for which no testcase exist</li> + </ul> + </li> + <li class="lihack"> + Run our <a href="/running-tests.php">test suite</a> on a + regular schedule, we're currently setting up a system to do + this all automatically.<br /><br /> + </li> + <li class="lihack">Give a PHP/QA Team member access to a server that + you administrate, especially on ones running some of the more + exotic Operation Systems. <br /><br /> To do this, please send + mail to the PHP/QA email list (<a + href="mailto:php-qa@lists.php.net">php-qa@lists.php.net</a>) + with the subject 'Guest Account for PHP/QA Team Member'. In the + body of the message, please list the specifications on the + machine (hardware, operating system, installed software, + etc...). </li> </ul> </td> <td width="10"> </td> Index: qaweb/index.php diff -u qaweb/index.php:1.59 qaweb/index.php:1.60 --- qaweb/index.php:1.59 Sat Dec 21 16:02:45 2002 +++ qaweb/index.php Sat Jan 18 17:33:14 2003 @@ -2,8 +2,8 @@ include("include/functions.php"); $TITLE = "PHP-QAT: Quality Assurance Team"; -$SITE_UPDATE = date("D M d H:i:s Y T", filectime($SCRIPT_FILENAME))."<br> -/* $Id: index.php,v 1.59 2002/12/21 21:02:45 edink Exp $ */"; +$SITE_UPDATE = date("D M d H:i:s Y T", filectime($SCRIPT_FILENAME)); +/* $Id: index.php,v 1.60 2003/01/18 22:33:14 derick Exp $ */ common_header(); ?> @@ -11,33 +11,24 @@ <tr> <td width="10"><img src="gfx/spacer.gif" width="10" height="1"></td> <td width="100%"> - <h1>Welcome to the<br> - PHP Quality Assurance Team Web Page.</h1> - </td> - <td width="10"><img src="gfx/spacer.gif" width="10" height="1"></td> - </tr> - <tr> - <td width="10"> </td> - <td width="100%"> - <p>The team is currently focused on:</p> - <ul> - <li> - <span class="lihack">Providing QA for the PHP 4.3.0RC4 (<a href="http://www.php.net/~andrei/php-4.3.0RC4.tar.gz">source</a>, <a href="http://snaps.php.net/~edink/php-4.3.0RC4-Win32.zip">windows binaries</a>) release.</span><br /> - </li> - </ul> + <h1>Welcome to the<br />PHP Quality Assurance Team Web Page</h1> + <p> - You can help us by running the test framework, see:<br /> - <a href="http://qa.php.net/running-tests.php">http://qa.php.net/running-tests.php</a> + The PHP Quality Assurance Team is supporting to the PHP + Development Team by means of providing them with information on + compatibility and stability issues. + </p> + <p> + The team is currently focused on upgrading the testsuite. This + includes extending the testsuites with tests for every function, + collecting test data in a different way then mailing all output + to the QA mailinglist. + </p> + <p> + If you would like to contribute to this effort, please visit our + <a href="howtohelp.php">How To Help</a> page. </p> </td> - <td width="10"> </td> - </tr> - <tr> - <td width="10"> </td> - <td width="100%"> - <p>If you would like to contribute to this effort, please - visit our <a href="howtohelp.php">How To Help</a> page.</p> - </td> <td width="10"> </td> </tr> <tr> Index: qaweb/projects.php diff -u qaweb/projects.php:1.4 qaweb/projects.php:1.5 --- qaweb/projects.php:1.4 Fri Mar 15 19:14:14 2002 +++ qaweb/projects.php Sat Jan 18 17:33:14 2003 @@ -3,7 +3,7 @@ $TITLE = "Projects & Goals [PHP-QAT: Quality Assurance Team]"; $SITE_UPDATE = date("D M d H:i:s Y T", filectime($SCRIPT_FILENAME))."<br> -/* $Id: projects.php,v 1.4 2002/03/16 00:14:14 imajes Exp $ */"; +/* $Id: projects.php,v 1.5 2003/01/18 22:33:14 derick Exp $ */"; common_header(); ?> @@ -64,8 +64,7 @@ <tr> <td width="10"> </td> <td width="100%"> - <h3><a class="h3_link" href="http://bugs.php.net" target="_blank">Bug - Hunting</a></h3> + <h3>Bug Hunting</h3> </td> <td width="10"> </td> </tr> @@ -73,7 +72,7 @@ <td width="10"> </td> <td width="100%"> <ul> - <li><span class="lihack">analysing/closing existing bug reports at bugs.php.net </span></li> + <li><span class="lihack"><a href="handling-bugs.php">analysing/closing existing bug reports</a> at bugs.php.net </span></li> <li><span class="lihack">analysing new bugs posted on the php-dev list </span></li> <li><span class="lihack">actively seeking and tracking bugs on available platforms </span></li> <li><span class="lihack">monitoring/reviewing information from existing PHP mailing lists</span></li> @@ -84,38 +83,6 @@ <tr> <td width="10"> </td> <td width="100%"> - <h1>Finish PHP-QAT Website</h1> - </td> - <td width="10"> </td> - </tr> - <tr> - <td width="10"> </td> - <td width="100%"> - <h3>QA Team Roster Application</h3> - </td> - <td width="10"> </td> - </tr> - <tr> - <td width="10"> </td> - <td width="100%"> - <ul> - <li><span class="lihack">Finish how to help page </span></li> - <li><span class="lihack">Archive and condense important threads from the php-qa list - à la perl.com</span></li> - <li><span class="lihack">Expand projects/goals page: - <ul> - <li>add additional information on projects. </li> - <li>build simple interface to allow project managers to update - goals, status, members, etc... for projects</li> - </ul> - </span></li> - </ul> - </td> - <td width="10"> </td> - </tr> - <tr> - <td width="10"> </td> - <td width="100%"> <h3>Provide Client-Side Bug Reporting via PHP Interpreter</h3> </td> <td width="10"> </td> @@ -147,4 +114,4 @@ <?php common_footer(); -?> \ No newline at end of file +?> Index: qaweb/running-tests.php diff -u qaweb/running-tests.php:1.6 qaweb/running-tests.php:1.7 --- qaweb/running-tests.php:1.6 Tue Dec 17 14:29:11 2002 +++ qaweb/running-tests.php Sat Jan 18 17:33:14 2003 @@ -2,8 +2,8 @@ include("include/functions.php"); $TITLE = "Submit Build Test [PHP-QAT: Quality Assurance Team]"; -$SITE_UPDATE = date("D M d H:i:s Y T", filectime($SCRIPT_FILENAME))."<br> -/* $Id: running-tests.php,v 1.6 2002/12/17 19:29:11 derick Exp $ */"; +$SITE_UPDATE = date("D M d H:i:s Y T", filectime($SCRIPT_FILENAME)); +/* $Id: running-tests.php,v 1.7 2003/01/18 22:33:14 derick Exp $ */ common_header(); ?> @@ -11,7 +11,7 @@ <tr> <td width="10"><img src="gfx/spacer.gif" width="10" height="1"></td> <td width="100%"> -<h2>Test framework tests</h2> +<h1>Test framework tests</h1> <p> Please run the tests from our test framework. You can do this by typing <code>make test</code> after you compiled PHP with <code>make</code>. You Index: qaweb/styles.css diff -u qaweb/styles.css:1.2 qaweb/styles.css:1.3 --- qaweb/styles.css:1.2 Sat Mar 16 14:58:33 2002 +++ qaweb/styles.css Sat Jan 18 17:33:14 2003 @@ -1,10 +1,27 @@ -body, ul, td, th { +body, ul, th, p, dd, dt { font-family: Arial, Helvetica, sans-serif; font-size: 11pt; text-decoration: none; color: #000000 } +dt { + font-weight: bold; + color: #FF9900; +} + +dd { + margin-bottom: 11px; +} + +ul { + font-family: Arial, Helvetica, sans-serif; + font-size: 11pt; + text-decoration: none; + color: #000000; + padding-bottom: 6pt; +} + input.small { font-size: 75%; } @@ -15,6 +32,7 @@ font-size: 18px; font-style: italic; font-weight: bold; + padding-bottom: 18px; } h2 { @@ -30,6 +48,7 @@ text-decoration: none; font-size: 14px; font-weight: bold; + padding-bottom: 7px; } h4 { Index: qaweb/include/functions.php diff -u qaweb/include/functions.php:1.8 qaweb/include/functions.php:1.9 --- qaweb/include/functions.php:1.8 Tue Jan 7 12:56:51 2003 +++ qaweb/include/functions.php Sat Jan 18 17:33:15 2003 @@ -3,7 +3,7 @@ (c)'2001 by Marco Kaiser (bate@php.net) and the PHP Group Read an Learn. Any Questions so ask. -Version: $Id: functions.php,v 1.8 2003/01/07 17:56:51 derick Exp $ +Version: $Id: functions.php,v 1.9 2003/01/18 22:33:15 derick Exp $ */ function common_header() { @@ -11,29 +11,29 @@ <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> <html> <head> - <title><?= $GLOBALS["TITLE"]; ?></title> + <title><?php echo $GLOBALS["TITLE"]; ?></title> <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1"> <meta name="MSSmartTagsPreventParsing" content="TRUE"> <link rel="stylesheet" href="styles.css" type="text/css"> </head> <body bgcolor="#ffffff" text="#000000" link="#000000" vlink="#000000" alink="#000000" topmargin="0" leftmargin="0" marginheight="0" marginwidth="0"> -<table width="100%" border="0" cellspacing="0" cellpadding="0" height="102"> +<table width="100%" border="0" cellspacing="0" cellpadding="0"> <tr> <td bgcolor="#ffcc66"><img src="gfx/spacer.gif" width="5" height="1"> <a href="http://qa.php.net/"><img src="gfx/logo_qa.jpg" width="111" height="58" border="0"></a></td> <td bgcolor="#ffcc66" align="right" valign="bottom"> <table border="0" cellspacing="0" cellpadding="0" height="70"> <tr> - <td align="right" valign="top" class="headline_white"><?= date("l, F d, Y", time()); ?></td> + <td align="right" valign="top" class="headline_white"><?php echo date("l, F d, Y"); ?></td> <td align="right" valign="top" class="headline_white"><img src="gfx/spacer.gif" width="5" height="1"></td> </tr> <tr> <td valign="bottom" align="right"><a href="/" class="head_links">Home</a> | <a href="projects.php" class="head_links">Projects and Goals</a> - | <a href="links.php" class="head_links">Links & Resources</a> - | <a href="members.php" class="head_links">Members</a> - | <a href="howtohelp.php" class="head_links">How to help</a> + | <a href="howtohelp.php" class="head_links">How to Help</a> + | <a href="stats.php" class="head_links">Statistics</a> + | <a href="handling-bugs.php" class="head_links">Handling Bug Reports</a> | <a href="running-tests.php" class="head_links">Submit a build test</a> </td> <td valign="bottom" align="right" class="head_links"> </td> @@ -45,20 +45,14 @@ <td colspan="2" bgcolor="#000000" height="1"><img src="gfx/spacer.gif" width="1" height="1" border="0"></td> </tr> <tr> - <form method="get" action="http://bugs.php.net/search.php" target="_blank"> - <td colspan="2" bgcolor="#ff9900" align="right" class="head_links"> search - qa for - <input type="hidden" name="cmd" value="display"> - <input type="text" name="search_for" value="" size="30" class="small"> - <input type="image" src="gfx/submit.gif" border="0" width="11" height="11" alt="search" align="bottom" name="image"> <img src="gfx/spacer.gif" width="3" height="8" border="0"></td> - </form> + <td colspan="2" bgcolor="#ff9900" align="right" class="head_links"> </td> </tr> <tr> <td colspan="2" bgcolor="#000000" height="1"><img src="gfx/spacer.gif" width="1" height="1"></td> </tr> </table> -<table width="100%" border="0" cellspacing="0" cellpadding="0"> +<table width="100%" border="0" cellspacing="0" cellpadding="0" height="70%"> <tr> <td width="200" bgcolor="#eeeeee" align="center" valign="top"> <table width="95%" border="0" cellspacing="0" cellpadding="0"> @@ -87,39 +81,23 @@ </tr> <tr> <td class="sidebox"> - <h2>Links & Resources</h2> - </td> - </tr> - <tr> - <td class="sidebox"> - Visit the PHP|QAT <a href="links.php">Links & Resources</a> page. - We have links to web based resources for ... - </td> - </tr> - <tr> - <td class="sidebox"> - <h2>Members</h2> - </td> - </tr> - <tr> - <td class="sidebox"> - View the PHP-QAT <a href="members.php">Member register</a>. - </td> - </tr> - <tr> - <td class="sidebox"> <h2>Contact Information</h2> </td> </tr> <tr> <td class="sidebox"> - - <p>Questions about the PHP-QAT should be sent to the <a href="mailto:php-qa@lists.php.net">PHP/QAT - Mailing List</a></p> - <p> Bug Reports should be submitted to the official PHP bug list - (<a href="http://bugs.php.net/" target="_blank">http://bugs.php.net</a>)</p> - <p> All other questions should be directed to the appropriate <a href="http://www.php.net/support.php" target="_blank">PHP - mailing list.</a> </p> + Questions about the PHP-QAT should be sent to the + <a href="mailto:php-qa@lists.php.net">PHP/QAT Mailing List</a> + <br /> + <br /> + + Bug Reports should be submitted to the official PHP bug list + (<a href="http://bugs.php.net/" target="_blank">http://bugs.php.net</a>) + <br /> + <br /> + + All other questions should be directed to the appropriate + <a href="http://www.php.net/support.php" target="_blank">PHP mailing list.</a> </td> </tr> </table> @@ -134,7 +112,7 @@ ?> </tr> </table> -<table width="100%" border="0" cellspacing="0" cellpadding="0" height="22"> +<table width="100%" border="0" cellspacing="0" cellpadding="0"> <tr> <td bgcolor="#000000"><img src="gfx/spacer.gif" width="1" height="1"></td> </tr> @@ -158,7 +136,7 @@ </table> </td> <td bgcolor="#cccccc" nowrap align="right" class="footer">Last - update: <?= $GLOBALS["SITE_UPDATE"]; ?></td> + update: <?php echo $GLOBALS["SITE_UPDATE"]; ?></td> <td bgcolor="#cccccc" nowrap align="right" class="footer"><img src="gfx/spacer.gif" width="10" height="1"></td> </tr> </table> Index: qaweb/handling-bugs.php +++ qaweb/handling-bugs.php <?php include("include/functions.php"); $TITLE = "How To Help [PHP-QAT: Quality Assurance Team]"; $SITE_UPDATE = date("D M d H:i:s Y T", filectime($SCRIPT_FILENAME))."<br> /* $Id: handling-bugs.php,v 1.1 2003/01/18 22:33:14 derick Exp $ */"; common_header(); ?> <table width="70%" border="0" cellspacing="0" cellpadding="0"> <tr> <td width="10"><img src="gfx/spacer.gif" width="10" height="1"></td> <td width="100%"> <h1>Handling bug reports?</h1> </td> <td width="10"><img src="gfx/spacer.gif" width="10" height="1"></td> </tr> <tr> <td width="10"> </td> <td width="100%"> <h2>Introduction</h2> <p> Welcome to the HOWTO on managing PHP bugs via <a href="http://bugs.php.net/">bugs.php.net</a>. PHP is a large project with many bugs being submitted daily. Bug topics range from the PHP website itself, various PHP extensions, PEAR, etc. This document is for all PHP developers using the bug system. Because there are so many members using the system it's important we act in a consistent manner. This HOWTO is created to solve this. </p> <p>If you're going to edit a bug be sure that you know the topic. Don't make assumptions. If you've read the bug carefully and think of a solution or related questions, post your answer/comments. If you know of the solution, solve and close the bug.</p> <h2>Acting on a bug</h2> <p>Never change a status if you're not sure. If you close a bug because you think it's not really a bug and in fact it is, this makes the bug system useless and doesn't benefit anyone. Never close a bug because it's too old, unless your name is Jani. If a bug is in "feedback" status it will close automatically if the bug reporter doesn't answer after two weeks.</p> <p>If you want to view a bug report, enter the bug id into the url like so (with 20406 being an example):</p> <ul> <li> <a href="http://bugs.php.net/20406">http://bugs.php.net/20406</a> </li> </ul> <p>Which redirects to:</p> <ul> <li> <a href="http://bugs.php.net/bug.php?id=20406">http://bugs.php.net/bug.php?id=20406</a> </li> </ul> <p>At that point you'll see a set of options. Because you're a developer you will choose the developer option which will then put you here:</p> <ul> <li> <a href="http://bugs.php.net/bug.php?id=20406&edit=1">http://bugs.php.net/bug.php?id=20406&edit=1</a> </li> </ul> <h2>Automatic answers (quickfix)</h2> <p>There are a set of quickfix options each of which will both insert text into the bug report and change the bug status. Please understand what text and status will be used and only choose a quickfix option if an appropriate quickfix exists. Choosing a quickfix that's not 100% correct will confuse and sometimes irritate the reporter. The following table lists them (see also <a href="http://bugs.php.net/quick-fix-desc.php">quick-fix-desc.php</a>):</p> <h2>Manual answers</h2> <p>If no quickfix is available you will manually choose the new status and write some feedback. Select the best status that corresponds to the bug. Here are descriptions for each status:</p> <p> <dl> <dt>Open</dt> <dd> The bug still exists and you want to comment on it. </dd> <dt>Closed</dt> <dd> It has been fixed. If you choose this please make sure it's also been documented. Also, explain why it's closed. </dd> <dt>Duplicate</dt> <dd> If this almost the same bug, both bugs are found 'duplicate' later on and have both useful information. Also mention what bug it's a duplicate of with a full url to the report this is duplicate of. </dd> <dt>Critical</dt> <dd> Only bugs that affect most/all users and/or are in the engine or ext/standard. Only Verified and reproduced bugs in the latest CVS can be marked critical. </dd> <dt>Assigned</dt> <dd> If a specific person, such as yourself, will take of this bug then assign it. If you know someone else is or will take care of it then assign it to them but be sure to ask them first. </dd> <dt>Analyzed</dt> <dd> If you've analyzed why this bug is here and know why the bug exists, you have just analyzed it. Also, add a comment. If you are unsure why it exists then use 'verified' instead. </dd> <dt>Verified</dt> <dd> If you're able to reproduce this bug with the information given. Be sure to test with the latest CVS. Typically you aren't sure why it exists you just know it does and have confirmed it. </dd> <dt>Suspended</dt> <dd> Usually used when there might be a fix in future and/or it relies on something external to be fixed first. </dd> <dt>Wont fix</dt> <dd>When something is not considered a bug or the bug is not fixable.</dd> <dt>No feedback</dt> <dd> If no answer have been given by the reporter after we've asked them something. Sometimes you will ask for an example script or ask the reporter to test using CVS or the latest snap. </dd> <dt>Feedback</dt> <dd> You're asking the reporter for more information such as please use CVS/snap, and/or the smallest possible test script to reproduce the error, and/or a value for a certain PHP directive. </dd> <dt>Bogus</dt> <dd> This bug is not a bug, support related or just an assumed bug. Be 100% it's really bogus and also be sure it's not a documentation bug. </dd> </dl> <h2>Reclassification</h2> <p>Sometimes you'll also want to reclassify a bug. For example, a reporter marks a bug as Apache2 related when really it's a MySQL bug. Just change the category but be 100% sure it's related to the new category. Another example would be changing the type to a documentation bug. If you're changing it to a documentation bug it will help the documentation team if you add specific information that is to be documented including what version the changes will take place.</p> <p>Also note that all bugs are sent to various mailing lists with php-bugs@lists.php.net being the default (most go here). Here's a list:</p> <dl> <dt>Default</dt> <dd><a href="http://news.php.net/group.php?group=php.bugs">php-bugs@lists.php.net</a></dd> <dt>Documentation</dt> <dd><a href="http://marc.theaimsgroup.com/?l=phpdoc">phpdoc@lists.php.net</a></dd> <dt>PEAR</dt> <dd><a href="http://marc.theaimsgroup.com/?l=pear-dev">pear-dev@lists.php.net</a></dd> <dt>PHP.net Website</dt> <dd><a href="http://news.php.net/group.php?group=php.mirrors">php-mirrors@lists.php.net</a></dd> </dl> <p>Reclassifying will immediatly change which mailing list is used. If you reclassify a bug and don't leave a comment then no email is sent to the mailing list. So, be sure to leave a comment.</p> <h2>Tips and links</h2> <ul> <li> The Jani Javascript bug popup window (right click to bookmark): <a href='javascript:void(t=prompt("Get BUG report # ..",""));if(t){ void(top.location.href="http://bugs.php.net/bug.php?edit=1&id="+t);}'>here</a> </li> <li> Look at the <a href="http://bugs.php.net/bugstats.php">raw bug stats</a> OR a <a href="http://www.php.net/~jani/bugs-graph.php">graph</a>. </li> <li> Not leaving a comment means no email will be sent to the mailing list. (all quickfix options leave comments) </li> <li> If a version involves CVS or a snapshot be sure to label it in the form: <b>4.x.y-dev</b> An example is: 4.3.0-dev. </li> <li> If you have a question either email the <a href="mailto:php-dev@lists.php.net">php-dev@lists.php.net</a> mailing list or check out the #php.bugs channel in IRC on <a href="http://www.irchelp.org/irchelp/networks/efnet.txt">EFNET</a>. </li> </ul> <h2>Conclusion</h2> <p>If everyone maintains the bug system in a consistent manner then PHP will be better for it. Also, bug reporters will not get their feelings hurt through miscommunication (e.g. a wrong quickfix or bogus status) Thank you for reading this HOWTO and helping make PHP better.</p> <br /> </td> <td width="10"> </td> </tr> </table> <?php common_footer(); ?> Index: qaweb/stats.php +++ qaweb/stats.php <?php include("include/functions.php"); $TITLE = "How To Help [PHP-QAT: Quality Assurance Team]"; $SITE_UPDATE = date("D M d H:i:s Y T", filectime($SCRIPT_FILENAME))."<br> /* $Id: stats.php,v 1.1 2003/01/18 22:33:14 derick Exp $ */"; common_header(); ?> <table width="70%" border="0" cellspacing="0" cellpadding="0"> <tr> <td width="10"><img src="gfx/spacer.gif" width="10" height="1"></td> <td width="100%"> <h1>Statistics</h1> </td> <td width="10"><img src="gfx/spacer.gif" width="10" height="1"></td> </tr> <tr> <td width="10"> </td> <td width="100%"><img src="http://www.php.net/~jani/count-<?php echo date ('Y-m'); ?>.png"><br /><br /> </td> <td width="10"> </td> </tr> </table> <?php common_footer(); ?>