Wiki is the best place for community knowledge and best practices as
it doesn't require neither commit privileges, nor familiarity with
editing process (which in case of docs.python.org is not trivial).

It seems that there are different documentation pages in different places:
 * http://docs.python.org/dev/py3k/bugs.html
 * http://wiki.python.org/moin/SubmittingBugs
 * http://wiki.python.org/moin/TrackerDocs/
 * http://www.python.org/dev/workflow/

There's some overlapping and the contents are not up to date. If we figure out a place where this documentation should be (docs.python.org would be better), we could merge these documents and update them.

Note from the Py3K sprint: Anna Ravenscroft is updating the bugs.rst file in the
Py3K source tree (under Doc) to match the document currently in the moin. In the
end we should decide where we want to maintain the thing.

I did no testing, just was revisiting the tracker status and found that
things started moving, while documentation was incomplete for the launch,
and thought that mentioning the recent change can help ensure that
documentation is up-to-date in regard to data migration procedure.

Reagrds,

m.

On 7/25/07, Erik Forsberg <metatracker@psf.upfronthosting.co.za> wrote:
>
>
> Erik Forsberg added the comment:
>
> Hopefully, the new importer produces the same result as the old one, so
> there should be no need for documentation updates.
>
> Feel free to prove me wrong, especially if your proving includes
> rigorous testing and comparisons of the data in sourceforge's tracker,
> and the data on http://bugs.python.org :-).
>
> Regards,
> \EF
>
> ----------
> nosy:  -forsberg
> status: unread -> chatting
>
> _______________________________________________________
> Meta Tracker <metatracker@psf.upfronthosting.co.za>
> <http://psf.upfronthosting.co.za/roundup/meta/issue119>
> _______________________________________________________
>

Hopefully, the new importer produces the same result as the old one, so 
there should be no need for documentation updates.

Feel free to prove me wrong, especially if your proving includes 
rigorous testing and comparisons of the data in sourceforge's tracker, 
and the data on http://bugs.python.org :-).

Regards,
\EF

Tracker Documentation (http://wiki.python.org/moin/TrackerDocs/) linked on
bugs.python.org sidebar should be updated before launch. It should include valid
"Getting a Developer account under Roundup" section. And due to recent importer
update (#110), there is a chance that "About Differences between SF and Roundup"
and "Fields" sections need an update as well, thus adding Eric, to nosy list...