Projects / kInspire

An interesting concept I addressed when working with project pier. Again versions seems to be purely program oriented and almost clutters me into being required to use them. At the same time, you are grouping off a section of work and then again doesn't milestone serve this purpose? In projectpier what I did to address this issue was NAME my milestone "alpha, beta, v.1, v.2" which gave me more control over how I'm grouping tasks/task lists. In addition to the option of throwing files/messages under milestones (a seperate issue) I think you may want to consider removing versioning and allowing the user to follow this approach of naming milestones versions. I'm not sure how many milestones there are to versions but in projectpier's own development they have testing, submitting, developing, renaming all per version and still built a system that solely endorses milestones. I could then name a milestone "alpha testing, alpha release, alpha bug submitting, alpha translating" however that _or_ allowing subsectioning of milestones may still be a question worth postulating. I however am fond of the less is more approach and lack of clutter allowed by only having milestones (part of my 'adding a task should be simple' argument). I just checked, milestones cannot be assigned underneath other milestones in projectpier. That isn't a point only a comment.