coar 98/08/07 02:16:51
Modified: . bugdb-policies.html Log: Downsize the typeface inside the tables for better readability and printability. Reviewed by: Ralf Engelschall Revision Changes Path 1.2 +159 -143 apache-devsite/bugdb-policies.html Index: bugdb-policies.html =================================================================== RCS file: /export/home/cvs/apache-devsite/bugdb-policies.html,v retrieving revision 1.1 retrieving revision 1.2 diff -u -r1.1 -r1.2 --- bugdb-policies.html 1998/08/03 14:48:27 1.1 +++ bugdb-policies.html 1998/08/07 09:16:49 1.2 @@ -4,6 +4,11 @@ <HEAD> <TITLE>Apache Bug Database Policies for Developers </TITLE> + <STYLE TYPE="text/css"> + <!-- + TD { font-size: smaller } + --> + </STYLE> </HEAD> <!-- Background white, links blue (unvisited), navy (visited), red (active) --> <BODY @@ -151,148 +156,159 @@ state should be for a PR you're handling, consult the table for some guidelines. </P> - <TABLE BORDER=1> - <TR VALIGN=BOTTOM ALIGN=CENTER> - <TD></TD> - <TH>open</TH> - <TH>analyzed</TH> - <TH>feedback</TH> - <TH>suspended</TH> - <TH>closed</TH> - </TR> - <TR VALIGN=TOP> - <TH VALIGN=CENTER>open</TH> - <TD><!-- open-open --> - </TD> - <TD><!-- open-analyzed --> - Either the submitter or a responding developer has determined what the - problem cause is. - </TD> - <TD><!-- open-feedback --> - A question has been posed to the submitter, such as asking for more - detail or requesting an experiment. - </TD> - <TD><!-- open-suspended --> - The PR describes a request for a change or functionality that is - reasonable or interesting, but isn't appropriate to the current - version under development, or to the current plans or work effort - available. - </TD> - <TD><!-- open-closed --> - The PR deals with a non-issue, one that has already been solved, or is - already being tracked. Or almost any case in which further attention - is inappropriate. - </TD> - </TR> - <TR VALIGN=TOP> - <TH VALIGN=CENTER>analyzed</TH> - <TD><!-- analyzed-open --> - It turns out that the analysis was incorrect and the cause really isn't - known after all. - </TD> - <TD><!-- analyzed-analyzed --> - </TD> - <TD><!-- analyzed-feedback --> - The submitter is being asked for more information or experimentation. - </TD> - <TD><!-- analyzed-suspended --> - The issue described by the PR should be deferred until some later version. - </TD> - <TD><!-- analyzed-closed --> - The decision has been made to <STRONG>not</STRONG> address the PR, - possibly because the behaviour is not considered a bug. This usually - follows discussion amongst the developers. - </TD> - </TR> - <TR VALIGN=TOP> - <TH VALIGN=CENTER>feedback</TH> - <TD><!-- feedback-open --> - The requested information has been supplied by the submitter, but - doesn't really explain the behaviour. (It may be more appropriate to - move the PR to "analyzed" instead.) - </TD> - <TD><!-- feedback-analyzed --> - The response from the submitter has provided the necessary information - to determine the cause, if not the solution, of the issue. - </TD> - <TD><!-- feedback-feedback --> - </TD> - <TD><!-- feedback-suspended --> - Additional information from the submitter allows the determination to - be made that the issue should be addressed in some future version. - </TD> - <TD><!-- feedback-closed --> - <MENU> - <LI>Additional information supplied by the submitter has explained the - cause, and the solution is provided in the closure text. - </LI> - <LI>The PR has '<A HREF="#dates">timed out</A>' due to lack of response - from the submitter. - </LI> - </MENU> - </TD> - </TR> - <TR VALIGN=TOP> - <TH VALIGN=CENTER>suspended</TH> - <TD><!-- suspended-open --> - <MENU> - <LI>The time has come for the issue described by the PR to be considered - for inclusion in the project. - </LI> - <LI>The PR describes a genuine bug rather than a change or enhancement. - It may be more appropriate to move the PR to "analyzed" instead. - </LI> - </MENU> - </TD> - <TD><!-- suspended-analyzed --> - <MENU> - <LI>The time has come for the issue described by the PR to be considered - for inclusion in the project. - </LI> - <LI>The issue described by the PR is a genuine bug or problem, and the - circumstances are tolerably well understood. - </LI> - </MENU> - </TD> - <TD><!-- suspended-feedback --> - The PR's issue wasn't clearly understood, and it really is a bug - report. More information from the submitter has been requested. - (This typically follows <A HREF="#outofband">out-of-band email</A> - exchanges between the submitter and a developer.) - </TD> - <TD><!-- suspended-suspended --> - </TD> - <TD><!-- suspended-closed --> - The issue was discussed by the developers, and the decision was made - to not invest in the necessary effort. The PR submitter can, and perhaps - should, be encouraged to develop the solution personally and supply it - to the project for possible inclusion. - </TD> - </TR> - <TR VALIGN=TOP> - <TH VALIGN=CENTER>closed</TH> - <TD><!-- closed-open --> - The report was closed prematurely, probably due to insufficient detail - in the PR or perhaps because the developer didn't understand the - issue as described. It may be more appropriate for the PR to have - been moved to "analyzed" or "feedback" instead. - </TD> - <TD><!-- closed-analyzed --> - The PR was closed prematurely, but the issue is now clarified and - understood -- though not yet solved. - </TD> - <TD><!-- closed-feedback --> - The PR was closed prematurely, but additional information has been - requested from the submitter to investigate further. - </TD> - <TD><!-- closed-suspended --> - After closure, additional information has been supplied to make a case for - future consideration of the issue. - </TD> - <TD><!-- closed-closed --> - </TD> - </TR> - </TABLE> + <DIV ALIGN=CENTER> + <TABLE BORDER=1 WIDTH="95%"> + <TR VALIGN=BOTTOM ALIGN=CENTER> + <TD></TD> + <TH>open</TH> + <TH>analyzed</TH> + <TH>feedback</TH> + <TH>suspended</TH> + <TH>closed</TH> + </TR> + <TR VALIGN=TOP> + <TH VALIGN=CENTER>open</TH> + <TD><!-- open-open --> + </TD> + <TD><!-- open-analyzed --> + Either the submitter or a responding developer has determined what the + problem cause is. + </TD> + <TD><!-- open-feedback --> + A question has been posed to the submitter, such as asking for more + detail or requesting an experiment. + </TD> + <TD><!-- open-suspended --> + The PR describes a request for a change or functionality that is + reasonable or interesting, but isn't appropriate to the current + version under development, or to the current plans or work effort + available. + </TD> + <TD><!-- open-closed --> + The PR deals with a non-issue, one that has already been solved, or is + already being tracked. Or almost any case in which further attention + is inappropriate. + </TD> + </TR> + <TR VALIGN=TOP> + <TH VALIGN=CENTER>analyzed</TH> + <TD><!-- analyzed-open --> + It turns out that the analysis was incorrect and the cause really isn't + known after all. + </TD> + <TD><!-- analyzed-analyzed --> + </TD> + <TD><!-- analyzed-feedback --> + The submitter is being asked for more information or experimentation. + </TD> + <TD><!-- analyzed-suspended --> + The issue described by the PR should be deferred until some later + version. + </TD> + <TD><!-- analyzed-closed --> + <MENU> + <LI>A fix for the problem has been committed to the development stream. + </LI> + <LI> + The decision has been made to <STRONG>not</STRONG> address the PR, + possibly because the behaviour is not considered a bug. This usually + follows discussion amongst the developers. + </LI> + </MENU> + </TD> + </TR> + <TR VALIGN=TOP> + <TH VALIGN=CENTER>feedback</TH> + <TD><!-- feedback-open --> + The requested information has been supplied by the submitter, but + doesn't really explain the behaviour. (It may be more appropriate to + move the PR to "analyzed" instead.) + </TD> + <TD><!-- feedback-analyzed --> + The response from the submitter has provided the necessary information + to determine the cause, if not the solution, of the issue. + </TD> + <TD><!-- feedback-feedback --> + </TD> + <TD><!-- feedback-suspended --> + Additional information from the submitter allows the determination to + be made that the issue should be addressed in some future version. + </TD> + <TD><!-- feedback-closed --> + <MENU> + <LI>A fix for the problem has been committed to the development stream. + </LI> + <LI>Additional information supplied by the submitter has explained the + cause, and the solution is provided in the closure text. + </LI> + <LI>The PR has '<A HREF="#dates">timed out</A>' due to lack of response + from the submitter. + </LI> + </MENU> + </TD> + </TR> + <TR VALIGN=TOP> + <TH VALIGN=CENTER>suspended</TH> + <TD><!-- suspended-open --> + <MENU> + <LI>The time has come for the issue described by the PR to be considered + for inclusion in the project. + </LI> + <LI>The PR describes a genuine bug rather than a change or enhancement. + It may be more appropriate to move the PR to "analyzed" instead. + </LI> + </MENU> + </TD> + <TD><!-- suspended-analyzed --> + <MENU> + <LI>The time has come for the issue described by the PR to be considered + for inclusion in the project. + </LI> + <LI>The issue described by the PR is a genuine bug or problem, and the + circumstances are tolerably well understood. + </LI> + </MENU> + </TD> + <TD><!-- suspended-feedback --> + The PR's issue wasn't clearly understood, and it really is a bug + report. More information from the submitter has been requested. + (This typically follows <A HREF="#outofband">out-of-band email</A> + exchanges between the submitter and a developer.) + </TD> + <TD><!-- suspended-suspended --> + </TD> + <TD><!-- suspended-closed --> + The issue was discussed by the developers, and the decision was made + to not invest in the necessary effort. The PR submitter can, and perhaps + should, be encouraged to develop the solution personally and supply it + to the project for possible inclusion. + </TD> + </TR> + <TR VALIGN=TOP> + <TH VALIGN=CENTER>closed</TH> + <TD><!-- closed-open --> + The report was closed prematurely, probably due to insufficient detail + in the PR or perhaps because the developer didn't understand the + issue as described. It may be more appropriate for the PR to have + been moved to "analyzed" or "feedback" instead. + </TD> + <TD><!-- closed-analyzed --> + The PR was closed prematurely, but the issue is now clarified and + understood -- though not yet solved. + </TD> + <TD><!-- closed-feedback --> + The PR was closed prematurely, but additional information has been + requested from the submitter to investigate further. + </TD> + <TD><!-- closed-suspended --> + After closure, additional information has been supplied to make a case + for future consideration of the issue. + </TD> + <TD><!-- closed-closed --> + </TD> + </TR> + </TABLE> + </DIV> <HR> <H2><A NAME="dates">Date Thresholds</A> </H2> @@ -302,7 +318,7 @@ for dealing with PRs that aren't being actively worked. </P> <DIV ALIGN=CENTER> - <TABLE BORDER=1> + <TABLE BORDER=1 WIDTH="95%"> <TR> <TH>State</TH> <TH>Time Since Last Touched</TH>