Hi, versions are independent of milestones. Already the meaning of the terms "version" and "milestone" can be different from use case to use case. Some people interpret a version as dated event, some say it's just like a release label. In the end it's just a grouping tag for a bunch of tickets, but more related to an software package entity. Also a milestone is interpreted differently. For trac.edgewall.org it's the same as the released version, for e.g. us it's just an event in the ISO9001 process (milestone M1 to M5). There can be several versions on the way to a milestone, and even if the final version is bundled, some tickets can remain for the milestone. We cannot set a fixed hierarchy, it depends how you use Trac and interpret both terms. For some people: - milestones can include several versions - versions can include several milestones - a milestone can happen without a special version (M2) - a version can happen without a milestone (4.5.24 after M5)
CU, F@lk ---- R&D Software Baumer Optronic GmbH www.baumer.com Gesch?ftsf?hrer: Dr. Albert Schmidt* Dr. Oliver Vietze Sitz der Gesellschaft: Radeberg Amtsgericht Dresden: HRB 15379 Ust. ID: DE 189714583 -- You received this message because you are subscribed to the Google Groups "Trac Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/trac-users?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
