j: Next unread message
k: Previous unread message
j a: Jump to all threads
j l: Jump to MailingList overview
On Mon, Jun 26, 2000 at 02:41:12PM -0400, Tim Peters wrote:
revision 1 26-Jun-2000
Open The initial status of all patches. The patch is under consideration, but has not been reviewed yet. The status will normally change to Accepted or Rejected next. The person submitting the patch should (if they can) assign it to the person they most want to review it. Else the patch will be assigned via [xxx a list of expertise areas should be developed]
What are the chances of getting other meta data fields on patches, i.e. changes to the patch manager? Categorizing patches could really help as a filter. For instance, I may be a Unicode genius and would like to see the patches associated with it.
Discussion of patches is carried out via [xxx Python-Dev? patches list? without a mail gateway, the SourceForge patch interface looks too clumsy to use for controversial patches]
I like the separation of python-dev and patches, but it is not a biggie for me.
Postponed The previous status was Open or Accepted, but for some reason (e.g., pending release) the patch should not be reviewed or applied until further notice. The status will normally change to Open or Accepted next. Please enter a comment when changing the status to Postponed, to record the reason, the previous status, and the conditions under which the patch should revert to Open or Accepted.
Perhaps ownership (i.e. 'assigned to') of the patch should transfer to the person responsible for later taking to patch out of 'postponed' status.
-- Trent Mick email@example.com