Changes between Initial Version and Version 5 of Ticket #11376

Timestamp:

Dec 18, 2007, 6:35:59 PM (17 years ago)

Author:

jmpp@…

Comment:

It should be noted that this ticket spans multiple issues and the preferred way to report them is one issue per ticket. Nevertheless, since discussion already happened on this ticket, I'm going to comment on each of the points raised and will cross them out of the original description if already fixed:

1. This is a Mac OS Forge issue related to virtual hostnames, if I'm not mistaken, and there's nothing the MacPorts team can do about it. I don't think it's fixed, as I've personally seen jumps from http based URLs to https ones, from trac.macports.org based URLs to trac.macosforge.org ones, and even from and to svn.macports.org URLs (with the /projects/macports path). Tickets #10665 and #13428 are presumably related to this issue.

2. This is fixed, crossed out from the original description.

3. See 4 below.

4. I'd love it if our Trac portal could be unified into the look of our new website, but I'm not too sure this is possible. Mac OS Forge personnel has to get back to us on this one, but I'd think they still have more pressing matters to attend to so this might be a low priority issue.

5. If you could provide the SQL glue to build up per port queries I'd happily set them up at the ​query page. Maybe the TracReports page might come in handy for this.

6. You mean to make the query that searches for tickets assigned to the logged in user a standard ​report? If so, then {7} and {8} serve that purpose, but you have to be logged in for them to work. In any case, I don't see how this helps with item 5 above. Lastly, what do you mean by initializing the custom query to search the summary? Its initialization doesn't take any user input parameters, so it's hard to search the summary for anything in particular. Custom query initializes to tickets assigned to the logged in user, displaying the summary among other ticket fields, so I'd say this is also covered for. Crossing out from original description.

7. Ticket properties have been standardized to the most common values: "Priorities" range from High to Low, including "Not set"; "Version" should always match the version of MacPorts you're using, with the svn trunk version always being $current_release + 1 (which is always accounted for in the "Version" property of tickets), or simply not set ("blank") for issues unrelated to MacPorts releases (like the guide or website); Trac belongs to the infrastructure component, Installer is no longer a valid component; the "Severity" property has been removed; for a particular report, any keyword which you might think is related to the issue itself and/or might help find it through Trac searches is an appropriate value for the corresponding field. Reading our ​ticketing guidelines will help in understanding our workflow. Crossing out from original description.

8. If you mean the Help link on the sidebar, then this is more than anything related to the visual design of our Trac portal, see item 4 above in my reply.

9. That help link is about Trac itself. When you say "describe this tracker" I can only assume you are referring to a description of MacPorts itself and our particular Trac workflow. Our new ​web page and ​ticketing guidelines fill that void. Crossing out from original description.

10. We don't maintain that help document and, above all, "Severity" is no longer a valid ticket property for us. Crossing out from original description.

11. (from the first ticket comment) Assigning to a port maintainer is as simple as selecting his/her e-mail address from the "Assign to" pop-up menu for the corresponding ticket property. even though currently not all maintainers are listed in that menu, as per the discussion in ticket #13352. Nevertheless, the facility to assign tickets is there and readily available, so this issue is also covered for.

-jmpp