[pygr-notify] [pygr commit] r172 - Edited wiki page through web user interface.

[codesite-noreply at google.com]

Author: marecki
Date: Tue Apr  7 18:47:46 2009
New Revision: 172

Modified:
    wiki/IssueProcessing.wiki

Log:
Edited wiki page through web user interface.

Modified: wiki/IssueProcessing.wiki
==============================================================================
--- wiki/IssueProcessing.wiki	(original)
+++ wiki/IssueProcessing.wiki	Tue Apr  7 18:47:46 2009
@@ -34,9 +34,13 @@
  The *reviewer* of an issue is a person expected to validate fixes provided  
for that issue by the owner. By default this will be the person who  
reported the issue; however, keep in mind the reviewer and the owner of an  
issue must *NOT* be the same person. The reviewer is indicated using labels  
("reviewby-_name_") as well as by being the first on the "Cc" list.


-== Filing ==
+== Filing and Assigning ==

-TBA
+A newly-filed issue should normally have the status *New*. A possible  
exception to this rule involves issues reported by developers in the course  
of their work (i.e. when one is 100% certain they are valid), in which case  
one can file as *Accepted* or, when the person in question is already  
working on the fix, *Assigned*.
+
+Open issues without owners, i.e. all *New* and *Accepted* ones, should  
have their respective owner field set to  
_pygr-bug-wranglers at googlegroups.com_, a mailing list of people responsible  
for managing issues, thus letting them know an issue has appeared which  
needs an owner.
+
+TBC


  == Submission of Fixes ==
@@ -54,6 +58,6 @@
  Issues tagged *ReviewedNeedsCommit* should be closed as soon as the  
relevant changes have made their way into the Git repository, by the person  
who performed the commit.


-== Closing ==
+== Miscellaneous ==

-TBA
\ No newline at end of file
+Any situations not discussed here will be resolved by project managers on  
the basis of communication with involved parties and, above all, common  
sense.
\ No newline at end of file