Where should unstructured files be committed in SVN? -
i realize purpose of svn store structured files application or other purpose have standard names, , updates these files committed, becoming revisions.
we know files in svn typically environment agnostic. i'm defining environment dev, qa, uat , prod. suppose mix qa , uat "unstructured" files this, , want keep track of qa scripts, qa automation scripts, screen shots, proposed documentation defects fixed, business requirements piece of development, etc..? essentially, want place store these unstructured files. in structure below store such thing, or not recommended?
since branches smaller project work (or task work) within larger project (or application), store pieces of development within branch sub-folder. trunk stable version of what's in production, right? in past, i've heard tags deployment , rollback scripts should live, , @ point in past, more or less static. i'm thinking either put these unstructured files in branches or tags.
the reason "unstructured" because may have qa screen shots may different each piece of development , might become obsolete later on. don't want check these trunk after development, during development, screen shot may change new development changes checked branch before branch stable, may want overwrite screen shot newer screen shot. also, test scripts change development changes. have business requirements development, test plans dev , qa, test results dev , qa, descriptions of defects found before development, , descriptions of fixes defect development, etc...
here structure have:
\app \app\trunk\ \app\trunk\file_x \app\branches\ \app\branches\yyyy-mm-dd_branch_x\file_x \app\tags\
documentation's files , tests candidates content of separate tree in repo (shared app-sources or external, linked app-repo svn:externals). repository may like
/trunk /tests /docs in result
other qa-work (bug-hunting) subject of (some, any, preferred) issue-tracking system: found bugs added (with descriptions, steps-to-reproduce, screenshots), can discussed in ticket's comments, have related bug commits (linked tickets also)
Comments
Post a Comment