Am 22.02.2011 um 09:48 schrieb Henrik Helgesen: > On Feb 22, 12:40 am, Christian Aust <christian.a...@software- > consultant.net> wrote: >> Am 22.02.2011 um 09:28 schrieb Henrik Helgesen: >> >>> I was hoping I could use this to let SOX Auditors look in the source >>> code, and see the differences between released versions. >> >> Should be possible. >> >>> I created a Repository for each version and uploaded my source code >>> files into the directories specified. However when trying to browse >>> and select a version, I get the "No node at revision 0" error. >> >> Did you actually create a separate repository for each version, instead of >> using svn tags within the same repository? > > Henrik: Yes I did - I am new to this, so if that is not the best way > of doing it, I am open to changing that ;) - Can you set your own > revisions i'e' OMP1.05, OMP1.05.01, OMP1.06?
Please see svn documentation on "branching and tagging", which basically allows you to keep track of full configurations efficiently. http://svnbook.red-bean.com/nightly/en/svn.branchmerge.commonpatterns.html#svn.branchmerge.commonpatterns.release This is a key concept of using SCM in general, so you should become familiar with it. trac fully supports diff'ing whole trees, so your auditors will be able to spot every single change from one release to another. Kind regards, Christian -- You received this message because you are subscribed to the Google Groups "Trac Users" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/trac-users?hl=en.
