Timeline for Finding the right directory structure for version control
Current License: CC BY-SA 3.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jul 26, 2012 at 17:30 | comment | added | Wynand Pieterse | Hehe sorry just tought I should express it a more :) | |
| Jul 26, 2012 at 11:40 | comment | added | Kylotan | Yes, my comment is meant to read as "exported assets, just like binary builds of code, should be excluded" :) | |
| Jul 26, 2012 at 11:27 | comment | added | Wynand Pieterse | What I meant with exported assets is assets that are ready to be consumed by the engine. So basically the artist will export into this format straight out of their DCC tool | |
| Jul 26, 2012 at 11:26 | history | edited | Laurent Couvidou | CC BY-SA 3.0 |
Added directory layout; added 3 characters in body
|
| Jul 26, 2012 at 11:13 | comment | added | Kylotan | +1. This is exactly what I was going to say - separate directories for assets and code (so that artists don't have to check out code and vice versa) but exported assets - like binary builds of code - should be excluded and generated on demand. (If you want to keep snapshots of the build, that's fine, but that's usually best done outside of version control.) | |
| Jul 26, 2012 at 10:55 | comment | added | Wynand Pieterse | Hmmm that's way different than what I thought. I like this aproach more. Keep all "source" data under source control, and generate all data locally as needed. This will also work nicely with a CI server building the stuff and just pushing it out to everybody | |
| Jul 26, 2012 at 8:58 | history | answered | Laurent Couvidou | CC BY-SA 3.0 |