I'm confused mostly about the "versions". What is the meaning of having a version? All I see on Trac's site (trac.edgewall.org) is milestones. All reporting and project management seems to be around milestones. What are versions for?
I read somewhere that milestones are supposed to be future feature packs, and versions are supposed only to indicate which release (in the past) each ticket did actually get into. But that seems incomplete, as it would indicate that there would also be some mechanism to mass-assign tickets to versions (e.g. assign a completed milestone to a version/release). That seems intuitive, and that's the way I'd like to work, with the following clarifications: - Each milestone would be a batch of tickets needed to complete a feature (i.e. milestones are features of the project, which seems to be about the way they are being used already). - Each version would be a bunch of milestones/features that have been included, or are expected to be included in that release (i.e. a version is a release), depending on the release date (whether it's in the past or future This way it is possible to track features and plan releases (i.e. by adding/subtracting features, thus postponing or hastening a release). How about that? Oh, and I'd like to mention that the roadmap also makes no mention of versions. Doc P.S. I think Trac is great otherwise, especially the upcoming 0.11 release (NOT milestone! :) ) --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Trac Users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/trac-users?hl=en -~----------~----~----~----~------~----~------~--~---
