staff
1,114
edits
Content:Files: Difference between revisions
Jump to navigation
Jump to search
→Version: added some language regarding version continuity
(→Version: clarity) |
(→Version: added some language regarding version continuity) |
||
| Line 48: | Line 48: | ||
Sometimes the group makes mistakes and wants to correct them by releasing a second (third, fourth...) version, usually called ''v2'' (''v3, v4, ...''). This field is usually based on information in the file name (where no information normally means ''version 1''). | Sometimes the group makes mistakes and wants to correct them by releasing a second (third, fourth...) version, usually called ''v2'' (''v3, v4, ...''). This field is usually based on information in the file name (where no information normally means ''version 1''). | ||
'''IMPORTANT''': Even if a group releases two files of the same episode it does not mean that the first has to be marked ''v1'' and the second has to be marked ''v2''. There are other reasons to do something like that other than correcting mistakes | '''IMPORTANT''': Even if a group releases two files of the same episode it does not mean that the first has to be marked ''v1'' and the second has to be marked ''v2''. There are other reasons to do something like that other than correcting mistakes, such as: different source (DTV/DVD), different sub languages, dual audio vs single audio releases, high and low quality versions, etc. | ||
'''Discretion should be applied''' when "other reasons" are the cause of multiple releases. For example, if the group's intent is to release as a final product only a dual audio release, but they release a single audio release as a "v0" or "draft" version, then we should consider this single audio "draft" within the version continuity of any subsequent dual audio releases. However, if the group's intent is to release as a final product both a single and dual audio release, do not combine the versioning continuity. | |||
{{eyecatch|Note|We generally do not consider resolution changes and source changes as version bumps. That being said, you are free to add a file comment, indicating a file is marked as v2 and intended to replace a certain file. For example: <pre>Labelled as v2 of https://anidb.net/f2030447</pre>}} | {{eyecatch|Note|We generally do not consider resolution changes and source changes as version bumps. That being said, you are free to add a file comment, indicating a file is marked as v2 and intended to replace a certain file. For example: <pre>Labelled as v2 of https://anidb.net/f2030447</pre>}} | ||