- Lock step versioning has been shown to not work across multiple bodies
- Moving version has challenges!
- Possible workable approach
- Upgrade as you need to
- When the tool has a feature you need
- Try to stay close to the latest
- Evaluate the tool adequately before moving
- Share the evaluation activity
- When you are sharing with someone who is on a later version
- Upgrade only the transferred parts and commit to keep doing this
- Upgrade the source
- If upgrade loses a feature that you use then you have to change to deal with it
- Try to get the tool changed (use our weight as we have large and rich models... but note that we pay nothing)
- We have chosen UML due to its general nature but we are dependent upon one tool
- If the tool development goes in a direction that is significantly contrary to our necessary evolution then we will need to consider changing tool
Martin Skorupski Action: On next call determine who should write the above up as a process and how we should then agree it. Also idetify other areas to consider wrt the above.