I the past I've tried to separate the technical versions from the planning versions. Some projects do this with code names, but we did with release numbers. The CI system gave us build numbers, we didn't know in advance which build would become the release, esp weeks in advance. So when people ask which version is going to contain feature X, or bug fix Y, then we tell them the planned release number (or code name), and then we have a build and we release it, we bind the release number to the build number.
Once the project had been running for a long time the separation between the two version numbers wasn't so tight, and it didn't matter as we were much better about planning releases as there was less change. David -- View this message in context: http://www.nabble.com/Version-Numbers-with-Scrum-tp19182915p19250282.html Sent from the Maven - Users mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
