On Thu, 16 Mar 2006 23:53:56 -0300 "Julio Nobrega" <[EMAIL PROTECTED]> wrote:
> > Hey tone, > > Eric provided a good explanation of what's like working with svn. I > would like to comment a little on point number 3. > > Having everything on svn helps us on deployment too. Most software > management tips will tell you to compile your code daily. Because it > gives the development team a clear goal and discourages them to commit > bugged code. > > Here's what happens where I work: QA approves the 'build' (a svn > revision), and a Python script that I made checkout this code, removes > the .svn directories, Actually, if you do ``svn export http://path.to.svn.server/path/to/repository/`` it'll strip out all the .svn cruft for you. When I get ready to do a release (not at work, we have different procedures here), I stop working on the branch I'm no, ``svn copy`` to a new branch, and ``svn export`` the finished branch. I'm thinking of changing my release procedures and branching to a "release" branch and exporting from there.... - jmj --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users -~----------~----~----~----~------~----~------~--~---
