#14909: Roadmap does not provide direction ----------------------------------+----------------------------------------- Reporter: rhwood@macports.org | Owner: wsiegrist@apple.com Type: defect | Status: assigned Priority: High | Milestone: Component: server/hosting | Version: Resolution: | Keywords: milestones roadmap ----------------------------------+----------------------------------------- Changes (by wsiegrist@apple.com): * keywords: => milestones roadmap * priority: Normal => High * component: base => server/hosting * milestone: Website & Documentation => Comment: I would like to use Milestones for their actual purpose, which is to assign tickets to future releases so we can see how close we are to a given version. I propose to remove the existing "category" milestones and setup milestones for 1.6.1, 1.7.0, 1.8.0, and 2.0. The 2.0 milestone would basically serve as a bucket for tickets that are to be worked on far in the future. People can then nominate tickets for a particular release by putting them in a milestone. If people disagree, then the milestone is changed or removed. This of course only applies to tickets against base, or whatever else goes into a release. Tickets against portfiles should not have a milestone or a version, since those fields deal with base releases. The version field should mark the most recent version that is affected by the ticket. An enhancement ticket should not have a version number, but it should have a milestone. A defect ticket should have both set. Please provide feedback here in a comment. Once we come to a final set of guidelines, I'll update the Guide and perform the necessary ticket changes. -- Ticket URL: <http://trac.macports.org/ticket/14909#comment:2> MacPorts <http://www.macports.org/> Ports system for Mac OS