"Affected Versions" vs "Fixed in Version" and what is a "version" anyw
I'm just getting started with Gemini, so I'm still getting used to the options and such... What is the difference between "Affected Versions" and "Fixed in Version" fields? I guess I'm not sure what the "Affected Versions" field is used for or how it affects how an issue is set up.
All software development work is for a web-based application... so the concept of "version" is a bit odd for us. We don't have "builds" per se... we just deploy code (.aspx and code and image files and what-not) as needed. But, if we don't use versions, then the Project Log and Road Map stuff seems to be meaningless.
So one thought was just to have a "next release" version. Any issues that a developer wants to release can assign it to that version. Then, when I really do move code into production, I can rename the version (perhaps a date derivative like 20071231), and create a new "next release" version...
Would that work?
MNoreen
· 1 |
|
Monday, January 7, 2008, 8:53:51 PM |