Not understanding "Fixed in Version" field
Let's say I'm working on version 0.1 of a development project, and I've added versions for 0.1, 0.2, 0.3, and 1.0 in Gemini. Now I've decided that my classes are too tightly coupled, so I want to create an "Enhancement" issue that reminds me to refactor the classes. It's low priority, so I don't want to work on it until the very end of the development phase, but I definitely want to have it done before the 1.0 release is out.
Given this scenario, what exactly am I supposed to put for the "Fixed in Version" and "Versions Affected" fields? My guess is that "Fixed in Version" should be "1.0" and "Versions Affected" should be "0.1", "0.2", and "0.3".
However, this is a bit nonsensical because the 1.0 version hasn't even started yet, so it's not accurate to say that the issue has been "fixed" (past tense). Also, what happens when I inevitably add new versions (0.4, 0.5, etc.)? I guess I'll have to go back and edit the issue to add these new versions to the "Versions Affected" field.
Given these issues, is my understanding of the fields correct? (The documentation does not even mention the word "fixed".)
Trevor Harmon
· 1 |
|
Sunday, August 22, 2010, 11:34:24 PM |