On Sun, Mar 16, 2008 at 11:37 AM, Guido van Rossum <
guido@python.org> wrote:
On Sun, Mar 16, 2008 at 11:19 AM, Benjamin Peterson
<
musiccomposition@gmail.com> wrote:
> I don't like the idea of task like items in the main bug tracker.
the same way. It might be convenient to have everything in one
tracker. What's your objection? It should be easy enough to search for
tasks or bugs etc.
It's just depends on how you see the tracker. It's not just to "bug" tracker anymore, is it? On other projects I've worked with, we had separate areas for bugs, features, and tasks. (yes, it's SourceForge.) I found it easier to keep organized. However, if this is Python's way, I'm not going to stand in it.
> I do, however, like the bug tracker interface for this sort of thing. Could we
> start a new instance of the the tracker just for internal development tasks?
I'm not sure how easy it would be to start a new instance, but I
expect setting up the database, configuration etc. would require a
fairly significant amount of work. I'd much rather use existing
infrastructure.
I'm now fine with that.
> We could change the statuses around to "Work in progress", "Completed",
> "Incomplete", and such. It'd be easy to search for tasks that have to be
> accomplished for a given release.
That would be good for bugs too, actually.
Well, I'm glad to help somehow! :P
--