Binary files and versioning storage space
I have a pre-sales customer asking the following two questions. I researched the forum and found a discussion on binary files and file locking (future feature) but did not see a discussion about size requirements.
1. Are binary files stored efficiently (PowerPoint for example)?
2. Can I control the number of versions of a binary file I want to retain? That is set a limit of the last 30 revisions for example? I want to retain the meta-data for all versions but conserve storage for these binary (PowerPoint) files.
================
"See https://jazz.net/learn/LearnItem.jsp?href=content/docs/source-control/index.html for an overview of the basic SCM actions.
However, we won't have file locking for 1.0, so you'll need to coordinate your edits, for example via chat/mail, to avoid conflictings edits. Now if you happen to edit concurrently, it isn't a problem, you'll get a chance to resolve but without a merge tool, you'll have to pick a version to move forward."
1. Are binary files stored efficiently (PowerPoint for example)?
2. Can I control the number of versions of a binary file I want to retain? That is set a limit of the last 30 revisions for example? I want to retain the meta-data for all versions but conserve storage for these binary (PowerPoint) files.
================
However, we won't have file locking for 1.0, so you'll need to coordinate your edits, for example via chat/mail, to avoid conflictings edits. Now if you happen to edit concurrently, it isn't a problem, you'll get a chance to resolve but without a merge tool, you'll have to pick a version to move forward."