Description
As of the latest team discussion, we decided upon not allowing the user to be able to edit past versions before the latest, as it would potentially create a conflict of versioning following the SEMVER standard.
We had two options:
- Allow the user to access the version as a read-only editor
- Fork the project at that version
The first would be a herculean effort, given that we would need to add rules for every button and text box, so the second seems more reasonable.
This issue, then, proposes a this new "Fork project" feature that would cover this usability gap, and allow the user to edit past projects.
Description
As of the latest team discussion, we decided upon not allowing the user to be able to edit past versions before the latest, as it would potentially create a conflict of versioning following the SEMVER standard.
We had two options:
The first would be a herculean effort, given that we would need to add rules for every button and text box, so the second seems more reasonable.
This issue, then, proposes a this new "Fork project" feature that would cover this usability gap, and allow the user to edit past projects.