svn add command!

This is just a quick rant to say:

The svn add command exists for a reason.
Learn it, use it, love it!

I went into work for a few hours today as we have a rather pressing deadline for the current project and it would be nice to get stuff finished on time to allow for some testing. After making a bunch of changes to the code that I was working on I was ready to compile and give it a test. I decided to do the prudent thing and update my local copy so that I coud test what I had done with the latest version of the project.

Unfortunately someone(s) else had incompletely checked in some work since my last update. I say incomplete because they had obviuosly created new files and the VS.NET project file had references to where they should be, but they didn’t exist in the repository.

After some carefully thought out exclusions in the solution and a quick informative email later I was able to get my changes to compile. Even though I have not completed what I was working on, and hence not checked it back in I emailed the other developers to let them know what I had done (the exclusions) and why I had done it. Obviously excluding someone elses work from a project solution is not the best thing to do when there are tight deadlines. I didn’t want the things that I had excluded to become overlooked simply because the original developer(s) thought that they were now complete.

If we were running test driven development that would not be a problem as it would be caught in the next build and test phase, however we have not yet reached that point of restructure of our methodologies.

1 Comment »

  1. Alistair Said,

    January 24, 2006 @ 10:15 pm

    It’s coming Jacob, have faith. The difference in Phase II compared to the original work completed for Phase I by unnamed developers is a world apart. I can’t wait for the next iteration of our Best Practice to kick in, it’s going to be very exciting!

    Al.

RSS feed for comments on this post · TrackBack URI

Leave a Comment