Source Files & Version Control Best Practices
I'm wondering if anyone would be willing to share any best practices they may have found in terms of the storage of source file(s) along with released versioning controls when it comes to developing and publishing of Learning Program/Modules.
For example; in our organization there can be several authors developing content at the same time (which obviously will over the years too). Are best practices to use a shared-drive to share final .story (raw source files) along with any attachments and related files that may accompany that project?
Also, what does everyone use for versioning control of published items? This can be extremely important when relating to compliance items. At times, we may get a request from legal to provide them with all released versions of a module over the last X years. I've considered outputting a word-document each time we publish a version to a shared location for tracking purposes -- but word documents are very limited in nature especially as courses evolve in terms of interactivity and attached media. I have some other ideas too but I'm curious if anyone has any best practices they can share here?
Has anyone created tracking systems of their own (e.g. in Excel) or utilize other software platforms to help streamline this process?
Thanks in advance!