So, long after realizing that having MacPorts version specific milestones up on the Trac Roadmap doesn't work one bit unless we have a defined set of goals for each release (as was naturally concluded from Jordan's "Objection your Honor, Counselor is leading the witness!" type of question last week), I finally got my act together and closed/deleted such milestones. I closed the 1.5 milestone as I'm sure we can consider that release set already over, and deleted the 1.6 milestone, retargetting all tickets in both as either base bugs or base enhancements. Further tickets against base should be filed as either one of those, bugs or enhancements, just as we have for ports. Version specific milestones can be brought back to life once we start defining clear and specific goals for each release, but not before as all they add is confusion. One thing we can do in the mean time, I'd suggest, is create a version specific milestone for a particular set of releases after such is considered over (that is, when we start another one, e.g. 1.7 and leave 1.6 behind), and reclassify tickets that were closed in the relevant timeframe into it... if such work flow does not prove to be too much of a hassle. Mark, Simon, Maun Suang, could you guys amend the #project.tickets section of the guide as appropriate to reflect this new workflow? Thanks! Regards,... -jmpp