Latest Neocron News and Information

  • New test server patch #550 has been released to Vedeena

Difference between revisions of "NcSource talk:SVN Structure"

From Neocron Wiki
Jump to: navigation, search
m (Created page with 'r2d22k wants to discuss changing the setup of this svn, so go ahead mate ;) --~~~~')
 
Line 1: Line 1:
 
r2d22k wants to discuss changing the setup of this svn, so go ahead mate ;) --[[User:Biglines|Biglines]] 12:32, 26 February 2010 (UTC)
 
r2d22k wants to discuss changing the setup of this svn, so go ahead mate ;) --[[User:Biglines|Biglines]] 12:32, 26 February 2010 (UTC)
 +
 +
Yeah he wants to discuss this ^^ currently everything is just put into more or less one folder. i think we should change that to something like the following:
 +
/trunk
 +
/branch
 +
/content_work
 +
/content_finished
 +
/release
 +
the '''trunk''' folder would be the coders main working folder everything code related should go here. the substructure of this folder should look like the folderstructure the source sdk creates when you use the "create new mod" function
 +
the '''branch''' folder will contain the sourcecode to corresponding to a specific release, i think to really be on the safe side ( i know svn normally saves all diffs but you never know what can happen) we should keep the sourcecode of every single version we release
 +
the '''content_work''' will contain all the textures, models, maps and everything related to art that is currently being worked on. one could for example create the subfolders: textures, models, maps and sounds
 +
'''content_finished''' i'm not sure how we should structure this folder. we could for example only put the compiled .vmt, .vft and such stuff in this directory or we could move the finished models the .3ds, .bmp etc in there and put the compiled versions somewhere else
 +
'''release''' will contain the files needed on the clients we should perhaps create subfolders to distinguish between develreleases, alpha releases and beta releases. the devreleases are the releases we will use internally to test things, the alpha and beta releases will be on a milestone basis --[[User:R2d22k|R2d22k]] 12:58, 26 February 2010 (UTC)

Revision as of 12:58, 26 February 2010

r2d22k wants to discuss changing the setup of this svn, so go ahead mate ;) --Biglines 12:32, 26 February 2010 (UTC)

Yeah he wants to discuss this ^^ currently everything is just put into more or less one folder. i think we should change that to something like the following: /trunk /branch /content_work /content_finished /release the trunk folder would be the coders main working folder everything code related should go here. the substructure of this folder should look like the folderstructure the source sdk creates when you use the "create new mod" function the branch folder will contain the sourcecode to corresponding to a specific release, i think to really be on the safe side ( i know svn normally saves all diffs but you never know what can happen) we should keep the sourcecode of every single version we release the content_work will contain all the textures, models, maps and everything related to art that is currently being worked on. one could for example create the subfolders: textures, models, maps and sounds content_finished i'm not sure how we should structure this folder. we could for example only put the compiled .vmt, .vft and such stuff in this directory or we could move the finished models the .3ds, .bmp etc in there and put the compiled versions somewhere else release will contain the files needed on the clients we should perhaps create subfolders to distinguish between develreleases, alpha releases and beta releases. the devreleases are the releases we will use internally to test things, the alpha and beta releases will be on a milestone basis --R2d22k 12:58, 26 February 2010 (UTC)