version control - Best practices to store binary documents in SVN -


from answers is version control (ie. subversion) applicable in document tracking?, okay store documents in svn. projects have documents requirement book, design book, manuals, test report etc. best folder structure store it? should store under each project, create document folder same level src? or should separate , create document folder (and create subfolder each project) under root? or should use repo?

root |-- parent-pom |   |-- branches |   |-- tags |   `-- trunk |       `-- pom.xml `-- projecta     |-- branches     |-- tags     `-- trunk         |-- module1         |   `-- pom.xml         |-- modulen         |   `-- pom.xml         `-- pom.xml 

i think makes sense have under project. way gets versioned application code. , it's not in module code aren't make builds large.

when "project", meant level docs at. sounds projecta me description, root.

root |-- parent-pom |   |-- branches |   |-- tags |   `-- trunk |       `-- pom.xml `-- projecta     |-- branches     |-- tags     `-- trunk         |-- module1         |   `-- pom.xml         |-- modulen         |   `-- pom.xml         `-- pom.xml         |         `-- docs 

Comments

Popular posts from this blog

html - How to style widget with post count different than without post count -

How to remove text and logo OR add Overflow on Android ActionBar using AppCompat on API 8? -

javascript - storing input from prompt in array and displaying the array -