CollabNet founded the Subversion open source project. Because many of the Subversion features are still developed by Subversion committers employed by CollabNet, the company has collected the broadest and deepest knowledge base available around Subversion. This expertise can be rapidly transferred to your teams through CollabNet's Support, Training, and Consulting services.
Subversion Implementation Lifecycle
Whether you've already deployed Subversion to some projects or are just getting started with Subversion, CollabNet's consultants can advise you in planning the roll out of Subversion into your organization, guide you through the deployment, configuration and migration of artifacts into Subversion, train developers during the rollout and finally assess your overall use of Subversion.
Plan & Align
Deploy
Migrate and Adopt
Subversion Applied Workshop
Workshop focused on formulating your organization's needs for version control and configuration management and how to best utilize Subversion to meet those needs. Covers the following topics: Repository Layout, Branching Patterns, Tagging, Access Control, Release Management, Workspace Management. Action taken:
Examine your current software development and release management needs
Establish best practices on the use of Subversion that meet your needs
Subversion Server Configuration and Administration
Advice and assistance in setting up, administering and maintaining a Subversion server. We can assist in setting up your Subversion server environment or assess an existing environment. Covers the following areas:
Hardware, software and network requirements and recommendations
Migrations from Legacy Systems
We provide advice and assistance in migrating version control data from legacy systems into Subversion. Our migration services cover the execution of full history conversions from CVS and VSS repositories as well as advice in migrating from other version systems. Action taken:
Migrate valuable legacy version control data to Subversion
"After careful evaluation, we migrated our entire development organization to Subversion. Subversion has been incredibly easy to deploy; best of all, we accomplished this with zero impact to our delivery schedules."
—Ron Sheen, CTO of Fujitsu Siemens Computers
Applied Workshop
A four day engagement involving a two day onsite workshop with up to (5) architects, configuration managers, and senior software engineers with the purpose of aligning the organization's software development process to its use of Subversion. During the workshop, use cases and software development processes will be formulated which will then be mapped into Subversion best practices.
Among others, the workshop covers topics such as:
Repository layout
Branching patterns
Tagging: How to deal with internal and external releases
Access control
Release management: How does one team pick up the changes from another
Workspace management: How should developers manage their local workspace
At the end of the Workshop, recommendations will be provided to help organize your software development processes using Subversion.
A five day engagement involving a two day onsite workshop focused on helping an organization assess its need to migrate legacy version control data, define what data can and should be migrated, and plan the migration process. The tasks to be completed are as follows:
Environment assessment: For each legacy system, we will assess the environment to inventory data that can and cannot be migrated to Subversion
Needs analysis: We will assess specific software development projects to understand the need for migrating version control data from the legacy system. We will help you identify and quantify the business value of the data to be migrated and provide you with advice on the technical limitations with migrating and mapping data into Subversion
Planning: We will schedule preparatory test runs of the data migration using representative project data. We will advise on whether to continue software development during the migration process or whether shutdown development while you migrate data. If software development continues, we'll help you assess the costs and benefits of synchronizing the legacy system with Subversion for that limited amount of time.
At the end of the Workshop, a document will be provided listing recommendations on what data to migrate from the legacy system as well as how to plan and execute the migrations to Subversion
Configuration and Administration of a Subversion Server
Advice and assistance in setting up, administering and maintaining a Subversion server. We can assist in setting up your Subversion server environment or assess an existing environment.
These services are tailored to the organization's needs and often include the topics described below.
Assessment and recommendation on the server hardware, network connectivity, and server software configuration that is best suited for the anticipated load and the customer's computing environment
Definition and implementation of an authentication and authorization scheme to be maintainable and manageable. If applicable, assistance will be provided for setting up authentication against an external authentication source such as Microsoft Active Directory or LDAP.
Configure audit trails using Subversion's logging capabilities
Define and set up of a backup and recovery approach that integrates with the customer's existing backup solution
Assistance and advice on how to integrate and connect external tools and scripts such as build and test environments to Subversion
We provide advice and assistance in migrating version control data from legacy systems into Subversion. Our migration services cover the execution of full history conversions from CVS and VSS repositories as well as advice in migrating from other version systems. Action taken:
Migrate valuable legacy version control data to Subversion
A five day engagement involving a two day onsite workshop with architects, configuration managers, and senior software engineers with the purpose of assessing the use of Subversion. We examine how well the best practice established during the planning phase (with the Applied Workshop) has been followed and adjust/fine-tune recommendations to cater to the changing needs of the organization.
Among others, the workshop covers topics such as:
Repository layout
Branching patterns
Tagging: How to deal with internal and external releases
Access control
Release management: How does one team pick up the changes from another
Workspace management: How should developers manage their local workspace
At the end of the assessment, a document will be provided with the evaluation findings as well as the recommendations on changes and adjustments to current processes, practices and policies.
China
Korea
Japan
Learn more
CLOSE