Question
`.nuke/temp`, `.nuke/parameters.json`, `.nuke/build.schema.json` etc. are hard-coded inside `Nuke.Common` as the standard NUKE working directory.
Three options:
-
Keep `.nuke/` — the directory name becomes a historical artifact, like how Mercurial repos still have `.hg` after rebranding. Zero migration cost for consumers. Cheap.
-
Migrate to `.fallout/` — clean rebrand. Every consumer needs to move files. Source code reads from new path; ideally also has back-compat fallback that warns.
-
Hybrid — read from both, write to `.fallout/`, warn if `.nuke/` is found.
Recommendation
Option 3 for two release cycles, then drop `.nuke/` support. Captures the symbolic break without inflicting a forced migration.
Out of scope here
Implementing the chosen option. This issue is the decision; the implementation issue follows.
Done when
Question
`.nuke/temp`, `.nuke/parameters.json`, `.nuke/build.schema.json` etc. are hard-coded inside `Nuke.Common` as the standard NUKE working directory.
Three options:
Keep `.nuke/` — the directory name becomes a historical artifact, like how Mercurial repos still have `.hg` after rebranding. Zero migration cost for consumers. Cheap.
Migrate to `.fallout/` — clean rebrand. Every consumer needs to move files. Source code reads from new path; ideally also has back-compat fallback that warns.
Hybrid — read from both, write to `.fallout/`, warn if `.nuke/` is found.
Recommendation
Option 3 for two release cycles, then drop `.nuke/` support. Captures the symbolic break without inflicting a forced migration.
Out of scope here
Implementing the chosen option. This issue is the decision; the implementation issue follows.
Done when