Issues with oudated ports / GitHub

Ryan Schmidt ryandesign at
Fri Oct 7 10:16:13 PDT 2016

> On Oct 7, 2016, at 12:05 PM, Rainer Müller <raimue at> wrote:
> We are currently using the type field with "defect", "enhancement",
> "update", "submission", "request". A ticket should be filed with the
> appropriate type.
> To indicate a patch is attached to the ticket, we add the "haspatch"
> keyword. Additionally the "maintainer" keyword can be added to express
> the update needs no thorough review as it comes directly from the
> maintainer.
> I am not sure how we could change these to make triaging trickets easier.

I've been unhappy with the fact that the "update" ticket type represents both submissions of updates and requests for updates, whereas submissions of new ports and requests for new ports each get their own ticket type. There should either be 2 ticket types (one for new ports, one for existing ports), or 4 ticket types (new port submission, new port request, existing port update submission, existing port update request). The names should also be more obvious. We constantly get "request" tickets filed which are not new port requests but something else.

I'm also not happy with our ticket resolutions. "invalid" sounds rude; "not a bug" might be nicer. We also should have "not our bug" for things which are bugs but not MacPorts bugs (things like Xcode bugs, macOS bugs).

We also need some way to classify tickets which are not supposed to be in the issue tracker, like user-specific problems, tech support, etc.

Maybe we need to take a fresh look at how some other projects classify their issues.

More information about the macports-dev mailing list