getavalon
Workfiles: Major/Minor versioning
@tokejepsen can you give an example of how you'd like to see this work with the template?
We have {version} now. Would the other counterpart be {minor} or {revision}?
I haven't used this in production so I am looking to get some more input on how you are used to using this?
Also, does major/minor get similar "select version" control? And does it auto-increment the major or the minor? In UX-design, how would the user decide to increment which of the too?
I personally haven't actually used major/minor versions. Think it was @mkolar that mentioned it as a feature.
I've never seen this feature anywhere in production.
Are we talking about something like myfile_1.1.ma or myfile_v001_v001.ma?
We use this all the time for workfiles.
An artist works toward v02 of a shot, but needs to version for himself within this version so his workfiles look like this
sh010_animation_v01
sh010_animation_v02_001
sh010_animation_v02_002
sh010_animation_v02_003
sh010_animation_v03_001
sh010_animation_v03_002
but we don't specify what the minor version needs to be at this point, so some artist use their initials and a number for instance, others, just numbers. Technically we use comments for this.
Maybe the issue is actually that the comment field is being used for a variety of things. Perhaps there is a better wording for this field of the work file template?
We have {version} now. Would the other counterpart be {minor} or {revision}?
We naturally started calling them subversion in the studio.
@mkolar would you be able to propose/describe how you'd like your artists to be confronted with an interface for doing either an incremental save {version} and how they would do the {subversion} save.
What would feel natural for you?