Get in Touch

Course Outline

Subversion design philosophy and its advantages

  • Understanding the typical copy-modify-merge workflow and techniques for resolving simple conflicts.
  • Establishing user policies and guidelines to ensure smooth and consistent team collaboration.
  • Implementing the lock-and-unlock mechanism as a complement to the copy-modify-merge method.

Branching and merging

  • Determining when to create branches and exploring various use cases for them.
  • Effectively resolving conflicts and merging changes, including strategies for absorbing modifications from different directions.
  • Leveraging newer Subversion features to streamline branching and merging processes.
  • Guiding users on when to encourage or discourage local branching practices.

Daily digests and revision reviews

  • Utilizing mailing lists, RSS feeds, and digest tools for updates.
  • Performing blame analysis and managing delegation of tasks.

Subversion properties

  • Overview of built-in properties, properties with SVN-prefixed keywords, and global properties.
  • Best practices for designing and implementing these properties.
  • Creating custom Subversion properties tailored to organizational needs.
  • Innovative applications of customized Subversion properties.
  • Awareness of the limitations and constraints of Subversion properties to avoid over-engineering.

Subversion hooks

  • Classification of different hook types.
  • General usage patterns for hooks that ship with Subversion.
  • Development of self-defined hooks for specific requirements.
  • Fostering creativity in the application of hooks for automation and control.

Secondary Subversion servers

  • Setting up secondary servers for backup and fail-safe recovery.
  • Utilizing secondary servers for automatic background tasks.
  • Managing temporary arrangements, such as support for distributed locations.

Integration with other tools

  • Integration with issue tracking systems such as Bugzilla, Track, and Jira.
  • Connecting with content management systems, including wikis.

Requirements

  • Strong proficiency in SVN is required.
  • Participants are preferably expected to have completed the Subversion for Administrators and Subversion for Users courses.
  • This course can be condensed into a one-day format with reduced exercise content, which may also adjust the fee structure.
 14 Hours

Testimonials (2)

Related Categories