Managing Project Versions

[Dentxinho]

What steps do you guys follow to release a new version in mantisbt.org tracker?
I saw that there are versions 1.2.x and 1.3.x which new issues are targetted to. When launching 1.2.(x+1), what do you do? Rename 1.2.x to 1.2.(x+1), create another 1.2.x and manually retarget the issues that weren't fixed to the brand new 1.2.x ?

How do you other goys manage versions in other projects?

Any help will be appreciated.
Thanks!

[atrol]

I saw that there are versions 1.2.x and 1.3.x which new issues are targetted to. When launching 1.2.(x+1), what do you do? Rename 1.2.x to 1.2.(x+1), create another 1.2.x and manually retarget the issues that weren't fixed to the brand new 1.2.x ?

Yes, that's the workflow

and manually retarget

Is this a problem for you? Are you aware that you can update target versions for multiple issues on page "View Issues"?

[Dentxinho]

I saw that there are versions 1.2.x and 1.3.x which new issues are targetted to. When launching 1.2.(x+1), what do you do? Rename 1.2.x to 1.2.(x+1), create another 1.2.x and manually retarget the issues that weren't fixed to the brand new 1.2.x ?

Yes, that's the workflow

and manually retarget

Is this a problem for you? Are you aware that you can update target versions for multiple issues on page "View Issues"?

Thanks atrol, I was not aware of that.
This way all mails are sent? Isn't that a problem, a very active reporter receiving 10+ emails at once?

[atrol]

This way all mails are sent?

Yes

Isn't that a problem, a very active reporter receiving 10+ emails at once?

I think the e-mails are not the problem for the reporter. The problem will be, that he will not be happy that his issues will be resolved in "next" version although he saw it on the roadmap.
If you want avoid e-mails you should not set too much issues to target version X if you are not really sure that you will fix most of them in next release.