It's usually a nagging question at work or a random idea that gets me writing these app-a-weekends. This one's partially in response to the question I get from QA folks (and business people) - "What's in this build?"

Towards generating "Change Log" notes, here's yet another winforms app - this time to view svn logs. The interesting thing about this one is that I sort of used a scrum-of-one for it: I defined backlogs, defined tasks for those backlogs and have been executing on them.

First, the app's goal: to make a stand alone svn log viewer that could output comments nicely to produce the beginnings of a "Change Log" for various apps. It needs URL persistence and the ability to display svn's logs nicely. Apart from the "Change Log" generation, QA folks at work want to know what's in different builds.

To perform the actual svn log command, the app calls out to the command line svn.exe, which I downloaded from Collabnet.


  1. List log differences btw svn revisions
    1. call svn
    2. toggle verbose
  2. Manage list of svn repositories
    1. add repository urls and nicknames
    2. save
    3. recall
    4. view in grid
    5. edit
  3. Display nicely
    1. raw text format
    2. as grid view
  4. Export nicely
    1. save as text
    2. save as Word 2007
    3. save as Excel 2007
  5. Tie up loose ends
    1. warn if svn.exe is missing

Over the weekend I started the app, did all of 1 (1.1, 1.2), some of 2 (2.1, 2.2, 2.3), and 3.1.

Tonight I did 2.4.

My backlog is:
3. 2. Display : In Grid
4. 1. Save : As Text
5. 1. Loose: Check for Svn
2. 5. Svn List: Edit

If I really wanted to push the "app-a-weekend" thing, I could throw in an msi and a chm help file. Other things that would make this a more useful concept are if this was tied in to a particular projects tag-numbering scheme and if it was a webpage, so that the users didn't need to install an app. Refactoring the final product into libraries for use in a web app should do the trick.