From Subversion 1.4 to Subversion 1.5

Last week, we upgraded our development environment from Subversion 1.4 running on Apache 2.0 to Subversion 1.5 running on Apache 2.2. The primary reason for this upgrade is the support of relative URLs in the svn:externals property introduced in the new version of Subversion. 

The upgrade process was smooth and easy. Here are the steps we followed:   

  1. Stopped our existing Apache Server
  2. Backed up our Subversion repository 
  3. Downloaded and installed Apache 2.2.9
  4. Downloaded and installed Subverstion 1.5.2
  5. Configured httpd.conf configuration file for our new Apache server and started the server
  6. Upgraded our repository by executing svnadmin upgrade
  7. Upgraded our indexes by executing svn-populate-node-origins-index
  8. Upgraded client tools - we installed Tortoise 1.5.3 and Ankh 2.0
  9. Upgraded Team City automated build and continuous integration server to the latest version 3.1.2
A couple of notes... 
  • In the past, in order to use Windows authentication with Subversion we had to write a custom We did not have to do anything for 1.5. Loading modules in the correct order and referencing them from the Subversion application folder did the trick for us:     
LoadModule sspi_auth_module modules/
LoadModule dav_module modules/
LoadModule dav_svn_module C:/Apps/svn-win32-1.5.2/bin/
LoadModule authz_svn_module C:/Apps/svn-win32-1.5.2/bin/               
<Location /svn>
DAV svn
SVNPath C:\Dev\Repository

     AuthName "SVN Server"
     AuthType SSPI
     SSPIAuth On
     SSPIAuthoritative On
AuthzSVNAccessFile "C:/Repository/conf/authz"
     SSPIOfferBasic on
     Require valid-user     

  • Team City 3.1.2 does support Subversion 1.5, but unfortunately does not support relative URL's in the svn:externals property. 

August book review: Toyota Talent

Jeffrey Liker and David Meier
Toyota Talent: Developing Your People The Toyota Way

I am leading a product development team at a financial organization. One of my objectives is to create an environment supporting and motivating team members to learn all jobs within the team and continuously improve our work methods. This may not be an easy goal to achieve, but I see a huge value in having team members capable of performing multiple jobs and willing to assume different roles and responsibilities.  

While I was exploring ideas on how to organize training and skill development for our employees, I came across Jeffrey Liker's and David Meier's book describing an approach to training used by Toyota. At Toyota, managers and team leaders are responsible for establishing a teaching environment within their teams. They create development plans for their team members, work closely with the trainers to evaluate the progress and skill level of each individual, and keep an eye on the overall performance indicators.

Jeffrey and David provide excellent ideas on how to identify critical knowledge, analyze and standardize work methods, break down jobs into small pieces for teaching, run training sessions, and follow up to verify the results. Even though the approach described in the book is targeted towards manufacturing, I found it to be applicable (with little adaptation) to product development and engineering. 

Happy reading!

Welcome to ModelBlog

Thank you for visiting ModelBlog. We hope the time you spend with us will be both entertaining and worth your while. Have fun!