# Table that defines what cvs revision numbers correspond to which version numbers
# For a single version number all the cvs revisions numbers are broadly compatible - at least
# forwards (e.g. perhaps dm model additions, but not renames/deletions). So the OT should be
# able to cope with any of these revisions.
#
# For version numbers with minor (.something) versions the idea is that while these do
# require migrations they are not normally provided on the grounds that the affected revisions
# are typically internal to the OT team, so no persistent projects should be affected (there
# should be no projects with those revision numbers "in the wild"). However, in principle 
# migrations could be provided if necessary.
#
10  10
9   9
8   8
7   7
6.0 1.74,1.73.4.1
5.0 1.61.4.7,1.61.4.8,1.72,1.73
#4.1 1.61.4.8
4.0 1.60.6.3,1.61,1.62,1.63,1.64,1.65,1.66,1.67,1.68,1.69,1.61.4.1,1.70,1.71
3.1 1.60.6.1,1.60.6.2
3.0 1.58.4.4,1.59,1.60,1.61
2.2 1.58.4.2,1.58.4.3
2.1 1.58.4.1
2.0 1.56.6.1,1.57,1.58
1.0 1.54,1.54.4.1,1.55,1.56
