How to work with version?

[karl.reichert]

I have a question about versions, the manual is not quite clear about them.

I'm using a version scheme of x.y.zz, where x is changed in major updates only, y is changed in minor updates and zz is changed in so called bugfix updates only. Especially the bugfix version is changing quite ofter, let's say a few times a week. But minor and major version are increased from time to time, too.

So the question is how to deal with that.

If I create the versions for the project, I could add them like "1.0.00", "1.0.01" ... "9.9.99". This of course is a lot of work to do and makes the selection list for versions for users when entering a bug pretty long. Additionally, the changelog and roadmap will be nearly unusable for a manager which wants to know, what changes were made from one to the next minor version. If he wants to check that, he has to go through all bugfix versions in the changelog. However, for a developer, which needs the exactly version where a bug is found and where it's fixed, this is good.

If I would create version like "1.0.x", "1.1.x" ... "9.9.x", selecting the version when entering a bug is more easy and the changelog and roadmap will be nice for managers, but not for developers. All the information about the bugfix version will be lost, which is a no go for developers.

So I wonder how you guys are solving this, because I saw in your bugtracker, that when entering a bug, the exactly version (e.g. 1.2.1) has to be selected. When I check your changelog/roadmap, I can see, that there is a changelog for the exact version 1.2.1, but also one generated for the version 1.2.x. How did you do that, what do I have to do to have the same?

And is there a way that I don't have to enter each version from hand? I know, I could write a script (and I will probably do), but wouldn't it be nice to have Mantis ask for a range and it will create all versions in between itself?

Thanks in advance!
Karl

[karl.reichert]

No one?