[Python-Dev] OS information, tags

[Anand Balachandran Pillai]

On Tue, Apr 13, 2010 at 6:24 PM, Nick Coghlan <ncoghlan at gmail.com> wrote:

> Senthil Kumaran wrote:
> > On Mon, Apr 12, 2010 at 07:06:29PM +0530, Anand Balachandran Pillai
> wrote:
> >>            I am surprised to see that the bug-tracker
> >> doesn't have an OS classifier or ability to add
> >> tags ? Since a number of issues reported seem to
> >
> > There is one. In the Components you can do a multiple select and it
> > has Macintosh , Windows as options.
>

 Thanks for pointing that out. I missed it.

 A problem seems to be that for most bugs, the filer seems to select
 just one component and leave the rest of it to bug description. When
 I searched with "Windows" component, the most recent bugs I saw
 was upto 1 week ago, where as a bug like http://bugs.python.org/issue8384
 which is a distutils issue reported on Windows is not present, because
 the reporter chose to file it under "distutils" component.


>
> I think that setup dates from the Sourceforge days when we didn't have
> keywords or the ability to add our own fields. Would it make sense to
> put a request on the metatracker to convert these to keywords now that
> they're available? Or even a separate OS field with "Windows, Mac OS X,
> Linux, *BSD, Other" as the options?
>
> While there is some Windows and Mac specific code, treating them as
> separate components seems fairly unintuitive.
>

 +1. I don't understand why Windows and Mac should come under
 "Components". It is not very obvious to the reporters also.

 Separate question: Who is in charge of bug triaging in pydev ? This is
something which I would like to help out with, if help is required :-)


>
> Cheers,
> Nick.
>
> --
> Nick Coghlan   |   ncoghlan at gmail.com   |   Brisbane, Australia
> ---------------------------------------------------------------
>



-- 
--Anand
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/python-dev/attachments/20100413/cc3cbea8/attachment-0001.html>