Typical Workflow – Using Subversion for Revision Control

Use the following general procedure when using Subversion for software version control:

Setting up the Software Version Control System for use with ASCET:

Check the ASCET database or workspace for SCM Source Configuration Management, a general term for versioning of software elements and their relationships. compatibility

Set up an ASCET – Subversion Connection

Select an existing repository

Handling items:
Check out items
Lock items
Edit items in ASCET‑MD and/or update items
Commit your changes
For items that still need to be brought under version control, the typical "handling items" part of the workflow comprises the following steps:
Add and commit items
Check out items for editing
Lock items
Edit items in ASCET‑MD and/or update items
Commit your changes

Note
When items are checked out, updated or committed while opened in an editor, the editor will be closed and reopened after the process.