...
These '.x' branches are also commonly referred to as 'maintenance branches', and as new version versions of Sakai are cut and tagged, a matching version of the SCORM Player will be cut from the appropriate maintenance branch. For example, when the Community cuts and releases the official 11.0 tag from the main 11.x Sakai code base, the SCORM Player will follow suit and cut an 11.0 tag from it's own 11.x maintenance branch. The same can be said for releases in the 10.x version family.
When the time comes that the Community creates a 12.x branch, and ultimately releases a 12.0 release, the SCORM Player will naturally follow suitthe leader. A new '12.x' maintenance branch will be cut from master, and master will effectively become what will later be known as version '13'.
...