Page MenuHomeAleph Objects Inc

Implement version control for ohai content
Closed, InvalidPublic

Description

Currently there is no good way to tell what the history of an OHAI looks like or to revert to previous versions. If the OHAI content were a git repo somehow, we could use the same methods to maintain the instructions that we use to maintain the hardware source.

Event Timeline

kent created this task.Dec 18 2018, 10:41 AM
kent triaged this task as Normal priority.
kent created this object with edit policy "LulzBot Hardware Products (Project)".

Suggest starting with https://github.com/etianen/django-reversion and seeing if that will be a good solution

kent changed the edit policy from "LulzBot Hardware Products (Project)" to "Ohai-kit (Project)".Feb 5 2019, 2:50 PM
kent moved this task from Backlog to Pending Review on the Ohai-kit board.Feb 5 2019, 2:52 PM
kent raised the priority of this task from Normal to High.
kent lowered the priority of this task from High to Wishlist.Mar 28 2019, 1:58 PM
kent moved this task from Pending Review to Backlog on the Ohai-kit board.
kent closed this task as Invalid.Apr 2 2019, 9:15 AM

Now that we have the print to pdf working better, we can just export a pdf and include it in the source before we create a product tag. This way, we will have the a version of the assembly instructions for each tag and we can look back to previous versions by just checking out the tag in the product repo.