Ezio Melotti ezio.melo...@gmail.com added the comment:
The attached patch has been committed in 252e2aabc87a, and the wiki pages have
been updated to link to the devguide.
--
resolution: - fixed
stage: patch review - committed/rejected
status: open - closed
Changes by Eli Bendersky eli...@gmail.com:
--
nosy: -eli.bendersky
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue13455
___
___
Python-bugs-list
Changes by Ezio Melotti ezio.melo...@gmail.com:
--
stage: needs patch - patch review
type: - enhancement
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue13455
___
Terry J. Reedy tjre...@udel.edu added the comment:
Antoine, what reference other than the devguide are you referring to?
If you keep info I need out of the devguide, where am I supposed to find it?
python.org/dev now redirects to python.org/devguide.
--
Nick Coghlan ncogh...@gmail.com added the comment:
Something else such docs could cover is how to manage remote Hg repos such that
the Create Patch button does the right thing.
Basically, you need to make sure an appropriate CPython version is found in the
ancestors of the tip your working
Éric Araujo mer...@netwok.org added the comment:
[...] The devguide is *already* too big. [...]
The devguide was supposed to be something that you read quickly and easily,
not an exhaustive
reference of how development works. Or at least there should be a clear
separation between the
two
Éric Araujo mer...@netwok.org added the comment:
+1 on grouping existing info into one or two files in the devguide
+1 to removing the wiki pages
+1 on keeping some basic directions in the main docs
--
___
Python tracker rep...@bugs.python.org
Ezio Melotti ezio.melo...@gmail.com added the comment:
I think the reason these docs are scattered is that the devguide is a
guide, not a reference manual. I don't think this patch makes sense: if
the tracker really needed so much text to explain how it works, then
the tracker would have
Antoine Pitrou pit...@free.fr added the comment:
This is true, however different people can figure out a different
amount of things just by using and experiment with something. While
most of the tasks should be obvious, some are a bit more advanced, and
even the obvious once might not be
Ezio Melotti ezio.melo...@gmail.com added the comment:
Well, it does hurt, because the more sentences you write, the more the
devguide becomes bloated and difficult to follow
OTOH is easy to ignore an how to register to the tracker section if you are
already registered or if you don't need
New submission from Ezio Melotti ezio.melo...@gmail.com:
The documentation about the bug tracker is sparse in a few different places.
The devguide contains 4 pages:
1. http://docs.python.org/devguide/helptriage.html
2. http://docs.python.org/devguide/devrole.html
3.
Antoine Pitrou pit...@free.fr added the comment:
I think the reason these docs are scattered is that the devguide is a guide,
not a reference manual. I don't think this patch makes sense: if the tracker
really needed so much text to explain how it works, then the tracker would have
a severe
Petri Lehtinen pe...@digip.org added the comment:
It seems to me there's not that much text on how the tracker itself works. Only
sections Checking if a bug already exists and Reporting an issue have this
kind of information. The text in these sections seems to be mostly from
Nick Coghlan ncogh...@gmail.com added the comment:
Documenting the tracker UI itself isn't the big issue - what is useful (and
what I think Ezio is getting at) is having a single place where newcomers can
get a better idea of how we *use* the tracker.
If someone just wants to report a bug,
14 matches
Mail list logo
