This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author skip.montanaro
Recipients loewis, skip.montanaro
Date 2007-09-28.16:33:17
SpamBayes Score 0.22858521
Marked as misclassified No
Message-id <18173.11465.582035.967638@montanaro.dyndns.org>
In-reply-to <1190954269.32.0.388843147486.issue1218@psf.upfronthosting.co.za>
Content
Martin> Website issues are not tracked in this tracker. See
    Martin> http://wiki.python.org/moin/PythonWebsiteCreatingNewTickets

Is there some reason at this point that we need to maintain two separate
trackers?  A ton of work went into making our Roundup instance what the key
players wanted.  Why not use it to track website issues as well?  With them
separate you have two communities of maintainers and triage folks who are
mostly disjoint.

I assume there would be some trac-to-roundup conversion necessary.  Perhaps
something like that already exists.

Skip
History
Date User Action Args
2007-09-28 16:33:18skip.montanarosetspambayes_score: 0.228585 -> 0.22858521
recipients: + skip.montanaro, loewis
2007-09-28 16:33:17skip.montanarolinkissue1218 messages
2007-09-28 16:33:17skip.montanarocreate