Skip to main content
Main menu
AMS Cloud Status
Product Info
Community
Contact Us
Mailing List / RSS Feed
Privacy Policy
Search form
Search
Installing Theatre Manager
Upgrading Theatre Manager
Quick Reference Guides
Self-Guided Demo Tutorial
Theatre Manager Online Help
Form Letters and EBlasts
Facility Management
Reports
Reveal Dashboards
REST API Overview
Web Page Documentation
Frequently Asked Questions
Theatre Manager: Responding to COVID 19
Newsletters
2010 - CAMT Survey Results: Theatre Manager is used by a lot of people who like it
2010 - December 2010 Newsletter
2010 - June 2010 Newsletter & Announcing Version 9
2015 - Google dropping support for XP, Vista, OSX 10.8
2016 - First National Theatre Manager User Conference
2017 - Offsite Backups are a key way to thwart recent Ransomware viruses
2017 - Second National Theatre Manager User Conference
2018 - Third National Theatre Manager User Conference
Training Curriculum's
ams
Human Resource's Policies
AMS Private Cloud
Exceptional Customer Support
FogBugz Issue Management (Change Control)
Product Development Process
Defect Tracking Process
Version Control
GIT Repository
Omnis Studio VCS
Branches
Getting Source
Get Latest Revisions
Comparing Revisions
Checking Out
Checking In Changes
Current Responsibility Matrix
Software Development Lifecycle
TLS Certificates
Coding Practices
Data Importing
Misc Support TechNotes
PA DSS 3.2.1 Documentation Index
Legacy Support Pages
AMS Cloud Status
Product Info
Community
Contact Us
Mailing List / RSS Feed
Privacy Policy
You are here
Home
›
Newsletters
›
ams
›
Product Development Process
›
Version Control
Omnis Studio VCS
The features of the Omnis VCS are described in the Omnis Developer Manual. The key ways that we use it are described in the following sections.
Branches
Getting Source
Get Latest Revisions
Comparing Revisions
Checking Out
Checking In Changes
‹ GIT Repository
up
Branches ›
Printer-friendly version
