#40353: Ticket Guidelines should include instructions for upgrade requests -------------------------+--------------------- Reporter: tal@… | Owner: markd@… Type: enhancement | Status: new Priority: Normal | Milestone: Component: guide | Version: 2.2.0 Keywords: | Port: -------------------------+--------------------- http://guide.macports.org/#project.tickets As a newcomer to MacPorts (but not to Macs, nor Ports :-) ), it wasn't clear how to report that a port is out of date. I learned by filing a badly formatted ticket, and being corrected. This wasted your time, for which I apologize. Since people that need to report out of dates this are often going to be newcomers, my suggestion is to make the docs "match the audience" a bit better by being more "hand-holding". Two points: (a) it wasn't obvious to set type=upgrade, component=ports. (b) people should be told to CC: the maintainers (and that "{{{port info --maintainers $portname}}}" reveals who that is). Suggested fix: Between 7.3.1 and 7.3.2 insert a new section similar to this: 7.3.x Reporting out-of-date ports / requesting updates to a port * Report out of date ports by opening a bug. See (link to 7.1.3. Trac Ticket Guidelines) * When creating the bug, set: * Summary: [port] [version] [concise description] * Example: "ghostscript @9.0.3_1 please upgrade to newest version 9.0.9" * Type: upgrade * Component: ports * CC: the maintainer. To determine this, see the output of: {{{port info --maintainers PORT}}} * Example: {{{port info --maintainers ghostscript}}} * Port: the name of the port [Note that the fields are listed in the same order as on the form, with the same capitalization. These things matter to newcomers.] Also, in section "7.1.3. Trac Ticket Guidelines" add to the end of the first paragraph: "... If you are reporting an out-of-date port, please see (link to the above section)." Thanks! -- Ticket URL: <https://trac.macports.org/ticket/40353> MacPorts <http://www.macports.org/> Ports system for OS X