Forum Discussion
Current Version Indicator Published
I am assuming that only one copy of the course is being updated at any given time, and not a duplicate copy. So, yes, the versioning would change in that scenario. We only work off of the original course and make updates to it. No duplicating.
There wouldn't need to be duplicates for there to be different ways to version. For a lot people, any updated version just gets the next whole number up, but many bigger projects (and indeed in a lot of software development), the periods are used to identify the kinds of changes. In version a.b.c., a is used to qualify major feature or updates such that may break backward compatibility, b is used for smaller features and upgrades, and c is used for patches or bug fixes. An entirely new Code of Conduct eLearning may go from version 2 to version 3, but if there was a problem with a slide transition and I fixed it so the course works normally, that might mean the version goes from 2 to 2.0.1.
This is why Rise can't assume how I and others want to version content. If it assumes and says something is version 3 when I don't want it to be, that's a problem.
I have never thought about versioning in that way. Major vs. Minor. As an instructional designer supporting my internal stakeholders, I need to simply understand which copy of the course are my stakeholders taking; which copy am I viewing; and if the updates I made and published to our LMS system updated properly upon testing. The versioning number for me, is that quick glance to know 100% that the published course is the desired course version. This saves me from having to dig through the course (for example) five lessons deep and search for the tiny text update that was made.