Menu
▾
▴
[phpBT-dev] CVS: phpbt/docs/html adminguide.html,1.14,1.15 bugdetail.html,1.3,1.4 bugsearch.html,1.5,1.6 configuration.html,1.14,1.15 devguide.html,1.20,1.21 devstandards.html,1.21,1.22 schema.html,1.6,1.7 userguide.html,1.11,1.12
Update of /cvsroot/phpbt/phpbt/docs/html In directory usw-pr-cvs1:/tmp/cvs-serv5694/html Modified Files: adminguide.html bugdetail.html bugsearch.html configuration.html devguide.html devstandards.html schema.html userguide.html Log Message: Updated for 0.8.0 Index: adminguide.html =================================================================== RCS file: /cvsroot/phpbt/phpbt/docs/html/adminguide.html,v retrieving revision 1.14 retrieving revision 1.15 diff -u -r1.14 -r1.15 --- adminguide.html 5 Apr 2002 19:06:07 -0000 1.14 +++ adminguide.html 8 Apr 2002 15:05:09 -0000 1.15 @@ -102,7 +102,7 @@ ><DIV CLASS="ABSTRACT" ><A -NAME="AEN119"><P +NAME="AEN108"><P >One of the main design goals of phpBugTracker is to make installation and administration easy. In fact, the difficulty of installing bugzilla was a key motivator for phpBugTracker's existence.</P ></DIV ></BLOCKQUOTE Index: bugdetail.html =================================================================== RCS file: /cvsroot/phpbt/phpbt/docs/html/bugdetail.html,v retrieving revision 1.3 retrieving revision 1.4 diff -u -r1.3 -r1.4 --- bugdetail.html 28 Feb 2002 18:55:43 -0000 1.3 +++ bugdetail.html 8 Apr 2002 15:05:09 -0000 1.4 @@ -83,7 +83,7 @@ CLASS="MEDIAOBJECT" ><P ><IMG -SRC="images/shots/user/bugdetail.png"><DIV +SRC="images/shots/user/bugdetail.jpg"><DIV CLASS="CAPTION" ><P >Editing a bug.</P @@ -92,14 +92,6 @@ ></DIV ><P >When changes are made to a bug, an email is sent to the person who reported it and to the person to whom the bug is assigned. However, email is not sent to the person who is making the changes to the bug. So, if a bug has been submitted and assigned to a developer, and then the developer adds comments to the bug, then those comments will be emailed to the reporter but not to the developer. Additional people can be added to receive these change emails by adding them to the CC list. To remove people from the CC list, simply select the people to be removed and submit the form.</P -><P ->The set of radio buttons beneath the <SPAN -CLASS="GUILABEL" ->Update Bug Status</SPAN -> label changes depending on the status of the bug. The bug in the screen shot is one that has been newly submitted, so it is unassigned at the moment. If a developer looking at this bug wanted to take ownership, she would click <SPAN -CLASS="GUILABEL" ->Accept bug</SPAN -> and then submit the form. If a bug is resolved as a duplicate of another bug (e.g, bug #77), it will be closed and a comment will be added to this bug and to bug #77 noting that this bug is a duplicate of that one. If there is a developer assigned to be the owner of this component (in this case, "name test"), then the bug can be assigned to that individual by clicking the last radio button.</P ><P >Files can be added to a bug as attachments by clicking on the <SPAN CLASS="GUILABEL" Index: bugsearch.html =================================================================== RCS file: /cvsroot/phpbt/phpbt/docs/html/bugsearch.html,v retrieving revision 1.5 retrieving revision 1.6 diff -u -r1.5 -r1.6 --- bugsearch.html 5 Apr 2002 19:06:08 -0000 1.5 +++ bugsearch.html 8 Apr 2002 15:05:10 -0000 1.6 @@ -78,12 +78,12 @@ ><A NAME="BUGSEARCH">1.2. Searching the Bug Database</H1 ><P ->The query page presents a wide array of options for finding a specific set of bugs, and thus can be a little overwhelming at first sight. By submitting the default form, without selecting any options, a list of all the bugs in the database will be returned. Every option selected will filter out more bugs as you get more specific in your search.</P +>There are two versions of the bug query page. The default version is the simple form, which allows you to restrict your search by project and bug status. The advanced query page presents a wide array of options for finding a specific set of bugs, and thus can be a little overwhelming at first sight. By submitting the default form, without selecting any options, a list of all the bugs in the database will be returned. Every option selected will filter out more bugs as you get more specific in your search.</P ><DIV CLASS="MEDIAOBJECT" ><P ><IMG -SRC="images/shots/user/query.png"><DIV +SRC="images/shots/user/query.jpg"><DIV CLASS="CAPTION" ><P >Searching for bugs.</P Index: configuration.html =================================================================== RCS file: /cvsroot/phpbt/phpbt/docs/html/configuration.html,v retrieving revision 1.14 retrieving revision 1.15 diff -u -r1.14 -r1.15 --- configuration.html 5 Apr 2002 19:06:08 -0000 1.14 +++ configuration.html 8 Apr 2002 15:05:10 -0000 1.15 @@ -82,7 +82,7 @@ ><DIV CLASS="ABSTRACT" ><A -NAME="AEN150"><P +NAME="AEN139"><P >Most of the options listed here can be configured via the Configuration page of the admin tools. The <TT CLASS="VARNAME" >DB_</TT Index: devguide.html =================================================================== RCS file: /cvsroot/phpbt/phpbt/docs/html/devguide.html,v retrieving revision 1.20 retrieving revision 1.21 diff -u -r1.20 -r1.21 --- devguide.html 5 Apr 2002 19:06:08 -0000 1.20 +++ devguide.html 8 Apr 2002 15:05:10 -0000 1.21 @@ -116,7 +116,7 @@ ><DIV CLASS="ABSTRACT" ><A -NAME="AEN297"><P +NAME="AEN286"><P >Adding on to or extending phpBugTracker should be easy for those with a knowledge of PHP and SQL. New developers are always welcome to join the project at <A HREF="http://www.sourceforge.net/projects/phpbt/" TARGET="_top" Index: devstandards.html =================================================================== RCS file: /cvsroot/phpbt/phpbt/docs/html/devstandards.html,v retrieving revision 1.21 retrieving revision 1.22 diff -u -r1.21 -r1.22 --- devstandards.html 5 Apr 2002 19:06:08 -0000 1.21 +++ devstandards.html 8 Apr 2002 15:05:10 -0000 1.22 @@ -82,7 +82,7 @@ ><DIV CLASS="ABSTRACT" ><A -NAME="AEN377"><P +NAME="AEN366"><P > This section details the coding and process standards to be followed by the developers working on phpBugTracker. </P Index: schema.html =================================================================== RCS file: /cvsroot/phpbt/phpbt/docs/html/schema.html,v retrieving revision 1.6 retrieving revision 1.7 diff -u -r1.6 -r1.7 --- schema.html 5 Apr 2002 19:06:08 -0000 1.6 +++ schema.html 8 Apr 2002 15:05:10 -0000 1.7 @@ -73,7 +73,7 @@ ><DIV CLASS="TABLE" ><A -NAME="AEN435"><P +NAME="AEN424"><P ><B >Table 3-1. Schema for table attachment</B ></P @@ -251,7 +251,7 @@ ><DIV CLASS="TABLE" ><A -NAME="AEN485"><P +NAME="AEN474"><P ><B >Table 3-2. Schema for table auth_group</B ></P @@ -413,7 +413,7 @@ ><DIV CLASS="TABLE" ><A -NAME="AEN531"><P +NAME="AEN520"><P ><B >Table 3-3. Schema for table auth_perm</B ></P @@ -560,7 +560,7 @@ ><DIV CLASS="TABLE" ><A -NAME="AEN573"><P +NAME="AEN562"><P ><B >Table 3-4. Schema for table auth_user</B ></P @@ -810,7 +810,7 @@ ><DIV CLASS="TABLE" ><A -NAME="AEN643"><P +NAME="AEN632"><P ><B >Table 3-5. Schema for table bug</B ></P @@ -1195,7 +1195,7 @@ ><DIV CLASS="TABLE" ><A -NAME="AEN751"><P +NAME="AEN740"><P ><B >Table 3-6. Schema for table bug_cc</B ></P @@ -1301,7 +1301,7 @@ ><DIV CLASS="TABLE" ><A -NAME="AEN781"><P +NAME="AEN770"><P ><B >Table 3-7. Schema for table bug_dependency</B ></P @@ -1371,7 +1371,7 @@ ><DIV CLASS="TABLE" ><A -NAME="AEN801"><P +NAME="AEN790"><P ><B >Table 3-8. Schema for table bug_group</B ></P @@ -1443,7 +1443,7 @@ ><DIV CLASS="TABLE" ><A -NAME="AEN822"><P +NAME="AEN811"><P ><B >Table 3-9. Schema for table bug_vote</B ></P @@ -1531,7 +1531,7 @@ ><DIV CLASS="TABLE" ><A -NAME="AEN847"><P +NAME="AEN836"><P ><B >Table 3-10. Schema for table bug_history</B ></P @@ -1673,7 +1673,7 @@ ><DIV CLASS="TABLE" ><A -NAME="AEN887"><P +NAME="AEN876"><P ><B >Table 3-11. Schema for table comment</B ></P @@ -1797,7 +1797,7 @@ ><DIV CLASS="TABLE" ><A -NAME="AEN922"><P +NAME="AEN911"><P ><B >Table 3-12. Schema for table component</B ></P @@ -2014,7 +2014,7 @@ ><DIV CLASS="TABLE" ><A -NAME="AEN983"><P +NAME="AEN972"><P ><B >Table 3-13. Schema for table configuration</B ></P @@ -2122,7 +2122,7 @@ ><DIV CLASS="TABLE" ><A -NAME="AEN1014"><P +NAME="AEN1003"><P ><B >Table 3-14. Schema for table group_perm</B ></P @@ -2192,7 +2192,7 @@ ><DIV CLASS="TABLE" ><A -NAME="AEN1034"><P +NAME="AEN1023"><P ><B >Table 3-15. Schema for table os</B ></P @@ -2298,7 +2298,7 @@ ><DIV CLASS="TABLE" ><A -NAME="AEN1064"><P +NAME="AEN1053"><P ><B >Table 3-16. Schema for table project</B ></P @@ -2476,7 +2476,7 @@ ><DIV CLASS="TABLE" ><A -NAME="AEN1114"><P +NAME="AEN1103"><P ><B >Table 3-17. Schema for table project_group</B ></P @@ -2582,7 +2582,7 @@ ><DIV CLASS="TABLE" ><A -NAME="AEN1144"><P +NAME="AEN1133"><P ><B >Table 3-18. Schema for table resolution</B ></P @@ -2688,7 +2688,7 @@ ><DIV CLASS="TABLE" ><A -NAME="AEN1174"><P +NAME="AEN1163"><P ><B >Table 3-19. Schema for table saved_query</B ></P @@ -2799,7 +2799,7 @@ ><DIV CLASS="TABLE" ><A -NAME="AEN1206"><P +NAME="AEN1195"><P ><B >Table 3-20. Schema for table severity</B ></P @@ -2926,7 +2926,7 @@ ><DIV CLASS="TABLE" ><A -NAME="AEN1242"><P +NAME="AEN1231"><P ><B >Table 3-21. Schema for table status</B ></P @@ -3032,7 +3032,7 @@ ><DIV CLASS="TABLE" ><A -NAME="AEN1272"><P +NAME="AEN1261"><P ><B >Table 3-22. Schema for table user_group</B ></P @@ -3138,7 +3138,7 @@ ><DIV CLASS="TABLE" ><A -NAME="AEN1302"><P +NAME="AEN1291"><P ><B >Table 3-23. Schema for table user_perm</B ></P @@ -3208,7 +3208,7 @@ ><DIV CLASS="TABLE" ><A -NAME="AEN1322"><P +NAME="AEN1311"><P ><B >Table 3-24. Schema for table user_pref</B ></P @@ -3278,7 +3278,7 @@ ><DIV CLASS="TABLE" ><A -NAME="AEN1342"><P +NAME="AEN1331"><P ><B >Table 3-25. Schema for table version</B ></P Index: userguide.html =================================================================== RCS file: /cvsroot/phpbt/phpbt/docs/html/userguide.html,v retrieving revision 1.11 retrieving revision 1.12 diff -u -r1.11 -r1.12 --- userguide.html 28 Feb 2002 18:55:44 -0000 1.11 +++ userguide.html 8 Apr 2002 15:05:10 -0000 1.12 @@ -137,7 +137,7 @@ CLASS="bold" ><B CLASS="EMPHASIS" ->Open a new account</B +>Create a new account</B ></SPAN >. To create a new account you will need to enter at least a valid email address (so that your password can be mailed to you). Providing your name is optional, but if you submit it then your name will appear with bugs you submit and comments you make. If the system has been configured to use a login separate from the email address, you will also be prompted for a login. If you have chosen an email address (or login) that is already in use, you will be prompted to choose a different one. After completing this form, your password will be mailed to you. Once you have received your password you can then login with your email (or login) and password to be able to submit bugs.</P ></DIV @@ -152,14 +152,14 @@ CLASS="bold" ><B CLASS="EMPHASIS" ->Enter Bug</B +>Add a New Bug</B ></SPAN > link from the top navigation bar to create a new bug. If there is more than one project for which you can submit a bug, you will be prompted to choose one.</P ><DIV CLASS="MEDIAOBJECT" ><P ><IMG -SRC="images/shots/user/enterbug-chooseproject.png"><DIV +SRC="images/shots/user/enterbug-chooseproject.jpg"><DIV CLASS="CAPTION" ><P >Selecting a project for a bug report.</P @@ -208,7 +208,7 @@ CLASS="MEDIAOBJECT" ><P ><IMG -SRC="images/shots/user/enterbug-detail.png"><DIV +SRC="images/shots/user/enterbug-detail.jpg"><DIV CLASS="CAPTION" ><P >Entering a bug report.</P |
