You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Wouldn't it be (at least potentially) valuable to have a formal way of versioning swirl courses (akin to package versioning etc) so that problems identified with course content can be isolated to particular versions of swirl course content in the case of students finding issues? I haven't seen a reference to this kind of thing anywhere in the documentation, so I assume it doesn't exist yet and I think it is worth considering.
Incorporating course versioning formally would of course involve updates to swirl itself rather than just to swirlify but since the motivation for the feature would be driven more from the instructor side I figured it would be more relevant to post it as an issue/potential enhancement here.
The text was updated successfully, but these errors were encountered:
Since the version number in lesson.yaml defaults to the version of swirl that is installed I'm assuming that it is intended to indicate the swirl version and not the course/lesson version.
Wouldn't it be (at least potentially) valuable to have a formal way of versioning swirl courses (akin to package versioning etc) so that problems identified with course content can be isolated to particular versions of swirl course content in the case of students finding issues? I haven't seen a reference to this kind of thing anywhere in the documentation, so I assume it doesn't exist yet and I think it is worth considering.
Incorporating course versioning formally would of course involve updates to swirl itself rather than just to swirlify but since the motivation for the feature would be driven more from the instructor side I figured it would be more relevant to post it as an issue/potential enhancement here.
The text was updated successfully, but these errors were encountered: