Mark - Again - Thanks so much for your insight. With your information and a little more googleing I was able to get things going. I am using TortoiseSVN as the client, and when I try to TAG the revision as OMP1.00 I am getting an error saying invalid tag. I guess I can have the version in the description though.
Can I ask what client you use? /Henrik On Feb 22, 12:59 am, "Cooke, Mark" <[email protected]> wrote: > > -----Original Message----- > > From: [email protected] > > [mailto:[email protected]] On Behalf Of Henrik Helgesen > > Sent: 22 February 2011 08:49 > > To: Trac Users > > Subject: [Trac] Re: Using 'Browse Source' > > > 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? > > Strictly speaking this is a subversion usage question, not Trac. Have you > used source code control before? The outline way to do what I think you want > is: > > 1) create one repository > 2) check out the empty repository to a local "working copy" (WC) > 3) Copy your earliest release files into your WC directory > 4) use subversion tools to add all the required files > 5) commit your WC to the repository > 6) "tag" the release using your desired name (e.g. 'OMP1.05') > 7) copy the source files for the next version over your WC > 8) use svn tools to add any new files/folders and remove any > no-longer-required files > 9) commit & tag again... > Repeat 7..9 until you have added all your source files into the repositories > history > > Finally, go back to trac and do a resync against your one repo and the > history should appear. > > Are your release files already in source control? Or do you just have zip > (or similar) archives? If the former you may be able to use a tool to > convert the whole history to svn... Anyway, check out the subversion book > (http://svnbook.red-bean.com/) and the mailing list > (http://groups.google.com/group/subversion_users) and archive > (http://svn.haxx.se/users/) for more information... > > ~ mark c -- 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.
