Idea: add Trac field for name of port

[shreevatsa.public@…]

It would be a good idea to have a Trac field for port name.

Possible uses:

• Users could exactly specify which ports are affected, when creating tickets.
• Maintainers could keep better track of what bugs a specific port has.
• Users facing problems with a port could more easily search for existing bugs involving that port.
• Committers might not have to manually cc maintainers: this could (in principle) be automated.

_wms thought this would be a good idea and asked me to create this ticket so that he would get to it eventually :-)

[raimue (Rainer Müller)]

I think it would be nice to also display the list of maintainers as an read-only field once we get this. This will be useful for a quick check if the submitted patch comes from a maintainer and therefore can be committed.

[wsiegrist@…]

I've added a text field labeled "Port". I'll have to think about how to automate some of the things mentioned above (maintainers and such).

[shreevatsa.public@…]

Great! It would also be desirable for the "Port" field to accept only valid port names.

[(none)]

Milestone Website & Documentation deleted

[ryandesign (Ryan Carsten Schmidt)]

Replying to shreevatsa.public@…:

It would also be desirable for the "Port" field to accept only valid port names.

The ticket might be a submission of (or a request for) a new port, in which case the Port field wouldn't contain the name of an existing port. So we could just enforce validation for defect, update and enhancement tickets, but really, I think we've done ok over the years since the Port field was added without it being validated.

[cooljeanius (Eric Gallager)]

Cc Me!

[larryv (Lawrence Velázquez)]

Cc Me!

[mf2k (Frank Schima)]

I assume this falls under Ryan now.

[raimue (Rainer Müller)]

We do have a custom port field for quite a while. I am not aware that any problems occurred without validation of the port names. I consider the original request of this ticket fixed.