This is a far-reaching proposal and should be swarmed on to come up with the best solution. Here's what I have so far: Talking with Firefox and Firefox mobile teams, having sequential version numbers for products would be very useful. We often have 3 versions of firefox going at the same time, i.e.: 12 in nightlies 11 in aurora 10 in beta Users want to be able to specify that a test case applies to a certain version and onward. So I might want to write a test case for 11 onward and not have it show up for test runs for 10.
A Pivotal Tracker story has been created for this Bug: http://www.pivotaltracker.com/story/show/22646383
Cameron Dawson added a comment in Pivotal Tracker: I know this is huge. We need to discuss this and hash out what's feasible and what's not. But I think this will solve all the questions about where are test versions are relevant to products/cycles/etc. This has many implications: 1. Products need an ordered set of versions that apply to it and UI to organize them 2. Test case versions need to be able to specify a product AND product version 3. Test cycles need to be able to specify product version 4. Test runs specify specific product versions within the cycle version 5. When a test manager adds a suite to a test run, it takes the latest version of the test case that would apply to the version set in the run 6. If a new test case is added to that suite, and a run exists that applies to the version specified, it will automatically get added to the test run (if test run still active, not closed). 7. Several more, I suspect Note: A product version is ALMOST like an environment category. The exception is that they are sequential.
Carl Meyer added a comment in Pivotal Tracker: Cam: I'm back from vacations! And we should talk about this story soon, as if we're going to do it in the near future I should probably get it into the data model now.
Carl Meyer added a comment in Pivotal Tracker: One thing I don't understand here that is relevant to the data model: is a Cycle associated with a single product version, or multiple product versions? I would have assumed a single version, but then I don't understand what it means to say "Test runs specify product versions within the cycle version" rather than just "test runs inherit the same version as their cycle." Cam, can you clarify your thoughts here?
Carl Meyer added a comment in Pivotal Tracker: Also, should product versions be orderable in any custom ordering, or should they be automatically intelligently ordered in a way that will do the right thing for most common dotted numbering schemes, and fall back to lexicographic ordering? If the latter is good enough, I think there's a lot of value in avoiding the extra UI complexity of custom ordering.
Cameron Dawson added a comment in Pivotal Tracker: Let's skip #4 above. Runs inherit the version from the cycle.
Carl Meyer added a comment in Pivotal Tracker: And we'll do automatic product version ordering, based on splitting dotted components and ordering numerically within each component, with fallback to lexicographic ordering if the component isn't numeric.
Carl Meyer changed story state to started in Pivotal Tracker
Carl Meyer changed story state to finished in Pivotal Tracker
Carl Meyer changed story state to delivered in Pivotal Tracker
Cameron Dawson changed story state to accepted in Pivotal Tracker