On Tue, Mar 10, 2009 at 12:34 AM, Tennessee Leeuwenburg <tleeuwenb...@gmail.com> wrote: > .. I'm not sure what's best: > * Post the review as a comment on the associated issue. Only nosies will > be updated.
You should always do that. If you feel that the nosy list is too small and you want to raise awareness for the issue, you can either CC the list or post a note with a link to the issue. Please keep in mind that tracker summaries are posted on this list every week and updated issues move to the top of the default tracker view, so just posting a new comment will already give it additional visibility. > * Post the review as a comment on the issue, then post a one-line > information update to this list All comments should be posted to the tracker. Comments summarizing long tracker discussions and proposing a resolution may be appropriate for a python-dev post, but if you do that, please reference the list thread on the tracker as it develops here. > * Post the review to this list for consideration Please do this only after a tracker update. This way your review will not be lost. _______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
