Join in our interactive Bloodhound session and get an update on the Apache Bloodhound project, discuss some of the key features we think sets Bloodhound aside from Trac and other defect tracker/requirements capture tools currently in existence, get an insight into where we would like to take the product and how you can contribute to its success.

Apache Bloodhound is an OpenSource tool for managing software development. Its strengths lie in a close tie in between Subversion source control and a powerful ticket system, built on the shoulders of Trac. Bloodhound develops the core Trac principles and builds on them to create a quick setup/install process, cleaner user experience and more approachable interface without compromising an organisation's need to evolve. In this session we'll discuss key UI and functional differences between Bloodhound and Trac, using Bloodhound within your Subversion ecosystem, users, projects, groups & Permissions and general ticket management.

Branching and merging can make development easier and more controllable but these must be done with a plan.

In order to take full advantage of the power of Subversion you need to use branches as part of development. This talk will discuss how branches and merging should be implemented as part of your development strategies and the benefits of having a branch plan. Learn how other companies use branches and several techniques to minimize the issues of forgotten branches and difficult conflicts.

• Different branches for different purposes
• Tracking branch usage, make it part of your project plans
• When to merge
• Actively avoiding conflicts

Learn about hidden gems and the latest improvements.

Subversion clients are constantly improving and often add functionality that is not delivered by the core project. New developments allow you to use Subversion similar to Dropbox, other very useful features have been present for a while now but are not known to most users. This talk will show you how those hidden gems and new capabilities can make your users even happier.

Focusing mainly on TortoiseSVN, there will also be a quick look at the "best" clients available on your favorite OS.

This session discusses the criticality of the tooling selection process when building an organisation's Application Lifecycle and how the application marketplace has evolved since we last discussed this topic.

In a crowded app/plugin marketplace it can be difficult to know what specific tools you need, to take your software idea to a fully tested and deployed application. We recognise that organisations need to build a strong set of tools, maintaining standards and control at the core of the Application Lifecycle whilst allowing the toolset to easily expand and contract on a per project basis. In this session we discuss the various steps in the Application Lifecycle and appropriate Opensource tools at each stage. By the end of the session attendees will be equipped to know how to create the right ecosystem for a project that matches the organisation's working methodology and culture. This session will focus on specific case studies, provide details of how the tools compliment each other and how they all integrate with Subversion.

Exploring the design of a symmetric merge algorithm to make to-and-fro merging simpler.

Subversion's automatic merge tracking comes into play in the 'sync' merge from parent branch to child branch and in the 'reintegrate' merge in the other direction. But if you want to continue making changes on both branches, and merging those changes to-and-fro, Subversion currently requires extra effort from the user. Why is that?

With clear graphical explanations, we demonstrate and contrast the operation of sync and reintegrate merges. We then explore the design of a symmetric merge algorithm and show how it makes to-and-fro merging simpler.

Tracking renames to automatically resolve tree conflicts during update and merge.

Tracking renames in the working copy to automatically resolve tree conflicts during update. Identifying renames in the repository to automatically resolve tree conflicts during merge.

Branching and merging can make development easier and more controllable but these must be done with a plan.

In order to take full advantage of the power of Subversion you need to use branches as part of development. This talk will discuss how branches and merging should be implemented as part of your development strategies and the benefits of having a branch plan. Learn how other companies use branches and several techniques to minimize the issues of forgotten branches and difficult conflicts.

• Different branches for different purposes
• Tracking branch usage, make it part of your project plans
• When to merge
• Actively avoiding conflicts

Exploring the design of a symmetric merge algorithm to make to-and-fro merging simpler.

Subversion's automatic merge tracking comes into play in the 'sync' merge from parent branch to child branch and in the 'reintegrate' merge in the other direction. But if you want to continue making changes on both branches, and merging those changes to-and-fro, Subversion currently requires extra effort from the user. Why is that?

With clear graphical explanations, we demonstrate and contrast the operation of sync and reintegrate merges. We then explore the design of a symmetric merge algorithm and show how it makes to-and-fro merging simpler.

Learn about hidden gems and the latest improvements.

Subversion clients are constantly improving and often add functionality that is not delivered by the core project. New developments allow you to use Subversion similar to Dropbox, other very useful features have been present for a while now but are not known to most users. This talk will show you how those hidden gems and new capabilities can make your users even happier.

Focusing mainly on TortoiseSVN, there will also be a quick look at the "best" clients available on your favorite OS.