From the to-do list: MPA V1.0: Older issues and tasks
✔ Optimize revisions tracking
(Completed by Pierre henri Seylan on July 25, 2018)
Comments
Pierre henri Seylan on July 12, 2018:
When DAW projects are synched, a new revision is pushed overtime that a file changes in the tracked directory. This is not working so well as sometimes temporary files are being added by the DAW.
To improve this mechanism we should push a new version only when the main project file has been updated.
The expected behavior is that the project is pushed as new revision only when the main project file is re-saved/ modified. If new files are added to the project directory but the main file didn't change (user didn't save the project), the revision is not pushed. When pushing the new revision, we should handle it like before: pushing the entire directory / all new and modified files.
The main project file is tracked by the app, it is the file which appears in the local project tab, and the one being opened when clicking on "open" in the revisions list.
Comments
Pierre henri Seylan on July 12, 2018:
This is not working so well as sometimes temporary files are being added by the DAW.
To improve this mechanism we should push a new version only when the main project file has been updated.
The expected behavior is that the project is pushed as new revision only when the main project file is re-saved/ modified.
If new files are added to the project directory but the main file didn't change (user didn't save the project), the revision is not pushed.
When pushing the new revision, we should handle it like before: pushing the entire directory / all new and modified files.
The main project file is tracked by the app, it is the file which appears in the local project tab, and the one being opened when clicking on "open" in the revisions list.
Karim Alabtakh on July 25, 2018: