Opened 10 years ago

Closed 10 years ago

#3491 closed enhancement (invalid)

Create fields for GCC version, kernel-version, and hardware type

Reported by: mmadia Owned by: haiku-web
Priority: normal Milestone: R1
Component: Website/Trac Version: R1/pre-alpha1
Keywords: Cc:
Blocked By: Blocking:
Has a Patch: no Platform: All

Description

Trac's Create New Ticket form should include additional fields/forms to allow a user to : -select gcc version (GCC 2, GCC 4, GCC 2+4, GCC 4+2) -input kernel-version (aka uname -v) -hardware type (real, virtualized:[qemu, ...,])

These additional fields should help organize bug reports.

Change History (7)

comment:1 Changed 10 years ago by nielx

I understand that having that kind of information is useful at times, I think that in reality it will only add complexity to the ticket system, which is something we should avoid for developers and users. I can think of only a limited number of cases where the GCC version and the kernel version are truly relevant.

As for the hardware type. It would be possible to add platforms to the platform dropdown, but again, I feel that there might be a limited use.

Perhaps instead we should add a line with 'keywords' in which we can add things like 'gcc2-only' or 'qemu'.

comment:2 Changed 10 years ago by anevilyak

Actually, I would disagree there: I can think of quite a few bugs of varying severity that only show up on gcc4 builds, so it would be quite helpful to be able to filter the bugs by applicable compiler, though the keywords mechanism you mentioned would probably do the trick there ; however, that somewhat relies on people being uniform in their keyword usage to be truly helpful when trying to categorize.

comment:3 in reply to:  2 Changed 10 years ago by nielx

Replying to anevilyak:

Actually, I would disagree there: I can think of quite a few bugs of varying severity that only show up on gcc4 builds, so it would be quite helpful to be able to filter the bugs by applicable compiler, though the keywords mechanism you mentioned would probably do the trick there ; however, that somewhat relies on people being uniform in their keyword usage to be truly helpful when trying to categorize.

The advantage with the keyword approach is that when you query for gcc4, you are certain that you will find gcc4 related bugs, and not all the bugs that happen to be reported on a gcc4 compiled image.

We can make keyword handling uniform by creating a list of accepted keywords and maintaining these.

comment:4 Changed 10 years ago by mmadia

Any thoughts on this before closing?

comment:5 Changed 10 years ago by axeld

I'm with Niels on this one.

comment:6 in reply to:  5 Changed 10 years ago by leavengood

Replying to axeld:

I'm with Niels on this one.

Me too, as long as we can maintain that list of keywords properly and have consistency.

comment:7 Changed 10 years ago by mmadia

Resolution: invalid
Status: newclosed

closing invalid.

Note: See TracTickets for help on using tickets.