The Vertical Sky Software Manager User Guide - MKS

Vertical Sky Software Manager 

USER GUIDE 

> > > > > > > > > > > > > >

Vertical Sky Software Manager 

USER GUIDE 

© Copyright (2000) Vertical Sky Canada Inc. (in Canada) 

© Copyright (2000) Vertical Sky International SRL (worldwide except Canada) 

Vertical Sky Evolution Management Solution, Vertical Sky Server, Vertical Sky Software Manager, Vertical Sky 

Collaboration Manager, Vertical Sky Content Manager are trademarks of Vertical Sky Inc. All rights reserved. 

All other trademarks or registered trademarks are the property of their respective holders. 

Contains Java software developed by Sun Microsystems, Inc. © Copyright Sun Microsystems, Inc. All Rights Reserved. 

Java and Java-based marks are trademarks or registered trademarks of Sun Microsystems, Inc. in the United States and 

other countries. 

Portions of this product are based upon copyrighted materials of BEA Systems Inc. All rights reserved. 

Portions of this product are based upon copyrighted materials of KL Group or its suppliers. All rights reserved. 

IBM Bean Scripting Framework (BSF) is incorporated in this product and is provided by International Business Machines 

or one of its subsidiaries (IBM) and is copyrighted and licensed. Vertical Sky Canada Inc. does not make or imply any 

representations or warranties on behalf of IBM. 

Mozilla Public License. The Source Code version of the Covered Code is available under the terms of the Mozilla Public 

License Version 1.1. 

> CORPORATE HEADQUARTERS 

Vertical Sky Incorporated 

2500 S. Highland Ave. 

Lombard, IL 60148 

tel: 630 495 2108 

fax: 630 495 3591 

sales: 800 633 1235 

www.VerticalSky.com 

> > > > > > > > > > > > > > 

8.0a-D293-1200 

Worldwide Offices: 

> CANADA 

tel: 519 884 2251 

fax: 519 884 8861 

sales: 800 265 2797 

> GERMANY 

tel: +49 711 351775 0 

fax: +49 711 351775 11 

> UK 

tel: +44 1483 733900 

fax: +44 1483 733901 

sales: +44 1483 733919 

> BARBADOS 

tel: 246 228 4217 

fax: 246 437 8223

Contents 

Chapters 1 Welcome to Vertical Sky Software Manager . . . . . . . . . . . 1 

The Vertical Sky Software Manager User Guide . . . . . . . . . . . 2 

Typographical Conventions . . . . . . . . . . . . . . . . . . . . . . . . 3 

Related Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 

Assumptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 

Getting Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 

2 Starting a Vertical Sky Software Manager Session . . . . . 7 

Before You Start 

the Vertical Sky Software Manager Client . . . . . . . . . . . . . . . . 8 

Starting the Vertical Sky Software Manager Client . . . . . . . . 8 

Graphical User Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 

Application Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 

Registered Projects and Registered 

Sandboxes Dialog Boxes . . . . . . . . . . . . . . . . . . . . . . . . . . 14 

Project and Sandbox Windows . . . . . . . . . . . . . . . . . . . . . 15 

Member History Window . . . . . . . . . . . . . . . . . . . . . . . . . 18 

Project History Window . . . . . . . . . . . . . . . . . . . . . . . . . . 19 

Using Filters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20 

Command Line Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21 

Viewing Available Commands . . . . . . . . . . . . . . . . . . . . . 21 

Using the Graphical User Interface . . . . . . . . . . . . . . . . . 22 

Command Prompts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22 

Member Name Arguments . . . . . . . . . . . . . . . . . . . . . . . . 22 

Logging In . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24 

Setting Preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26 

Quitting a Vertical Sky Software Manager Session . . . . . . . . 41 

Logging Out . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41 

Quitting a Session . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42 

3 Getting Started With Projects, Sandboxes, 

and Members . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45 

Creating a Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46 

Importing a Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47 

Creating a Sandbox . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48 

Importing a Sandbox . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54 

Dropping a Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55 

> > > > > > > > > > > > 

i

Contents 

Dropping a Sandbox . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57 

Opening or Viewing a Project . . . . . . . . . . . . . . . . . . . . . . . . . . 58 

Opening or Viewing a Sandbox . . . . . . . . . . . . . . . . . . . . . . . . 60 

Adding Members to a Project . . . . . . . . . . . . . . . . . . . . . . . . . . 62 

Selecting Members . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66 

Removing Members From a Project . . . . . . . . . . . . . . . . . . . . . 68 

Creating a Subproject . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69 

Variant Sandboxes and Development Paths . . . . . . . . . . . . . . 71 

Creating a Development Path . . . . . . . . . . . . . . . . . . . . . . 72 

Removing a Development Path . . . . . . . . . . . . . . . . . . . . . 73 

Build Sandboxes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74 

Checking Out a Member . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75 

Viewing and Editing a Member . . . . . . . . . . . . . . . . . . . . . . . . 78 

Scanning Your Sandbox for Changes . . . . . . . . . . . . . . . . 79 

Checking In a Member . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80 

Starting a Branch When Checking In a Member . . . . . . . 81 

Assigning Revision Numbers . . . . . . . . . . . . . . . . . . . . . . 81 

Assigning Revision Descriptions . . . . . . . . . . . . . . . . . . . . 82 

Comparing a Member’s Working File to Its 

Member Revision . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85 

Discarding Changes 

to Member Working Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87 

Resynchronizing Members . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88 

Locking a Member . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89 

Unlocking a Member . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90 

Using Keywords . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91 

Locating Keywords . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93 

Table of Keywords . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94 

4 Managing Projects, Sandboxes, and Members . . . . . . . 95 

Viewing and Editing Project Information . . . . . . . . . . . . . . . . 96 

Viewing and Editing Project Attributes . . . . . . . . . . . . . . 97 

Viewing and Editing Development Path Information . . 97 

Viewing Sandbox Information . . . . . . . . . . . . . . . . . . . . . . . . . 99 

Viewing a Project History . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102 

Viewing and Editing Member Information . . . . . . . . . . . . . 103 

Viewing and Editing Member Attributes . . . . . . . . . . . 104 

Viewing and Editing Member Labels . . . . . . . . . . . . . . . 105 

Updating a Member’s Revision . . . . . . . . . . . . . . . . . . . . . . . 107 

Adding Labels to Members . . . . . . . . . . . . . . . . . . . . . . . . . . . 109 

Deleting Member Labels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110 

Adding Labels to Projects . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112 

Deleting Project Labels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113 

ii > > > > > > > > > > > > > >

Contents 

Promoting Members . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113 

Demoting Members . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115 

Promoting a Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116 

Demoting a Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117 

Freezing Members . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119 

Thawing Members . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120 

Checkpointing a Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121 

VSky Software Manager Reporter . . . . . . . . . . . . . . . . . . . . . 124 

About the Report Information . . . . . . . . . . . . . . . . . . . . 124 

About Graphs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125 

Report Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125 

Creating a Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128 

5 Managing Member Histories and Revisions . . . . . . . . . 131 

Viewing a Member History . . . . . . . . . . . . . . . . . . . . . . . . . . 132 

Viewing and Editing Archive Information . . . . . . . . . . . . . 133 

Viewing and Editing Revision Information . . . . . . . . . . . . . 135 

Viewing and Editing Revision Labels . . . . . . . . . . . . . . 137 

Adding Labels to Revisions . . . . . . . . . . . . . . . . . . . . . . . . . . 139 

Deleting Revision Labels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140 

Viewing a Member’s Working File or Revision . . . . . . . . . . 141 

Promoting Revisions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143 

Demoting Revisions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144 

Locking Revisions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145 

Unlocking Revisions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146 

Setting the Member Revision . . . . . . . . . . . . . . . . . . . . . . . . . 148 

Deleting Revisions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149 

Comparing Revisions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151 

Merging Revisions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153 

6 Vertical Sky Software Manager Integrations . . . . . . . . . 155 

Introducing Vertical Sky Software Manager Integrations . 156 

Using Integrations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157 

Microsoft Visual Basic 5.0 and 6.0 Integration . . . . . . . . . . . 158 

Creating a Vertical Sky Software Manager Project . . . 160 

Creating a Sandbox . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161 

Adding Members to a Project . . . . . . . . . . . . . . . . . . . . . 161 

Checking Out Members . . . . . . . . . . . . . . . . . . . . . . . . . . 161 

Checking In Members . . . . . . . . . . . . . . . . . . . . . . . . . . . 162 

Microsoft Visual C++ 5.0 and 6.0 Integration . . . . . . . . . . . 162 

Creating a Vertical Sky Software Manager Project . . . 165 



> > > > > > > > > > > > iii

Contents 


Checking In Members . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167 

Microsoft Visual J++ 6.0 Integration . . . . . . . . . . . . . . . . . . . 167 

Creating a Vertical Sky Software Manager Project . . . . 169 




Checking in Members . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171 

Sybase PowerBuilder 7.0 Integration . . . . . . . . . . . . . . . . . . . 171 






Borland JBuilder 3.0 Integration . . . . . . . . . . . . . . . . . . . . . . . 174 





Checking in Members . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178 

WebGain VisualCafé 4.0 Integration . . . . . . . . . . . . . . . . . . . 179 






IBM Visual Age for Java 3.5 Integration . . . . . . . . . . . . . . . . 184 






Rational Rose 2000 Integration . . . . . . . . . . . . . . . . . . . . . . . . 189 






Starbase CodeWright 6.5 Integration . . . . . . . . . . . . . . . . . . . 193 




iv > > > > > > > > > > > > > >

Contents 


Checking In Members . . . . . . . . . . . . . . . . . . . . . . . . . . . 196 

7 Integrated Version Control . . . . . . . . . . . . . . . . . . . . . . . 197 

Adding Members to an Issue’s Change Package . . . . . . . . 198 

Viewing Change Packages in Vertical Sky 

Software Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 206 


Collaboration Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 210 

8 Glossary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213 

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 219 

> > > > > > > > > > > > v

Contents 

vi > > > > > > > > > > > > > >

Welcome to 

Vertical Sky Software 

Manager 

1 

Vertical Sky Software Manager is a comprehensive, projectoriented 

configuration management system that gives you control 

over the evolution of your files. It not only documents the changes 

made to your files, but also tracks who made them, when they were 

made, and the reasons why. 

In addition, its project functionality lets you group related files into 

projects that can follow your development cycle. VSky Software 

Manager includes extensive configuration options to provide 

configuration management that conforms with your established 

policies. 

Whether you work on one-person projects, or in multipleprogrammer 

development environments, VSky Software Manager 

has the features to help you get the job done. Its function set and 

project-oriented client/server architecture are available in both 

command line and graphical user interfaces. 

Briefly, there are two main roles when using VSky Software 

Manager: the administrator and the user. 

The administrator installs VSky Software Manager; defines and 

customizes projects and policies; and creates and manages user 

accounts, allowing users to access the program. 

A user is anyone who needs to work with VSky Software Manager 

projects. 

The Vertical Sky Software Manager User Guide provides details on the 

user role and explains how to approach the day-to-day tasks in 

VSky Software Manager. 

> > > > > > > > > > > > 1

Welcome to Vertical Sky Software Manager 

The Vertical Sky Software Manager User 

Guide 

This chapter introduces you to Vertical Sky Software Manager User 

Guide and its contents. The following is a list of the guide’s other 

chapters with a brief description of each chapter’s topic: 

Chapter 2: “Starting a Vertical Sky Software Manager 

Session” on page 7 

Describes starting the VSky Software Manager Client, the 

VSky Software Manager graphical user interface, the 

VSky Software Manager command line interface, logging in, 

setting preferences, logging out, and quitting a VSky Software 

Manager session. 

Chapter 3: “Getting Started With Projects, Sandboxes, and 

Members” on page 45 

Describes the basic tasks to work with projects, sandboxes, and 

members, for example, creating a sandbox, adding members, 

and checking out members for editing. 

Chapter 4: “Managing Projects, Sandboxes, and Members” 

on page 95 

Describes how to manage projects, sandboxes, and members, 

for example, viewing and editing project information, adding 

labels to projects, and freezing members. 

Chapter 5: “Managing Member Histories and Revisions” on 

page 131 

Describes how to manage member histories and revisions, for 

example, viewing and editing revision information, deleting 

revisions, and promoting revisions. 

Chapter 6: “Vertical Sky Software Manager Integrations” on 

page 155 

Explains how to integrate VSky Software Manager with a 

number of popular programming environments, including 

Borland JBuilder, Sybase PowerBuilder, Microsoft Visual Basic, 

Microsoft Visual J++, Microsoft Visual C++, WebGain 

VisualCafé 4.0, IBM Visual Age for Java 3.5, Rational Rose 2000, 

and Starbase CodeWright 6.5. 

2 > > > > > > > > > > > > > >

Typographical 

Conventions 

Related 

Documentation 

The Vertical Sky Software Manager User Guide 

Chapter 7: “Integrated Version Control” on page 197 

Describes adding project members to an issue’s change 

package in VSky Software Manager, and viewing change 

package information in VSky Software Manager and 

VSky Collaboration Manager. 

Appendix : “Glossary” (page 213) 

Provides a glossary of common terms and definitions for 


Throughout the manuals, the following typographical conventions 

identify the features, functions, and components of VSky Software 

Manager. 

Items in documentation Appear as follows 

Menus, commands Tools > Preferences 

Graphical user interface 

commands 

Command line commands si ci 

the Member command 

Dialog boxes, features Demote Member, Cancel, OK 

Screen information, messages Enter a name for this 

development path: 

Environment variables TMPDIR 

Path names c:\srcint\work 

VSky Software Manager terms appear in italics the first time 

Keyboard keys appear in bold between angle 

brackets, for example: 

Procedures for the graphical user 

interface and command line 

interface 

To give you the most convenient means of retrieving information, 

VSky Software Manager documentation is available in print 

(Vertical Sky Evolution Management Solution Installation only), in 

Adobe Acrobat’s Portable Document Format (PDF), and as online 

help. 

> > > > > > > > > > > > 3


Assumptions 

PDF files (located in the \admin\docs subdirectory of the 

distribution CD) are viewed with the Acrobat Reader provided 

with the distribution CD. You may install this program by running 

the setup program in the appropriate \acrobat subdirectory on the 

distribution CD. Once you have installed the Reader, it starts 

automatically whenever you open a PDF file. 

In addition to VSky Software Manager User Guide, the other 

documentation available with VSky Software Manager is as 

follows: 

Vertical Sky Evolution Management Solution Installation provides 

installation instructions for VSky Software Manager, VSky 

Collaboration Manager, and VSky Content Manager. 

Vertical Sky Evolution Management Solution Concepts provides an 

overview of VSky Software Manager, VSky Collaboration 

Manager, and VSky Content Manager concepts and features. 

Vertical Sky Software Manager Administration provides 

information on post-installation actions, and on configuring 

and administrating VSky Software Manager at your site. 

Vertical Sky Software Manager Reference provides details on the 

command line utilities included with VSky Software Manager. 

Online manual (man) pages for the command line utilities are 

available through the command line interface, using the man 

command. 

Online release notes provide the most up to date details which 

may have become available after the printed documentation 

went to press. These are simple text files that you can read with 

any editor program, such as Notepad, or as HTML documents 

that you can read with any Web browser. 

Before you use VSky Software Manager, Vertical Sky assumes that 

you have experience with the following: 

Windows (if you are using the Windows client and/or server) 

Solaris (if you are using the Solaris client and/or server) 

4 > > > > > > > > > > > > > >

Getting Help 

Getting Help 

your chosen Integrated Development Environment (IDE), for 

example, Sybase PowerBuilder (if you are using the 

integrations with VSky Software Manager) 

JavaScript (if you are working with VSky Software Manager 

event triggers) 

Vertical Sky Customer Support is ready to assist you with product 

solutions. You can choose the online system or telephone a 

Customer Support Representative. 

For online support, browse to www.VerticalSky.com and follow 

the links to the Support area. There you will find Frequently Asked 

Questions (FAQs), information about current releases, solution 

downloads, and Knowledge Base articles that can help you find the 

answers you need quickly. 

Online Web www.VerticalSky.com 

E-mail support@VerticalSky.com 

Telephone North America 800 633 6298 

630 652 9350 

UK +44 1483 733910 

Germany +49 711 351 775 0 

Fax North America 630 495 4855 

UK +44 1483 733901 

Germany +49 711 351 775 11 

> > > > > > > > > > > > 5


6 > > > > > > > > > > > > > >

Starting a Vertical Sky 

Software Manager 

Session 

2 

This chapter provides the basic steps necessary to start, configure, 

and close a Vertical Sky Software Manager session, and an 

overview of the VSky Software Manager interfaces. 

This chapter provides details on the following: 

starting the VSky Software Manager Client 

the VSky Software Manager graphical user interface 

the VSky Software Manager command line interface 

logging in to VSky Software Manager 

setting preferences 

logging out 

quitting a session 

> > > > > > > > > > > > 7

Starting a Vertical Sky Software Manager Session 

Before You Start 

the Vertical Sky Software Manager Client 

Before you start the VSky Software Manager Client, ensure you 

have the following: 

a copy of the VSky Software Manager Client installed locally 

on your computer 

the name and port number of the Vertical Sky Server you want 

to connect to 

your VSky Software Manager user name and password 

Your administrator provides you with a server name, port number, 

user name, and password. 

Starting the Vertical Sky Software Manager 

Client 

The VSky Software Manager Client is accessible in two interfaces: 

the graphical user interface and the command line interface. You 

can choose to work in one interface, or you can use both interfaces 

at the same time, because all VSky Software Manager commands 

are available in both interfaces. For example, you can perform a 

command in the command line interface and view the results in the 

graphical user interface. 

To start the VSky Software Manager Client graphical user 

interface in Windows 

Choose Start > Programs > Vertical Sky Solution > Software Manager 

(default Start menu shortcut). 

To start the VSky Software Manager Client graphical user 

interface in Solaris 

Open a command line window. 

Type si gui or si -g. 

8 > > > > > > > > > > > > > >

Graphical User Interface 

Application 

Window 

Title Bar 

Menu Bar 

Toolbar 

Sandbox 

Window 

Workspace 

Menu 

Status Bar 


To start the VSky Software Manager Client command line 

interface 

Open a command line window, such as MS-DOS or MKS 

KornShell. 

To log in, see “Logging In” on page 24. 

The application window contains a number of common features 

explained in this section. 

Menu Bar 

Filter List 

The menu bar is located directly below the title bar. Each menu 

contains available commands. When you first start VSky Software 

Manager, there are four menus in the menu bar: File, Tools, Window, 

> > > > > > > > > > > > 9


and Help. The list of available menus and commands varies 

depending on the function you are performing (for example, 

working with a member history or a sandbox). 

Toolbar 

Immediately below the menu bar is a toolbar that provides easy 

access to the most commonly used VSky Software Manager 

commands. Toolbar functions are carried out by clicking the 

appropriate toolbar button with the left mouse button. 

Most toolbar buttons only become available when an item is 

selected in a certain window. For example, selecting a project in a 

Project window displays project command toolbar buttons. 

The available toolbar buttons and their functions are: 

General Toolbar Buttons 

Toolbar Button Function 

The New Sandbox button creates a new 

sandbox. 

The New Project button creates a new project. 

The Open Sandbox button opens selected 

sandboxes. 

The Open Project button opens selected 

projects. 

The Connect button establishes a connection 

with a Vertical Sky Server. 

The Manage Sandboxes button allows you to 

manage registered sandboxes. 

The Manage Projects button allows you to 

manage registered projects. 

The Preferences button allows you to set 

session preferences. 

The Help button opens the VSky Software 

Manager online help. 

10 > > > > > > > > > > > > > >

Project Window Toolbar Buttons 

Sandbox Window Toolbar Buttons 



The Checkpoint button checkpoints the 

selected project/subproject. 

The Select button selects specific members. 

The Lock button locks selected members. 

The Unlock button unlocks selected members. 

The View Member History button displays the 

history of selected members. 

The Member Information button displays 

information about selected members. 


The Checkpoint button checkpoints the 

selected project/subproject. 

The Add Members button adds new members 

to the selected project/subproject. 

The Drop Members button removes members 

from the selected project. 

The Check Out button checks out selected 

members. 

The Check In button checks in selected 

members. 

The Resynchronize button resynchronizes 

selected members. 

The Revert button reverts selected members. 

The Edit Working File button opens the 

selected members’ working files for viewing/ 

editing. 

> > > > > > > > > > > > 11



Member History Window Toolbar Buttons 

The Differences button displays differences 

between the selected member and its working 

file. 

The Select button selects specific members. 

The Lock button locks selected members. 

The Unlock button unlocks selected members. 

The View Member History button displays the 

history of selected members. 

The Member Information button displays 

information about a selected member. 


The View/Edit Revision button opens 

selected revisions for viewing/editing. 

The View Differences button displays/merges 

the differences between two selected 

revisions. 

The Lock Revision button locks selected 

revisions. 

The Unlock Revision button unlocks selected 

revisions. 

The Add Label button adds a label to selected 

revisions. 

The Delete Label button deletes a label from 

selected revisions. 

The Promote Revision button promotes 


The Demote Revision button demotes 


The Set Member Revision button sets the 

member revision to the selected revision. 

12 > > > > > > > > > > > > > >

For more information on 

filters, see “Using Filters” 

on page 20. 

Project History Window Toolbar Buttons 

Filter List 



The Archive Information button displays 

information about the archive. 

Beside the toolbar is an optional list of built-in filters that allows 

you to focus your view on a subset of project members you are 

currently interested in. Only those members that meet the criteria 

specified by the filter are displayed. 

Note 

The list of built-in filters is only displayed when a Project or Sandbox 

window is active. 

Workspace 

The Revision Information button displays 

information about selected revisions. 

The Delete Revision button deletes the 

selected revision. 


The Add Label button adds a label to the 


The Delete Label button deletes a label from 

the selected revision. 

The Promote button promotes the selected 

revision. 

The Demote button demotes the selected 

revision. 

Everything between the toolbar and the status bar is considered the 

workspace. This is where VSky Software Manager displays 

windows containing your projects, sandboxes, or member histories. 

For example, when you open a sandbox, its members are presented 

in a Sandbox window in the workspace. 

> > > > > > > > > > > > 13


When you first start VSky Software Manager, the workspace is 

empty. 

Shortcut Menu 

VSky Software Manager supports standard shortcut menus. 

Selecting and right-clicking: 

a member in a Project or Sandbox window 

a revision in a Project or Member History window 

displays a menu of actions you can perform on the selected items. 

Status Bar 

When you select a command from a VSky Software Manager menu, 

a brief explanation of its purpose and status is displayed in the 

status bar. The status bar also displays the progress and status for 

commands launched from the graphical user interface. In addition, 

when you point to a toolbar button, you can see an explanation of 

its function. 

Registered Projects and Registered Sandboxes Dialog Boxes 

The Registered Projects and Registered Sandboxes dialog boxes 

allow you to create, import, and drop projects or sandboxes. 

The Registered Projects dialog box contains one tab, Regular, that 

displays projects used for regular development: 

14 > > > > > > > > > > > > > >

Project and Sandbox Windows 

An example of a Project 

window. 


The Registered Sandboxes dialog box contains three tabs that 

display different types of sandboxes: 

Regular is a sandbox used for regular development. 

Variant is a sandbox used for branching off the main 

development path of another project. 

Build is a sandbox based upon a specific revision of a project, 

but is used for building or testing the project, not for further 

development. 

When you open a project or sandbox, VSky Software Manager 

displays its contents in a Project or Sandbox window. 

> > > > > > > > > > > > 15


An example of a Sandbox 

window. 

The Project and Sandbox windows display project members, 

subprojects, and subsandboxes in a tree structure. You can open 

and close project, sandbox, subproject, and subsandboxes with the 

following options: 

double-click the project, sandbox, subproject, or subsandbox 

click the plus or minus icons 

from a Project window, choose Project > Expand All Subprojects 

or Project > Collapse All Subprojects 

from a Sandbox window, choose Sandbox > Expand All 

Subsandboxes or Sandbox > Collapse All Subsandboxes 

The information in Project and Sandbox windows is displayed in 

columns with the following headings and icons: 

Name displays the following information: 

project or subprojects, for example, project.pj. 

sandbox or subsandboxes, for example, project.pj. 

project or sandbox members, for example, demoapp.c. 

Revision displays the member’s revision number, for example, 

1.1. 

In the column, a delta symbol with a white document icon 

means your working file has changed. It also appears when no 

working file exists for the member. A description of the 

changes is shown at the bottom of the window. 

In the column, a delta symbol with a blue striped 

document icon means the member history has new revisions 

available. A description of the changes is shown at the bottom 

of the window. 

16 > > > > > > > > > > > > > >


change packages, see 

“Integrated Version 

Control” on page 197. 


In the column, a snowflake icon means the member is 

frozen. When the member is thawed, the snowflake icon 

disappears. 

Locked displays a member’s lock status with a padlock and the 

date and time the lock occurred and the name of the user who 

locked the member. 

Labels displays any labels assigned to the member revision, for 

example, Draft1. 

State displays the state of the member revision, for example, 

Beta. 

C.P. ID displays the member’s change package ID, for example, 

7. 

Note 

The C.P. ID column only appears if change packages are enabled. 

Select a member by clicking it, or by moving the selector bar to it 

with the cursor control keys. 

A box below the list of members displays all delta information: 

working file deltas, new revision (member) deltas, and revision 

sync deltas. For example, if the working file has been updated but 

not checked in, a message tells you that the working file has been 

changed. 

The Project and Sandbox windows can be resized within the 

VSky Software Manager application window’s workspace or 

reduced to an icon in the application window. 

The Project and Sandbox windows also support standard shortcut 

menus. Selecting and right-clicking a project member in a Project or 

Sandbox window displays a menu of actions you can perform on 

the selected items. 

> > > > > > > > > > > > 17


Member History 

Window 

When you open a member history, VSky Software Manager 

displays its contents in a Member History window. 

The information in a Member History window is displayed in 

columns with the following headings and icons: 

The member’s path and name, for example, 

c:\sandboxdemo\demoap.c, appears in the first row 

underneath the columns. If the working file can be edited, the 

entry is preceded by a document and pencil icon ( ). If the 

working file is read-only, the document and pencil icon is 

crossed out in red ( ). 

Revision displays the following information: 

the revision that the working file corresponds to, indicated 

by a white document icon. 

the member’s revision, indicated by a blue striped 

document icon. 

a list of the revisions in the member history, for example, 

1.1, 1.2, 1.3, and so on. 

Author is the user who checked in the revision. 

Date is the date and timestamp of the revision. The date and 

timestamp can be either the check in time and date or the date 

and time the file was last modified, depending on how the user 

checks in the file. 

Locked displays a revision’s lock status with a padlock and the 

date and time the lock occurred and the name of the user who 

locked the revision. 

Labels are the labels attached to the revision, for example, 

Draft1. 

State is the revision’s state, for example, Beta. 

18 > > > > > > > > > > > > > >


change packages, see 

“Integrated Version 

Control” on page 197. 

Project History 

Window 


C.P. ID displays the revision’s change package ID, for example, 

7. 

Note 

The C.P. ID column only appears if change packages are enabled. 

Select a revision by clicking it or moving the selector bar to it with 

the cursor keys. 

A box below the list of revisions displays the revision description 

for the currently selected revision. As you move the selector bar 

from one revision to another, the description changes to reflect the 

currently selected revision. 

The Member History window can be resized within the 



The Member History window also supports standard shortcut 

menus. Selecting and right-clicking a revision in a Member History 

window displays a menu of actions you can perform on the 


When you open a project history, VSky Software Manager displays 

its contents in a Project History window. 

The information in a Project History window is displayed in 

columns with the following headings: 

Revision is the revision number. 

Author is the user who checkpointed the revision. 

Date is the date and time the revision was checkpointed. 

\ 

> > > > > > > > > > > > 19


Using Filters 

Labels are the labels attached to the revision, for example, Bug 

Fixes. 

State is the revision’s state, for example, Beta. 

Select a revision by clicking it or moving the selector bar to it with 

the cursor keys. 

A box below the list of revisions displays the revision description 

for the currently selected revision. As you move the selector bar 

from one revision to another, the description changes to reflect the 

currently selected revision. 

The Project History window can be resized within the 



The Project History window also supports standard shortcut 

menus. Selecting and right-clicking an archive revision in a Project 

History window displays a menu of actions you can perform on the 

selected item. 

As projects become large, they can become more difficult to 

navigate. Finding and selecting the members you are interested in 

becomes increasingly difficult. Filters allow you to view and 

manipulate a predefined subset of project members that are 

grouped according to their properties. 

Note 

The list of built-in filters is only displayed if a Project or Sandbox 

window is active. 

In the graphical user interface, the filters appear in a drop-down list 

located on the toolbar. Choose one of the following filters, and your 

view is filtered accordingly: 

Note 

Filters do not work on subprojects or subsandboxes. They are always 

displayed, regardless of the filters used. 

All Members shows all members of the current project or 

sandbox. 

20 > > > > > > > > > > > > > >

Command Line Interface 

Viewing 

Available 

Commands 


Modified Working Files shows only members with a working 

file that has been modified. 

Out of Sync Members shows only members whose revision in a 

sandbox is not the same as the member revision in the 

corresponding project. 

Any Member Deltas shows only members with working file 

changes or out of sync members. 

Locked Members shows only members locked by any user. 

Members Locked By Me shows only members locked by you. 

Frozen Members shows only frozen members. 

Members with Label shows only members with a particular 

label. If you choose this filter, VSky Software Manager prompts 

you for a label. 

Enter a label in the Label field, then click OK. 

Members with State shows only members with a particular 

state. If you choose this filter, VSky Software Manager prompts 

you for a state. 

Enter a state in the State field, then click OK. 

VSky Software Manager provides a command line interface to 

manage your projects, sandboxes, members, and configure 


The Vertical Sky Software Manager Reference and man pages provide 

complete information about all VSky Software Manager commands 

and their options. 

You can view available VSky Software Manager commands by 

typing si. 

To view a list of a command’s options, add -? or --usage to the 

end of the command, for example, si connect -?. 

> > > > > > > > > > > > 21


Using the 

Graphical User 

Interface 

Command 

Prompts 

Member Name 

Arguments 

In addition to using the command line interface by itself, you can 

also combine the graphical user interface with commands entered 

in the command line interface. This can be useful if you prefer to 

perform certain operations in the command line interface and 

others in the graphical user interface. For example, you can use the 

si co command to check out a file, attaching -g or --gui to the 

end of the command to view the Check Out dialog box. You can 

then select check out options. This allows you to use the Check Out 

dialog box without having to launch the graphical user interface. 

For more information on using the graphical user interface with the 

command line interface, see Vertical Sky Software Manager Reference 

and man pages. 

You can enter some VSky Software Manager commands without 

entering any options, for example, si connect. Entering just the 

command prompts you to add additional information that you 

would normally add in the form of command options. This is 

useful for commands, such as si connect, because the prompts 

may contain default information, for example, your default 

Vertical Sky Server and port number. This information, if it exists, is 

in the IntegrityClientSite.rc file. 

For project and sandbox commands, member refers to members of a 

Vertical Sky Server project. If the member argument is omitted for 

project or sandbox commands, the command is applied to all of the 

members of the project or sandbox. 

The member element must be the last entry of a command 

statement. There are three ways to apply a command to multiple 

members: 

Enter Multiple Member Names 

You can enter two or more member names, separated by 

spaces, as the member component. For example, the command: 

22 > > > > > > > > > > > > > >


si co -S project.pj prog.c brochur.toc 

brochur.idx 

checks out all three members. You can name as many members 

as you like on the command line (subject to the line length 

limitations of your operating system). 

Note 

VSky Software Manager commands do not span command shell line 

lengths. 

Use Wildcards 

Use wildcards in the member component. For example, the 

command: 

si ci -S c:\work\project.pj brochur.* 

checks in all members with the base name brochur and any 

extension. 

Specify a Member List 

A member list (specified with the -F member option) is a text 

file containing the names of the members a command should 

be applied to. For example, the command: 

si ci -S c:\work\project.pj -F flist.lst 

checks in all the members listed in the flist.lst file. 

Members named in the member element may have any level of path 

qualification. 

A member list is a text file containing a list of member names, with 

each name on a line by itself. When you pass a member list to 

Vertical Sky Server, it reads the member names and applies the 

command to them in sequence. 

You can create a member list with any text editor by entering 

membernames—one name per line—in a plain text file. 

Alternatively, you can compile a list of members with the find 

command and copy them to a text file. The find command is a 

standard UNIX utility and is available on Win32 based systems 

with MKS Toolkit. 

> > > > > > > > > > > > 23


Logging In 

For both the VSky Software Manager graphical user interface and 

command line interface, you must establish a connection with an 

Vertical Sky Server before you can perform any VSky Software 

Manager operations on projects or sandboxes. 

All VSky Software Manager commands automatically ask you for 

information and will connect you to the appropriate server if you 

are not already connected. If your system is appropriately 

configured, there may be nothing for you to specify, for example, 

your host name and port number. Additionally, if you are using a 

Win32 system connecting to an NT server with single signon 

enabled, you are automatically authenticated as the current user on 

your local system. 

Note 

All or some of the login dialog boxes may appear, depending on the 

configuration set up by your administrator. 

To log in using the graphical user interface 

1 Choose File > Server Connection > Establish, or click . 

The Specify Server Connection dialog box may appear. 

2 In the Host Name field, enter the name of the Vertical Sky Server 

you want to connect to, for example, knovak-nt, or the 

numerical IP address, 1.2.34.56. 

3 In the Port Number field, type the port number, for example, 

7001. 

4 To accept the server information, click OK. To cancel connecting 

to the server, click Cancel. 

24 > > > > > > > > > > > > > >

The Enter Credentials dialog box appears. 

5 In the User Name field, enter your user name, for example, 

knovak. 

Note 

Your user name appears by default in the User Name field. 

6 In the Password field, enter your password, for example, 

docsteam. 

Logging In 

7 To accept the user information, click OK. To cancel connecting 

to the server, click Cancel. 

VSky Software Manager establishes a connection with the 

server. 

To verify your connection, choose File > Server Connection. If 

you are connected, your user name, server name, and port 

number appears in the Server Connection menu, for example, 

knovak@knovak-nt:7030. 

To log in using the command line interface 

Use the si connect command, for example: 

si connect --hostname=value --port=value 

--user=value --password=value 

where 

--hostname=value specifies the Vertical Sky Server name, for 

example, localhost 

--port=value specifies the port number, for example, 7030 

--user=value specifies your user name, for example, knovak 

> > > > > > > > > > > > 25


--password=value specifies your password, for example, 

docsteam 

Note 

Setting Preferences 

You may not need to specify certain options based on your 

configuration. 

VSky Software Manager establishes a connection with the server. 

To verify your connection, use the si servers command. If you are 

connected, your user name, server name, and port number appears, 

for example, knovak@knovak-nt:7030. 

Preferences allow you to customize your VSky Software Manager 

Client session. You can configure general preferences, connection 

preferences, commands, and views. 

To set general preferences in the graphical user interface 

1 Choose Tools > Preferences, or click . 

26 > > > > > > > > > > > > > >

The Preferences dialog box appears. 


2 To set the appearance of the graphical user interface, choose an 

option from the Look and Feel drop-down list. The available 

choices are: 

System is the appearance of the operating system you are 

running. This is the default appearance. 

Windows is the standard appearance for Windows 

applications. 

Motif is the standard appearance for UNIX applications. 

Metal is a metal-like appearance. 

Note 

You must restart the VSky Software Manager Client for the new look 

and feel changes to take effect. See “Quitting a Session” on page 42. 

3 To choose an editor for editing files, click an option under 

Editor. The available options are: 

Use System Editor uses the system’s default editor for the 

type of file being edited, for example, Notepad, to edit text 

files. 

> > > > > > > > > > > > 27


Editor allows you to choose an editor. Click Browse, then 

choose an editor, such as vi. 

4 To set the time in milliseconds (ms) that a command’s status 

appears in the graphical user interface, enter a numeric value in 

the GUI field, such as 4000, or use the up and down arrow 

buttons. 

5 To set the time in milliseconds (ms) that a command’s status 

appears in the command line interface, enter a numeric value 

in the CLI field, such as 4000, or use arrows to make a selection. 

6 To shut down the VSky Software Manager Client upon exiting 

the graphical user interface, select the Shutdown Vertical Sky 

Software Manager Client on Exit checkbox. A blank checkbox 

( ) means the option is not enabled, a checkmark ( ) means 

the option is enabled, and a question mark ( ) means you will 

be prompted to confirm or specify the option. 

If you shut down the client on exit, you exit the client 

completely. If you exit the graphical user interface, without 

shutting down the client, you can still perform VSky Software 

Manager commands in the command line interface, or start the 

graphical user interface again without having to restart the 

client. 

Setting Connection Preferences 

The Connection tab in the Preferences dialog box contains default 

settings for server and proxy connections. Default settings can be 

overridden when connecting to a Vertical Sky Server. 

To set connection preferences in the graphical user interface 

1 Click the Connection tab. 

28 > > > > > > > > > > > > > >

The Connection panel appears. 


2 To specify a default Vertical Sky Server to connect to, in the 

Host Name field, under Default Server Connection, enter the 

name of the server, for example, knovak-nt, or the numerical 

IP address, for example, 1.2.34.56. 

3 In the Port field, under Default Server Connection, type the port 

number, for example, 7030. 

4 To be prompted for the default Vertical Sky Server name and 

port number each time you log in to VSky Software Manager, 

select the Prompt for Host Name and Port checkbox. 

5 Optionally, in the Socks Host Name field, under Proxies, enter 

the name of the proxy Vertical Sky Server you want to connect 

to, for example, proxyhost, or the numerical IP address, for 

example, 1.2.34.66. 

Note 

Contact your administrator about using a proxy server. 

6 In the Port field, under Proxies, type the port number, for 

example, 7761. 

> > > > > > > > > > > > 29


Setting Command Preferences 

The Commands tab in the Preferences dialog box contains default 

settings for VSky Software Manager commands. Default settings 

can always be replaced for individual commands at the time of 

their use. 

To set command preferences in the graphical user interface 

1 Click the Commands tab. 

The Commands panel appears. 

2 From the Command drop-down list, choose a command to 

configure. The available commands and their options are: 

Command Options 

Add Label Move Existing Label moves the label, if it 

already exists, onto the revision specified. 

Recurse Into Subprojects adds the label 

recursively to subproject members. 

30 > > > > > > > > > > > > > >



Add Members Author is the author name applied to the new 

members. Enter a name in the Author field or 

leave blank to use the default author name. 

Data Type specifies the member’s data type. 

To let VSky Software Manager determine the 

data type automatically, choose Auto from the 

Data Type drop-down list. To specify a text file, 

choose Text from the Data Type drop-down 

list. To specify a file containing unprintable 

characters, or lines too long to be handled by 

text editors, choose Binary from the Data Type 

drop-down list. 

Retain Working File means the working file of 

a newly added member will not be deleted. 

Unexpand Keywords replaces literal values in 

the working file with keywords. 

Recurse Into Subdirectories adds members 

that exist in subdirectories of the current 

location. 

Save Working File Timestamp sets the 

timestamp of the revision in the history to the 

timestamp of the working file rather than the 

time of check in. 

Add Attribute Recurse Into Subprojects adds member 

attributes recursively to selected subproject 

members. 

Add Project Label Move Existing Label moves the label, if it 


Append Revision 

Description 

Recurse Into Subprojects appends the 

revision description recursively to subproject 

members. 

> > > > > > > > > > > > 31



Checkpoint Apply Label to All Members applies the 

checkpoint label to all project members. 

Apply State to All Members applies the 

checkpoint state to all project members. 

Recurse Into Subprojects recursively 

checkpoints subprojects. 

Author is the author name applied to the 

checkpoint. Enter a name in the Author field. If 

you do not enter a name, VSky Software 

Manager uses the current user name. 

32 > > > > > > > > > > > > > >



Check In Move Existing Label moves the label, if it 


Lock Revision causes VSky Software 

Manager to check in the working file, then 

immediately lock the new revision. This allows 

you to update the archive while retaining control 

of the revision. 

If this option is not set, the new revision is not 

locked following the check in. 

Check In if Unchanged checks in the working 

file even if it has not changed since it was 

checked out. 

Update Member Revision makes the new 

revision the member revision in the project, 

replacing the existing member revision. 

Author is the author name applied to the 

revision. Enter a name in the Author field or 

leave blank to use the default author name. 

Retain Working File causes VSky Software 

Manager to check in the working file and 

immediately check it out again. If this option is 

cleared, the working file is deleted after it is 

checked in. 

Unexpand Keywords replaces literal values in 

the checked in revision with keywords. 

Force Creation of New Branch causes 

VSky Software Manager to create a branch off 

of the revision you are checking in. 

Save Working File Timestamp sets the 

timestamp of the revision in the history to the 

timestamp of the working file rather than the 

time of check in. 

> > > > > > > > > > > > 33



Check Out Lock Revision checks out a writable working 

file, and ensures that no one else can make 

changes to the revision while you have it 

checked out. A revision must be checked out 

locked if strict locking is enabled, and you 

intend to make changes to it. 

Overwrite Working File if Changed overwrites 

the working file even if the member has 

changed since it was last checked in. 

Update Member Revision causes the revision 

you check out to become the new member 

revision of the project. For example, if the 

current project member is listed as Revision 2.3 

and you check out Revision 1.7 with the Update 

Member option selected, Revision 1.7 replaces 

Revision 2.3 as the member of the project. 

Force Creation of New Branch causes 

VSky Software Manager to force the creation of 

a new branch on checkout, eliminating the 

chance of a locking conflict. 

Restore Revision Timestamp sets the 

timestamp of the working file the revision is 

checked out to to the date and time of the 

revision in the history. If this option is cleared, 

the working file’s timestamp is set to the current 

date and time. 

Create Branch if Variant causes 


of the revision you are checking out, if you are 

working in a variant sandbox and this is the first 

time the member has been checked out. This 

reduces the possibility of locking conflicts with 

the member while work is being done in the 

variant and regular sandboxes. 

Keywords allows you to choose keyword 

expansion options when checking out a 

member. To leave keywords unexpanded, 

choose Do Not Expand from the Keywords 

drop-down list. To replace keywords in the 

revision with literal values in the working file, 

select Expand from the Keywords drop-down 

list. To unexpand keywords in the working file, 

select Unexpand from the Keywords dropdown 

list. 

34 > > > > > > > > > > > > > >



Create Sandboxes Populate Sandbox causes VSky Software 

Manager to add working files to the sandbox. 

Recurse Into Subprojects creates 

subsandboxes recursively from subprojects. 

Make Sandbox Sparse creates a sandbox with 

no working files. 

View Sandbox After Creation displays the 

sandbox after it has been created. 

Delete Label Recurse Into Subprojects deletes the label 

recursively from members in subprojects. 

Delete Revision Confirm Delete causes VSky Software 

Manager to confirm that you want to delete the 

revision before it is deleted. 

Recurse Into Subprojects deletes the revision 

recursively in members of subprojects. 

Demote Recurse Into Subprojects recursively 

demotes subproject members. 

Diff Ignore Case ignores case when comparing the 

selected revision and the member’s working file 

or another revision. 

Ignore Blanks ignores blank spaces when 

comparing the selected revision and the 

member’s working file or another revision. 

Disconnect From 

Server 

Confirm Disconnect causes VSky Software 

Manager to confirm you will be disconnected 

from the Vertical Sky Server. 

Drop Delete Member/Subproject deletes selected 

member/subproject working files when dropped 

from the project. 

Drop Attribute Recurse Into Subprojects recursively drops 

member attributes from members in 

subprojects. 

> > > > > > > > > > > > 35



Drop Sandbox Delete allows you to choose delete options 

when dropping a sandbox. To drop the sandbox 

without deleting any members, choose Nothing 

from the Delete drop-down list. To delete 

sandbox members only, select Sandbox 

Members Only from the Delete drop-down list. 

To delete the sandbox directory and all of its 

contents, select Entire Sandbox Directory 

from the Delete drop-down list. 

Confirm Drop causes VSky Software Manager 

to confirm that the sandbox will be dropped 

before it is dropped. 

Freeze Recurse Into Subprojects recursively freezes 

members in subprojects. 

Lock Force Creation of New Branch causes 


of the revision being locked. 

Recurse Into Subprojects locks all members 

in subprojects. 

Promote Recurse Into Subprojects promotes all 


36 > > > > > > > > > > > > > >



Resynchronize Populate Member if Missing copies the 

missing sandbox member’s working file with a 

copy of the project member. 


the working file even if it has changed. 


expansion options when resynchronizing. To 

replace keywords in the revision with literal 

values in the working file, select Expand from 

the Keywords drop-down list. To leave 

keywords unexpanded, choose Do Not Expand 

from the Keywords drop-down list. To replace 

literal values in the revision with keywords, 

select Unexpand from the Keywords dropdown 

list. 




revision in the history. If this option is not set, 



Force Overwrite Even if Unchanged 

overwrites the working file even if it is 

unchanged. 

Recurse into Subprojects recursively 

resynchronizes members in subprojects. 

> > > > > > > > > > > > 37



Revert Populate Member if Missing copies the 

missing sandbox member’s working file from 

the project member. 


the working file if it has changed. 


options when reverting a member. To leave 

keywords unexpanded, choose Do Not Expand 

from the Keywords drop-down list. To replace 

keywords in the revision with literal values in the 

working file, select Expand from the Keywords 

drop-down list. To replace literal values in the 

revision with keywords, select Unexpand from 

the Keywords drop-down list. 




revision in the history. If this option is not set, 



Force Overwrite Even if Unchanged 

overwrites the working file even if it is 

unchanged. 

Recurse Into Subprojects recursively reverts 

members in selected subprojects. 

Thaw Recurse Into Subprojects recursively thaws 


Unlock Break Lock breaks locks held by other users. 

Recurse Into Subprojects recursively unlocks 


Update Revision Recurse Into Subprojects updates the 

member revision of members in subprojects. 

3 If necessary, select a command’s option checkbox. A blank 

checkbox ( ) means the option is not enabled, a checkmark 

( ) means the option is enabled, and a question mark ( ) 

means you will be prompted to confirm or specify the 

option(s). For example, if the Overwrite Working File if 

Changed option for the Resynchronize command is not 

enabled, resynchronizing a member that has changed, does not 

38 > > > > > > > > > > > > > >


overwrite its working file. If the option is enabled, the working 

file is overwitten. If the option is set to confirm, you are asked if 

the working file should be overwritten. 

4 To restore a command’s default options, click Reset to Defaults. 

Setting View Preferences 

The Views tab in the Preferences dialog box contains default option 

settings for VSky Software Manager views. 

To set view preferences in the graphical user interface 

1 Click the Views tab. 

The Views panel appears. 

2 From the View drop-down list, choose a command to configure. 

The available commands and their options are: 


Archive Information 

View 

Show Labels displays archive labels. 

Show Locks displays locks. 

> > > > > > > > > > > > 39




View 

Member Information 

View 

Adorn Graphical View displays menus and 

toolbars on the window, where appropriate. If 

this option is not set, commands can only be 

activated with the keyboard and a shortcut 

menu. 

Show Attributes displays member attributes. 

Show Change Package Information 

displays change package information (only if 

VSky Collaboration Manager is installed). 

Show Labels displays member labels. 

Member Labels View Adorn Graphical View displays menus and 




menu. 

Project View Adorn Graphical View displays menus and 




menu. 

Project History View Adorn Graphical View displays menus and 




menu. 

Project Information 

View 

Registered Projects 

View 

Registered 

Sandboxes View 

Revision Information 

View 

Show Attributes displays project attributes. 

Show Development Paths displays 

development paths for creating variant 

sandboxes. 

Show Subprojects displays registered 

subprojects. 

Show Subsandboxes displays registered 

subsandboxes. 

Show Labels displays labels on the revision. 

Show Change Package Information 

displays change package information (only if 

VSky Collaboration Manager is installed). 

40 > > > > > > > > > > > > > >

Quitting a Vertical Sky Software Manager Session 

3 If necessary, select a view’s option checkbox. A blank checkbox 

( ) means the option is not enabled, and a checkmark ( ) 

means the option is enabled. 

4 To restore a view’s default options, click Reset to Defaults. 

To set and save configuration preferences in the command 

line interface 

Use the si setprefs command. 

For a complete list of the command’s options, see Vertical Sky 

Software Manager Reference, or the man pages. 

To save preferences in the graphical user interface 

In the Preferences dialog box, click OK. To cancel the operation, 

click Cancel. 

The preferences are saved. 

Quitting a Vertical Sky Software Manager 

Session 

Logging Out 


Sandbox View Adorn Graphical View displays menus and 




menu. 

Sandbox Information 

View 

Show Project Attributes displays project 

attributes. 

You can log out of VSky Software Manager and log in as another 

user, or allow another user to log in. 

To log out in the graphical user interface 

1 Choose File > Server Connection > Drop. 

A dialog box may appear asking you to confirm that you want 

to drop your server connection. To disable this dialog box, see 

> > > > > > > > > > > > 41


Quitting a 

Session 

the Disconnect From Server command in “Setting Command 

Preferences” on page 30. 

2 To disconnect from the server, click Yes. To cancel the 

operation, click No. 

Note 

Disconnecting from the server closes all current views, such as 

Sandbox windows. 

The server connection is disconnected. 

To login again, see “Logging In” on page 24. 

To log out in the command line interface 

Use the si disconnect command, for example: 

si disconnect 


To log in again, see “Logging In” on page 24. 

When you quit a VSky Software Manager session, you have the 

option of exiting the user interface you are in, and/or shutting 

down the client. If you shut down the client on exit, you exit the 

client completely. If you exit the graphical user interface, without 

shutting down the client, you can still perform VSky Software 

Manager commands in the command line interface or start the 

graphical user interface again without having to restart the client. 

To quit a session in the graphical user interface 

1 Choose File > Exit. 

A dialog box appears asking if you want to shut down the 

VSky Software Manager Client, depending on your 

preferences. 

Note 

You can configure the graphical user interface to shut down the client 

automatically each time you end a session. For more information, see 

“Setting Preferences” on page 26. 

42 > > > > > > > > > > > > > >

Quitting a Vertical Sky Software Manager Session 

2 To shut down the client, click Yes. To leave the client running, 

click No. 

The VSky Software Manager graphical user interface closes 

and the connection to the server is disconnected. 

To quit a session in the command line interface 

Use the si exit command, for example: 

si exit --[no|confirm]shutdown 

where 

--noshutdown leaves the client running 

--shutdown shuts down the client 

--confirmshutdown confirms the client will keep running or 

be shut down before you close the session 


> > > > > > > > > > > > 43


44 > > > > > > > > > > > > > >

Getting Started With 

Projects, Sandboxes, 

and Members 

3 

This chapter describes the Vertical Sky Software Manager features 

you will use in your day-to-day activities, such as creating a 

sandbox or checking out members. 

The tasks you can perform are restricted by the permissions 

assigned to you by your administrator. 


creating a project and sandbox 

importing a project and sandbox 

opening a project and sandbox 

adding members to a project 

removing members from a project 

creating a subproject 

variant sandboxes and creating/removing development paths 

build sandboxes 

selecting members 

checking out members 

viewing and editing members 

checking in members 

comparing a working file to its member revision 

discarding changes to a working file 

resynchronizing members 

locking and unlocking members 

using keywords 

> > > > > > > > > > > > 45

Getting Started With Projects, Sandboxes, and Members 

Creating a Project 

For suggested best 

practices on creating 

projects, see Vertical Sky 


Administration. 

When you are ready to place a group of files under VSky Software 

Manager control, the first step is to create a project. A project is a 

master group of files that reside on the Vertical Sky Server. When 

creating a project, you only create the project file. You must create a 

sandbox to add files, or members, to the project. 

To create a project in the graphical user interface 

1 Choose File > New Project, or click . 

The Specify a Project dialog box appears. 

2 Enter the path and file name, or browse to a location on the 

Vertical Sky Server where you want to create the project. 

Note 

If the project path does not exist on the Vertical Sky Server, it will be 

created. 

3 Enter a name for the project, for example, project.pj. 

4 Click OK. 

The project appears in a Project window. 

You can now create a sandbox, then add members to the sandbox. 

For more information, see “Creating a Sandbox” on page 48. 

To create a project in the command line interface 

Use the si createproject command, for example: 

si createproject projname 

where 

46 > > > > > > > > > > > > > >

Importing a Project 

Importing a Project 

projname specifies the path and name of the project you want to 

create, for example, c:/Docs Vertical Sky Server/ 

Projects/masterdemo/project.pj 

Note 

If the project path does not exist on the Vertical Sky Server, it will be 

created. 

VSky Software Manager confirms the project is created. 

When you create a project, it is automatically registered with the 

Vertical Sky Server; however, projects created with older versions 

of VSky Software Manager require that you import them to register 

them with the Vertical Sky Server. 

To import a project in the graphical user interface 

1 Choose Tools > Manage Projects, or click . 

The Registered Projects dialog box appears. 

> > > > > > > > > > > > 47


2 Click Import. 

The Select One or More Projects dialog box appears. 

3 Browse to the project file on the server. 

Note 

If your connection to the Vertical Sky Server is disconnected while you 

are browsing for a file, the file browser does not show any files or 

directories. 

4 Click OK. 

The project is added to the Registered Projects dialog box. 

To import a project in the command line interface 

Use the si importproject command, for example: 

si importproject projname 

where 

Creating a Sandbox 


import, for example, c:/import/project/project.pj 

VSky Software Manager confirms the project is imported. 

When you want to work with a project, you create a sandbox. A 

sandbox is a mirror image of the project that resides on your local 

drive. Working in a sandbox allows you to work in your own 

workspace without interfering with the work of others. Once a 

sandbox has been created, you can add files, or members to the 

sandbox. The project is then updated to reflect the addition of new 

project members. 

To create a sandbox in the graphical user interface 

1 Choose File > New Sandbox, or click . 

48 > > > > > > > > > > > > > >

The Create Sandbox Wizard appears. 


2 In the Project Name field, enter the path and name of the 

project, or click Select. 

Note 

If you have a Project window open, the project path and name appears 

in the Project Name field. 

If you click Select, the Select One or More Projects dialog box 

appears. 

Choose a project. 

3 Click Next. 

> > > > > > > > > > > > 49


The second panel of the Create Sandbox Wizard appears. 

4 In the Sandbox Location field, enter the directory in which you 

want to create the sandbox, or click Browse, then browse to a 

location on your local drive. 

5 Under Options, choose sandbox options by selecting 

checkboxes. A blank checkbox ( ) means the option is not 

enabled, a checkmark ( ) means the option is enabled, and a 

question mark ( ) means you will be prompted to confirm or 

specify the option(s). The available options are: 

Populate Sandbox adds working files to the sandbox. 

Recurse into Subprojects creates subsandboxes recursively 

from subprojects. 

Make Sandbox Sparse creates a sandbox with no working 

files. 

View Sandbox After Creation displays the sandbox after it is 

created. 

50 > > > > > > > > > > > > > >


variant sandboxes, see 

“Variant Sandboxes and 

Development Paths” on 

page 71. 

6 Click Next. 

Note 


If the directory you specify does not exist, a Confirm Create Sandbox 

Location dialog box appears asking if you want to create the new 

location. To create the path, click Yes. To change the sandbox location, 

click No. 

The third panel of the Create Sandbox Wizard appears. 

7 Choose the type of sandbox you want to create by clicking a 

sandbox type option. The available types are: 

Normal creates a sandbox based upon the current state of 

the project. 

Variant creates a sandbox based upon a specific revision of 

the master project and is used for branching off the main 

development path. 

> > > > > > > > > > > > 51



build sandboxes, see 

“Build Sandboxes” on 

page 74. 

From the Development Path Name drop-down list, choose a 

development path name, for example, Variant Project. 

Note 

The Variant option is unavailable if there are no available development 

paths. To create a development path, see “Creating a Development 

Path” on page 72. 

Build creates a static sandbox based upon a specific revision 

of the master project that is used for building or testing the 

project, but not for further development. 

From the Revision drop-down list, choose a project revision 

number, for example, 1.1. 

8 To accept the options, click Finish. To modify the options, click 

Back. To cancel the operation, click Cancel. 

The sandbox appears in a Sandbox window. 

To create a sandbox in the command line interface 

Use the si createsandbox command, for example: 

si createsandbox --project=value sandboxpath 

where 

--project=value specifies the path and name of the master 

project, for example, --project=c:/masterdemo/project.pj 

sandboxpath specifies the path of the new sandbox, for example, 

c:/sandboxdemo 

52 > > > > > > > > > > > > > >

VSky Software Manager confirms the sandbox is created. 

Note 


If the sandbox path does not exist, it is created automatically. If the 

sandbox path is not specified, the sandbox is created in the current 

directory. 

To create a variant sandbox in the command line interface 


si createsandbox --project=value --devpath=value 

sandboxpath 

where 



--devpath=value specifies the development path of the master 

project, for example, --devpath=Variant Project 


c:/variantsandbox 

VSky Software Manager confirms the variant sandbox is created. 

To create a build sandbox in the command line interface 


si createsandbox --project=value -projectRevision=value 

sandboxpath 

where 



--projectRevision=value specifies the project revision you 

want to create a sandbox from, for example, -projectRevision=1.2 


c:/buildsandbox 

VSky Software Manager confirms the build sandbox is created. 

> > > > > > > > > > > > 53


Importing a Sandbox 

When you create a sandbox, it is automatically registered with the 

VSky Software Manager Client; however, sandboxes created with 

earlier versions of VSky Software Manager, such as MKS Source 

Integrity, require that you import them to register them with the 

VSky Software Manager Client. 

Note 

The sandbox’s master project must be registered with the Vertical Sky 

Server. 

To import a sandbox in the graphical user interface 

1 Choose Tools > Manage Sandboxes, or click . 

The Registered Sandboxes dialog box appears. 

2 Click Import. 

The Select One or More Files dialog box appears. 

54 > > > > > > > > > > > > > >

3 Browse to the sandbox file on your local drive. 

Note 

Dropping a Project 



directories. 

4 Click Open. 

The Select a Project dialog box appears. 

5 Select the corresponding master project from the list of projects. 

6 Click OK. 

The sandbox is added to the Registered Sandboxes dialog box. 

To import a sandbox using the command line interface 

Use the si importsandbox command, for example: 

si importsandbox --project=value sandboxpath 

where 

Dropping a Project 


project, for example, --project=c:/A Soft Mgr 80a/Soft 

Mgr 80a/project.pj 

sandboxpath specifies the path and name of the sandbox you 

want to import, for example, c:/A Soft Mgr 80a/Soft Mgr 

80a/sandbox.pj 

VSky Software Manager confirms the sandbox is imported. 

When a project has outlived its usefulness or just does not belong 

on the Vertical Sky Server anymore, you can remove it at any time. 

Dropping a project unregisters it from the Vertical Sky Server, but 

does not delete the project. You can import the project again if you 

choose to. 

> > > > > > > > > > > > 55


To drop a project in the graphical user interface 

1 Choose Tools > Manage Projects, or click . 

The Registered Projects dialog box appears. 

2 Select the project you want to drop. 

3 Click Drop. 

The project is removed from the list of registered projects. 

To drop a project in the command line interface 

Use the si dropproject command, for example: 

si dropproject projname 

where 


drop, for example, c:/Docs Vertical Sky Server/ 

Projects/Projects 

VSky Software Manager confirms the project is removed from the 

list of registered projects. 

56 > > > > > > > > > > > > > >

Dropping a Sandbox 

Dropping a Sandbox 

When a sandbox has outlived its usefulness or just does not belong 

anymore, you can remove it at any time. 

Dropping a sandbox unregisters it from the VSky Software 

Manager Client, but does not delete the sandbox (unless specified). 

If the sandbox still exists, you can import the sandbox again if you 

choose to. 

To drop a sandbox in the graphical user interface 

1 Choose Tools > Manage Sandboxes, or click . 

The Registered Sandboxes dialog box appears. 

2 Select the sandbox you want to drop. 

3 Click Drop. 

4 Confirm that you want to drop the sandbox by clicking OK. To 

cancel the operation, click Cancel. 

> > > > > > > > > > > > 57


The Drop Sandbox dialog box appears. 

5 From the Delete drop-down list, choose a delete option. The 

available options are: 

Nothing does not delete any files from the sandbox 

directory. 

Sandbox Members Only deletes the sandbox members. 

Entire Sandbox Directory deletes the sandbox directory and 

all of its contents. 

6 To drop the sandbox, click OK (for multiple sandboxes, click OK 

to All). To cancel the operation, click Cancel. 

The sandbox is removed from the list of registered sandboxes. 

To drop a sandbox in the command line interface 

Use the si dropsandbox command, for example: 

si dropsandbox sandboxname 

where 

sandboxname specifies the path and name of the sandbox you 

want to drop, for example, c:/project.pj 

VSky Software Manager confirms the sandbox is removed from the 

list of registered sandboxes. 

Opening or Viewing a Project 

Opening a project in the graphical user interface allows you to view 

and work with the project and its members; however, because in 

the command line interface you perform commands upon a project 

and its members directly, you cannot open a project, only view the 

project and its members. 

58 > > > > > > > > > > > > > >

To open a project in the graphical user interface 

1 Choose File > Open Project, or click . 

The Select a Project dialog box appears. 

2 Select a project from the list of projects. 

3 Click OK. 

The project opens in a Project window. 

To view a project in the command line interface 

Use the si viewproject command, for example: 

si viewproject --project=value 

Opening or Viewing a Project 

> > > > > > > > > > > > 59


where 

--project=value specifies the path and name of the project you 

want to view, for example, --project=c:/Docs Vertical 

Sky Server/Project.pj 

VSky Software Manager displays the project’s members (if there 

are any), their status, and revision numbers, for example: 

demoapp.c archived 1.1 

demoapp.ico archived 1.1 

demoapp.ini archived 1.1 

Opening or Viewing a Sandbox 

Opening a sandbox in the graphical user interface allows you to 

view and work with the sandbox and its members; however, since 

in the command line interface you perform commands upon a 

sandbox and its members directly, you can not open a sandbox, 

only view the sandbox and its members. 

To open a sandbox in the graphical user interface 

1 Choose File > Open Sandbox, or click . 

The Select a Sandbox dialog box appears. 

60 > > > > > > > > > > > > > >

Opening or Viewing a Sandbox 

2 To select a sandbox type, click a sandbox type tab. The 

available sandbox types are: 

Regular is a sandbox used for regular development. 

Variant is a sandbox used for branching off the main 

development path of another project. 

Build is a sandbox based upon a specific revision of a 

project, but is used for building or testing the project, not 

for further development. 

3 Select a sandbox from the sandbox list. 

4 Click OK. 

The sandbox opens in a Sandbox window. 

To view a sandbox in the command line interface 

Use the si viewsandbox command, for example: 

si viewsandbox --sandbox=value 

where 

--sandbox=value specifies the path and name of the sandbox 

you want to view, for example, --sandbox=c:/Project.pj 

VSky Software Manager displays the paths and names of the 

sandbox’s members (if there any), their status, and revision 

numbers, for example: 

c:/demoapp.c archived 1.1 

c:/demoapp.ico archived 1.1 

c:/demoapp.ini archived 1.1 

> > > > > > > > > > > > 61


Adding Members to a Project 

Once you create a project and a sandbox, you can add files, or 

members, to the project through the sandbox. 

Note 

Before you add members to a project, the members must be in the 

sandbox’s directory tree. 

To add members to a sandbox in the graphical user interface 

1 With a Sandbox window open, select the sandbox or 

subsandbox you want to add members to. 

2 Choose Sandbox > Add Members, or click . 

The Add Members Wizard appears. 

3 In the Sandbox Name field, enter the path and name of the 

sandbox you want to add members to, or click Select, then 

choose a sandbox from the sandbox list. 

4 Click Next. 

62 > > > > > > > > > > > > > >


The second panel of the Add Members Wizard appears. 

5 Click Add. 

The Select One or More Members to Add to the Sandbox dialog 

box appears. 

6 Select one or more files from the displayed file list, navigating 

to the desired directory if necessary. 

Note 



directories. 

7 Click Open. 

The files are added to the members list. To remove files, select 

the files, then click Remove. 

8 To complete the operation, click Finish. To make changes, click 

Back. To cancel the operation, click Cancel. 

> > > > > > > > > > > > 63


The Create Archive dialog box appears. 

9 In the Archive Description field, enter a description of the 

member. 

10 In the Author field, if necessary, enter your user name. The user 

name specified in the Add Members command configuration 

appears by default. 

11 In the Revision Number field, if necessary, enter a revision 

number for the member. VSky Software Manager creates the 

revision number 1.1 by default. 

12 In the Data Type field, choose a file data type from the dropdown 

list. The available options are: 

Auto means VSky Software Manager determines the data 

type automatically. 

Text is a file format expected by MS-DOS and Windows 

text file editors. 

Binary is a file containing unprintable characters or lines 

too long to be handled by text editors. 

13 To keep the working file of a newly added member, select the 

Retain Working File checkbox. 

14 To replace literal values in the revision with keywords, select 

the Unexpand Keywords checkbox. 

64 > > > > > > > > > > > > > >


15 To set the timestamp of the revision in the history to the 

timestamp of the working file rather than the time the member 

was added, select the Save Working File Timestamp checkbox. 

16 To accept the information, click OK. To accept the information 

for all members, click OK to All. To cancel the operation, click 

Cancel. 

Note 

If you are re-adding a dropped member and the member’s archive still 

exists, a dialog box appears informing you an archive already exists 

for the member. To add the member and associate it with the archive, 

click Yes (for multiple members, click OK to All). To cancel adding the 

member and associating it with the archive, click No or Cancel (for 

multiple members, click No to All). 

17 Repeat for the remaining members, if necessary. 

The members appear in the Sandbox window. 

To add members to a sandbox in the command line interface 

Use the si add command, for example: 

si add --sandbox=value member 

where 


you are adding members to, for example, 

--sandbox=c:\sandboxdemo\project.pj 

member specifies the members you want to add to the sandbox, 

for example, demoapp.c, demoapp.h, demoapp.ico, 

demoapp.ini. 

> > > > > > > > > > > > 65


Selecting Members 

VSky Software Manager confirms the members are added to the 

sandbox. 

The Select command allows you to highlight any members of the 

current sandbox or project that meet specified selection criteria. 

Members selected with this command can be manipulated as a 

group by other VSky Software Manager commands. 

To select specific members (graphical user interface only) 

1 With a Project or Sandbox window open, choose Member > 

Select, or click . 

The Select Members dialog box appears. 

2 Choose the selection criteria you want to use by selecting a 

checkbox. A blank checkbox ( ) means do not use this criteria 

for selecting members, a checkmark ( ) means use this criteria 

66 > > > > > > > > > > > > > >

Selecting Members 

for selecting members, and an exclamation mark ( ) means 

use the negated form of this selection criteria. The available 

options are: 

Note 

These options only apply to visible members. Members in 

unexpanded directories and subprojects are not selected. 

All Members selects all visible members. 

Changed Members selects members that have specific 

changes to them. 

To select all members that have changes, choose All 

Changes from the Changed Members drop-down list. 

To select all members that have working file changes, 

choose Working File Changes from the Changed 

Members drop-down list. 

To select members whose working file revision is different 

from the member revision, choose Out of Sync Members 

from the Changed Members drop-down list. 

To select members that have a new revision available, 

choose New Revision Available from the Changed 

Members drop-down list. 

Members Locked By selects members locked by a specific 

user. 

To select members locked by you, choose from the 

Members Locked By drop-down list. 

To select members locked by any user, choose 

from the Members Locked By drop-down list. 

To select members locked by a specific user, select a user 

name, for example, , from the Members Locked By 


Members With Label selects members with a specific label. 

Choose a label from the Members With Label drop-down 

list. 

To select members with any label, choose 

from the Members With Label drop-down list. 

> > > > > > > > > > > > 67


Members With State selects members with a specific state. 

Choose a state from the Members With State drop-down list. 

Members With Attribute selects members with a specific 

attribute. Choose an attribute from the Members With 

Attribute drop-down list. 

Frozen Members selects all frozen members (members that 

are in a state that prevents changes being made to the 

member information). 

Members With Name selects members with a specific name. 

Enter a member name in the Members With Name field. 

Wildcards such as ? and * are supported. 

3 If two or more criteria are selected, they can be joined with a 

Logical AND or Logical OR by clicking the appropriate option. 

4 To accept the selection criteria, click OK. To cancel the 

operation, click Cancel. 

The member are selected in the Project or Sandbox window. 

Removing Members From a Project 

If a member has outlived its usefulness or just does not belong in a 

project anymore, you can remove it at any time. 

After you remove a member from a project, the member is no 

longer listed as part of the sandbox or master project, but the 

member’s history remains, in case you need to recreate an earlier 

version of the project. 

To remove a member in the graphical user interface 

1 With a Sandbox window open, select one or more members to 

remove from the sandbox. 

2 Choose Sandbox > Drop Members, or click . 

A dialog box appears asking you to confirm the member is to 

be removed. 

3 To remove the selected member, click Yes. To remove multiple 

members, click Yes to All. To cancel removing the member, click 

No. To cancel removing multiple members, click No to All. To 

cancel the operation, click Cancel. 

68 > > > > > > > > > > > > > >


resynchronizing, see 

“Resynchronizing 

Members” on page 88. 

Creating a Subproject 

The sandbox is updated to reflect the removed member. 

The member is removed from the project. 

Note 

Once a member is removed from a project, the change is not 

immediately reflected in other sandboxes. Other users must 

resynchronize their sandboxes. 

To remove a member in the command line interface 

Use the si drop command, for example: 

si drop --sandbox=value member 

where 

Creating a Subproject 

For suggested best 

practices on creating 

subprojects, see Vertical Sky 




containing the member you are removing, for example, 

--sandbox=c:/sandboxdemo/project.pj 

member specifies the member you are removing from the project, 

for example, errors.h 

VSky Software Manager confirms the member is removed from the 

project. 

VSky Software Manager allows you to create large projects 

composed of smaller component projects. These smaller projects 

are known as subprojects. Subprojects behave the same as projects, 

and can be accessed with most project and sandbox commands. 

Components usually fall into the following categories: 

source files for creating individual executables 

source files for common libraries 

graphic files 

documentation 

> > > > > > > > > > > > 69


For more information, see 

“Removing Members 

From a Project” on 

page 68. 

To create a subproject in the graphical user interface 

1 With a Project or Sandbox window open, select the project or 

sandbox to add the subproject to. 

2 From a Project window, choose Project > Create Subproject. 

From a Sandbox window, choose Sandbox > Create Subproject. 

The Specify a Subproject dialog box appears. 

3 Enter the path and name for the subproject, for example, 

sandboxdemo/subproject.pj. 

4 Click OK. 

The subproject appears in a Project or Sandbox window. 

You can now add members to the subproject just as you would with 

a project. 

To drop a subproject from a project, you drop it as you would a 

member. 

Note 

Most project commands can be performed on subprojects. 

To create a subproject in the command line interface 

Use the si createsubproject command, for example: 

si createsubproject --project=value subproject 

where 


want to add the subproject to, for example, 

--project=c:/masterdemo/subproject.pj 

70 > > > > > > > > > > > > > >

Variant Sandboxes and Development Paths 

subproject specifies the name of the subproject you want to 

create, for example, subproject.pj 

VSky Software Manager confirms the subproject is created. 

Note 

After a subproject is created, you must resynchronize your sandbox to 

view it from the command line interface. See “Updating a Member’s 

Revision” on page 107. 


Regular sandboxes are based upon the current state of the project. 

You can also create a sandbox that is based upon a previously 

checkpointed revision of the project. This type of sandbox is called 

a variant. When you create a variant sandbox, you choose a 

checkpoint (snapshot) of your project and use it as a starting point 

for new development. VSky Software Manager allows you to do 

this by defining a new development path. 

A development path is an identifier given to a new direction of 

software development. Changes made through the development 

path are kept separate from the main development trunk unless 

you choose to merge them into it later. 

VSky Software Manager allows multiple developers to point to the 

same development path, each using their own variant sandbox. In 

the variant sandbox, you can see the current state of the project 

along the development path and the changes made by other 

developers using it. 

When a variant sandbox is created for the first time, it is also 

created for all subprojects, reserving the assigned name as a unique 

identifier and ensuring no two paths can share the same name. 

Development paths are useful for performing post-release 

maintenance. Variant sandboxes pointing to a post-release 

development path allow you to make changes to a previous 

revision of a project. Any fixes, patches, or changes you check in go 

onto a branch and do not affect the main project, unless you choose 

to merge them. 

> > > > > > > > > > > > 71


Creating a Development Path 

To create a development path in the graphical user interface 

1 With a Project or Sandbox window open, select the project you 

want to create the development path from. 

2 From a Project window, choose Project > Create Development 

Path. 

From a Sandbox window, choose Sandbox > Create 

Development Path. 

The Create Development Path dialog box appears. 

3 Click an option tab, if necessary, then fill in or modify the create 

development path options. 

The Selection tab allows you to select a revision to create a 

development path from. 

To select a revision to create a development path from, click 

Pre-Defined Revision, then choose a revision type from the 

drop-down list. The available types are: 

Head creates a development path from the head revision in 

the project. 

Trunk Tip creates a development path from the latest 

revision in the trunk, independent of default branch 

settings. 

To select a specific revision, click Specific Revision, then click 

the Revisions or Labels tabs to choose a revision. 

72 > > > > > > > > > > > > > >

To create a variant 

sandbox, see “Creating a 

Sandbox” on page 48. 

To create a variant 

sandbox, see “Creating a 

Sandbox” on page 48. 


The Revisions tab allows you to create a development path 

from a specific revision. 

The Labels tab allows you to create a development path 

from a specific labeled revision. 

4 In the Development Path Name field, enter a name for the 

development path, for example, Variant Project. 

5 To create the development path, click OK. To cancel the 


The development path is created. 

To create a development path in the command line interface 

Use the si createdevpath command, for example: 

si createdevpath --project=value -projectRevision=value 

--devpath=value 

where 

Removing a Development Path 


project you want to create a development path from, for 

example, --project=c:/Docs Vertical Sky Server/ 


--projectRevision=value specifies the revision of the project 

you want to create a development path from, for example, 1.1 

--devpath=value specifies the name of the development path 

you want to create, for example, Variant Project 

VSky Software Manager confirms the development path is created. 

Once a development path is no longer needed or useful, you can 

remove it at any time. 

To remove a development path in the graphical user interface 

1 With a Project or Sandbox window open, select the project. 

> > > > > > > > > > > > 73



“Viewing and Editing 

Project Information” on 

page 96. 

2 From a Project window, choose Project > Remove Development 

Path. 

From a Sandbox window, choose Sandbox > Remove 

Development Path. 

The Remove Development Path dialog box appears. 

3 From the Development Path drop-down list, choose a 

development path to remove. 

4 To remove the development path, click OK. To cancel the 


The development path is removed. 

To remove a development path in the command line interface 

Use the si dropdevpath command, for example: 

si dropdevpath --project=value --devpath=value 

where 

Build Sandboxes 


project you want to remove a development path from, for 

example, --project=c:/Docs Vertical Sky Server/ 

Projects/masterdemo/project.pj. 

--devpath=value specifies the name of the development path 

you want to remove, for example, Variant Project. 

VSky Software Manager confirms the development path is 

removed. 

After major milestones, such as product releases, you might want 

to recreate a static version of an entire project as it existed at some 

point in the past. You create a build sandbox, to build or test the 

project, not to begin further work along a new development path. 

74 > > > > > > > > > > > > > >

To create a build sandbox, 

see “Creating a Sandbox” 

on page 48. 

Checking Out a Member 


A build sandbox is associated with a particular project revision, 

and has no development path (since it is static and not meant for 

further development). 

Within a build sandbox, you cannot 

check out, lock, or check in members 

remove or add members 

freeze or thaw members 

checkpoint the master project 

modify project or member attributes 

revert members 

set the member revision 

However, with a build sandbox, you can 

change labels and states 

resynchronize your sandbox 

compare a member revision in the build sandbox to another 

revision 

merge a member revision in the build sandbox with another 

revision (of course, you cannot check that merged file back into 

the build sandbox) 

check for differences between project revisions, such as changes 

to a project since it was last checkpointed 

Before you can make changes to a member, you must first check it 

out. When you check out a revision, it is copied to a working file 

where you can view or modify its contents. 

To check out a member in the graphical user interface 


check out. 

2 Choose Member > Check Out, or click . 

> > > > > > > > > > > > 75


The Check Out dialog box appears. 

3 Click an option tab, if necessary, then fill in or modify the check 

out options: 

The Selection tab specifies which revision of the member to 

check out. 

To check out a pre-defined revision, click Pre-Defined 

Revision, then choose a revision type from the drop-down 

list. The available options are: 

Member checks out the member revision, that is, the 

revision shown in the Sandbox window (this is the 

default). 

Head checks out the head revision. 

Trunk Tip checks out the latest member revision in the 

trunk. 

Member Branch Tip checks out the latest revision along the 

member’s current branch of development. 

The Revision tab allows you to select a specific member 

revision to check out. Choose a revision from the member 

history. 

76 > > > > > > > > > > > > > >


The Labels tab allows you to select a revision to check out by 

label. Choose a label from the label list. 

The General tab specifies general check out options. 

Lock Revision checks out a writable working file and 

ensures no one else can make changes to the revision while 

you have it checked out by locking the revision. A revision 

must be checked out locked if strict locking is enabled, and 

you intend to make changes to it. 

Overwrite Working File if Changed overwrites the working 

file even if it has been modified. 

The Advanced tab specifies advanced check out options. 

Update Member Revision causes the revision you check out 

to become the new member revision of the project. For 

example, if the current project member is listed as Revision 

2.3 and you check out Revision 1.7 with the Update Member 

Revision option selected, Revision 1.7 replaces Revision 2.3 

as the member revision of the project. 

Force Creation of New Branch causes VSky Software 

Manager to force the creation of a new branch on checkout. 

Restore Revision Timestamp sets the timestamp of the 

working file, to which the revision is checked out, to the 

date and time of the revision in the history. If this option is 

not set, the working file’s timestamp is set to the current 


Create Branch if Variant causes VSky Software Manager to 

create a branch off of the revision you are checking out, if 

you are working in a variant sandbox and this is the first 

time the member has been checked out. This reduces the 

possibility of locking conflicts with the member while 

work is being done in the variant and regular sandboxes. 

Keywords allows you to choose keyword expansion 

options when checking out a member. To leave keywords 

unexpanded, choose Do Not Expand from the Keywords 

drop-down list. To replace keywords in the revision with 

literal values in the working file, select Expand from the 

Keywords drop-down list. To unexpand keywords in the 

working file, select Unexpand from the Keywords dropdown 

list. 

> > > > > > > > > > > > 77


4 To check out the member, click OK. To check out all remaining 

members, click OK to All. To cancel the check out without 

checking out the member, click Cancel. 

The member is checked out for editing, indicated by a lock 

icon, who locked the revision, and when. 

To check out a member in the command line interface 

Use the si co command, for example: 

si co --sandbox=value --revision=value member 

where 

--sandbox=value specifies the sandbox containing the member 

you want to check out, for example, c:/sandboxdemo/ 

project.pj. 

--revision=value specifies the revision you want to check out, 

for example, 1.1. If the revision is not specified, the member 

revision is checked out. 

member specifies the member you want to check out, for 

example, demoapp.ico. 

VSky Software Manager confirms the member is checked out. 

Viewing and Editing a Member 

You can open a member in your default editor application (for 

example, Microsoft Windows Notepad or MKS Toolkit’s vi editor). 

Whether you can edit or just view the contents of the member 

78 > > > > > > > > > > > > > >

To configure your default 

editor, see “Setting 

Preferences” on page 26. 

Scanning Your 

Sandbox for 

Changes 

Viewing and Editing a Member 

depends upon whether you have read-only or read-write access to 

the member. You must have a member locked in your name to be 

able to check it in. 

To view or edit a member in the graphical user interface 

1 With a Sandbox window open, select the member you want to 

view or edit. 

2 Choose Member > Edit Working File, or click . 

The member’s working file is opened in your default editor, or 

in the editor associated with the file’s extension. 

Member information in a Sandbox window is automatically 

updated whenever changes are made, for example, if another user 

locks a member; however, changes to a working file are not 

immediately displayed. 

To scan a sandbox for changes in the graphical user interface 

1 With a Sandbox window open, select the members you want to 

scan for changes. 

2 Choose Member > Scan for Changes. 

The sandbox window displays members whose working file 

has changed (indicated by working file deltas - ), or a 

message informing you there are newer revisions available in 

the Member History (indicated by member deltas - ). 

To view or edit a member in the command line interface 

Use the si edit command, for example: 

si edit --sandbox=value member 

where 

> > > > > > > > > > > > 79



you want to view or edit, for example, c:/sandboxdemo/ 

project.pj 

member specifies the member you want to view or edit, for 

example, demoapp.ico 

The member’s working file is opened in your default editor, or in 

the editor associated with the file’s extension. 

To scan a sandbox for changes in the command line interface 

To scan for changes in a sandbox, use the si viewsandbox 

command, for example: 

where 

Checking In a Member 

si viewsandbox --sandbox=value 

--sandbox=value specifies the sandbox you want to scan for 

changes, for example, c:/sandboxdemo/project.pj 

VSky Software Manager displays changes in the sandbox, for 

example: 

c:/sandboxdemo/subproject.pj subproject 

c:/sandboxdemo/demoapp.c archived 1.1 gmiller May 5, 

2000 - 4:21 PM 

Working file 9 bytes larger, newer (May 8, 2000 - 

10:32:19 PM) 

c:/sandboxdemo/demoapp.h archived 1.1.1.1 

c:/sandboxdemo/demoapp.ico archived 1.1 

c:/sandboxdemo/demoapp.ini archived 1.1 

When you are satisfied with the changes you have made to a 

member, you should check in the member to preserve those 

changes as a new revision in the member’s history. Members 

should be checked in on a regular basis. 

80 > > > > > > > > > > > > > >

Starting a 

Branch When 

Checking In a 

Member 

Assigning 

Revision 

Numbers 


VSky Software Manager usually places new revisions at the top of 

the trunk, assigning them two-part revision numbers, such as 1.15. 

There are times, however, when you do not want your work to be 

checked into the trunk. You may be pursuing a line of development 

that will not be included in the finished product, for instance, or 

you may be doing post-release maintenance while development for 

the next release continues on the trunk. 

Divergent lines of development in the same archive are managed 

through the use of branches. A branch is an independent revision 

line that uses an existing revision as its starting point. Members of a 

branch revision are identified by their revision numbers. Whereas 

revisions on the trunk are characterized by two-part revision 

numbers (for example, 1.2 or 3.5), branch revision numbers are 

prefixed with the number of the revision they start from. For 

example, if a branch revision is started from revision number 1.2, 

the members of that branch are numbered 

1.2.1.3 

1.2.1.2 

1.2.1.1 

and so on. The first two digits of the number identify the revision 

where the branch diverges from the trunk, and the last two 

represent a position on the branch. 

By default, when you check in a member, VSky Software Manager 

automatically assigns a unique revision number to the new 

revision. It does this by incrementing the current revision number 

by one. For example, if the previous revision is 1.3, the new revision 

is assigned number 1.4. 

You can choose the revision number of the changes you are 

checking in, so long as your revision number: 

is greater than the last revision number (you cannot use 

previously “skipped” revision numbers) 

has no leading zeros (zeros as complete revision numbers are 

acceptable) 

starts a new branch based on an existing revision 

> > > > > > > > > > > > 81


Assigning 

Revision 

Descriptions 

If you check in a revision using an already existing revision 

number, VSky Software Manager attempts to add one to the 

revision number and check it in as that revision. If that revision 

already exists, VSky Software Manager then chooses the next 

available branch number and creates a new branch. 

For example, if you are checking in a new revision to an archive 

where the head revision is 1.7, the following numbers are valid: 

1.8 (greater than head revision)—if you check in a revision as 

1.7, which already exists, VSky Software Manager assigns it 1.8 

1.10 (greater than head revision) 

1.72 (although misleading—none of the numbers between 7 

and 72 may be used afterward) 

2.0 is valid 

1.7.1.1 is valid (if it starts a new branch) 

The following numbers are invalid: 

1.3, even if there was no revision 1.3 previously (VSky Software 

Manager branches the archive and assigns 1.3.x.1, where x is 

the first available branch number) 

1.08 (leading 0 in last portion) 

02.1 (leading zero in branch number) 

A revision description is text that becomes a permanent part of the 

archive’s metadata. It allows you to provide a record of the changes 

you made and why you made them. This can be of great value to 

you or other team members if it ever becomes necessary to revise or 

update the member. 

Once a new revision has been checked in, its revision description 

cannot be changed, although you can append new information to a 

revision description. 

To check in a member in the graphical user interface 


check in. 

2 Choose Member > Check In, or click . 

82 > > > > > > > > > > > > > >

The Check In dialog box appears. 


3 Click an option tab, if necessary, then fill in or modify the 

check-in options: 

In the Revision Description field, enter a comment about the 

new revision. For example, you can enter a detailed description 

of what you changed, what bug in the software the changes 

were meant to correct, or instructions for the next person who 

works on the member. 

The General tab specifies general check in options. 

Label is a unique string that identifies the new revision. 

Revision labels are usually assigned during check in, but 

can be assigned later, for instance, using the Member > Add 

Label command. 

Move Existing Label moves the label if it already exists on 

another revision. 

Lock Revision causes VSky Software Manager to check in 

the working file, then immediately lock the new revision. 

This allows you to update the archive while retaining 

control of the revision. If this option is not selected, the 

working file is checked into the archive unlocked. 

Check In if Unchanged checks in the working file even if it 

has not changed since it was checked out. 

> > > > > > > > > > > > 83


Update Member Revision makes the new revision the 

member revision in the project, replacing the existing 

member revision. 

The Advanced tab specifies advanced check in options. 

Author is the author name applied to the revision. If 

necessary, enter a name. The user name specified in the 

Add Members command configuration appears by default. 

Retain Working File causes VSky Software Manager to 

check in the working file and immediately resynchronize it. 

If this option is cleared, the working file is deleted after it is 

checked in. 

Unexpand Keywords replaces literal values in the new 

revision with keywords. 

Revision Number specifies the revision number you want to 

assign to the revision. By default, VSky Software Manager 

creates the next logical revision number, for example, 1.1 

to 1.2. Optionally, you can enter a revision number. 

Force Creation of New Branch causes VSky Software 

Manager to create a branch off of the revision you are 

checking in. 

Save Working File Timestamp sets the timestamp of the 

revision in the history to the timestamp of the working file 

rather than the time of check in. 

4 To check in the member, click OK. To check in all remaining 

members, click OK to All. To cancel the check in without 

checking in any members, click Cancel. 

The member is checked in. 

To check in a member in the command line interface 

Use the si ci command, for example: 

si ci --sandbox=value member 

where 


you want to check in, for example, c:/sandboxdemo/ 

project.pj 

84 > > > > > > > > > > > > > >

Comparing a Member’s Working File to Its Member Revision 

member specifies the member you want to check in, for example, 

demoapp.ico 

VSky Software Manager confirms the member is checked in. 

Comparing a Member’s Working File to Its 

Member Revision 

After you have made changes to a member’s working file, you 

usually check those changes back into the member history as a new 

revision. But you may also decide that those changes should be 

discarded. Before you make this decision, you have to be able to 

view the changes that you are checking in, or those that you are 

discarding if you choose. 

VSky Software Manager Visual Difference allows you to view the 

differences between the member’s working file and its member 

revision. 

To compare a member’s working file to its member revision in 

the graphical user interface 

1 With a Sandbox window open, select a member that has a 

modified working file (indicated by a working file delta ), or 

a member that has a new revision available (indicated by a 

member delta ). 

2 Choose Member > Differences, or click . 

Visual Difference launches and displays the member’s working 

file and member revision side-by-side, highlighting the 

differences between them, or VSky Software Manager informs 

you there are no differences between the files. 

> > > > > > > > > > > > 85


For more information on using VSky Software Manager Visual 

Difference, see Visual Difference Online Help. 

To compare a working file to its member revision in the 

command line interface 

Use the si diff command, for example: 

si diff --sandbox=value member 

where 


containing the member you want to compare, for example, 


member specifies the member whose working file and member 

revision you want to compare, for example, demoapp.c 

VSky Software Manager displays the differences between the 

member’s working file and member revision, for example: 

c:/sandboxdemo/demoapp.c“c:/sandboxdemo/ 

demoapp.c”: Differences between Revision 1.1 and 

working file c:/sandboxdemo/demoapp.c 

5c5 

< * (c) 1999 ABC Systems Inc. 

--- 

> * (c) 2000 ABC Systems Inc. 

9c9,11 

< * 

--- 

> * Second Draft: Geoff Miller 

> * Date: September 2000 

> 

86 > > > > > > > > > > > > > >

Discarding Changes 

to Member Working Files 

Discarding Changes to Member Working Files 

If you are sure you do not want to check in a member’s modified 

working file, you can revert it to its state before it was checked out. 

To discard changes to a member’s working file in the graphical 

user interface 

1 With a Sandbox window open, select one or more members 

that are checked out in your name and/or have been modified. 

2 Choose Member > Revert, or click . 

A confirmation dialog box appears if the working file has been 

modified. 

3 To proceed with the revert operation for a member, click Yes 

(for multiple members click Yes to All). Otherwise, click No (or 

No to All for multiple members). To cancel the operation, click 

Cancel. 

The member is reverted to its original state, prior to check out. 

To discard changes to a member’s working file in the 


Use the si revert command, for example: 

si revert --sandbox=value member 

where 

--sandbox=member specifies the path and name of the sandbox 

containing the member you want to revert, for example, 

c:/sandboxdemo/project.pj 

> > > > > > > > > > > > 87


Resynchronizing Members 

member specifies the member you want to revert, for example, 

demoapp.ini 

If the working file has been modified, enter y to confirm you want 

to overwrite the working file. 

VSky Software Manager confirms the member is reverted to its 

original state, prior to check out. 

When many users are working from sandboxes based on the same 

master project, it is common for the members in an individual 

sandbox to become out of sync with the member revisions in the 

master project. For example, the member revision of a particular 

file may be at 1.5, while you still have revision 1.2 in your sandbox. 

When this happens, a member delta symbol ( ) appears next to the 

member in the graphical user interface, signaling its status. In the 

command line interface, you can use the si viewsandbox 

command to display changes to files and archives. To update out of 

sync members to the most current revisions, you resynchronize the 

members. 

To resynchronize a member in the graphical user interface 

1 With a Sandbox window open, select one or more members 

that contain member deltas. 

2 Choose Member > Resynchronize, or click . 

If the working file is writeable, you will be asked to confirm 

overwriting it. 

88 > > > > > > > > > > > > > >

Locking a Member 

3 To resynchronize the member, click Yes (for multiple members, 

click Yes to All). To cancel resynchronizing the member, click No 

(for multiple members, click No to All). To cancel the operation, 

click Cancel. 

The selected member is updated. 

To resynchronize a member in the command line interface 

Use the si resync command, for example: 

si resync --sandbox=value member 

where 

Locking a Member 

--sandbox=value specifies the sandbox containing members 

you want to resynchronize, for example, c:/sandboxdemo/ 

project.pj 

member specifies the members you want to resynchronize, for 

example, demoapp.ini 

VSky Software Manager confirms the member is updated. 

When you want to prevent other users from changing a member 

you are working on, you can lock the member. Normally you lock a 

member during a check out. Sometimes, however, you may have 

made changes to a working file that was not checked out in your 

name first. In this case, you can set a lock without overriding your 

changes. 

In the graphical user interface, a locked member is denoted with a 

padlock symbol ( ), along with the locker’s name, and the date 

and time the member was locked. 

Note 

Locking a member does not affect the working file in any way. 

VSky Software Manager does not make the working file writable if it 

was read-only, and does not verify that it corresponds to the revision 

being locked. Make sure the working file corresponds to the revision 

you want to lock. 

> > > > > > > > > > > > 89


To lock a member in the graphical user interface 

1 With a Project or Sandbox window open, select one or more 

members to lock. 

2 Choose Member > Lock or click . 

A padlock symbol and lock information appears in the 

member’s Locked column. 

To lock a member in the command line interface 

Use the si lock command, for example: 

si lock --sandbox=value member 

where 

Unlocking a Member 


you want to lock, for example, c:/sandboxdemo/project.pj 

member specifies the member you want to lock, for example, 

demoapp.ico 

VSky Software Manager confirms the member is locked. 

When you no longer need the exclusive ability to change a member, 

you can unlock it again. This is normally done by default when you 

check the member in. You can unlock a member without checking it 

in, but your changes will not be recorded if you choose to do so. 

Depending upon what permissions your administrator has 

defined, you may be able to unlock a revision that is locked by 

another user. 

90 > > > > > > > > > > > > > >

To unlock a member in the graphical user interface 

Using Keywords 


locked members to unlock. 

2 Choose Member > Unlock, or click . 

The revision is unlocked and the padlock symbol ( 

removed. 

) is 

To unlock a member in the command line interface 

Use the si unlock command, for example: 

si unlock --sandbox=value member 

where 



you want to unlock, for example, c:/sandboxdemo/ 

project.pj 

member specifies the member you want to unlock, for example, 

demoapp.ico 

VSky Software Manager confirms the member is unlocked. 

Keywords are placeholders that can be inserted into text-based 

working files. VSky Software Manager updates them with 

information about the revision or archive. 

To use a keyword, simply include it in a working file, surrounded 

by dollar signs (for example, $Date$) and check the file back into its 

archive. 

The next time you check out the revision, VSky Software Manager 

scans it for keywords and replaces them with the appropriate 

information, if keyword expansion is turned on. 

For example, if the $Date$ keyword is encountered, the date and 

time of the revision (assigned at check in) is added to the working 

file as part of the keyword. When expanded, the entry would look 

something like 

$Date: 2000/06/12 10:25:32$ 

> > > > > > > > > > > > 91


For information on setting 

command keyword 

options, see “Setting 

Command Preferences” on 

page 30. 

For information on setting 

each command’s keyword 

options, see Vertical Sky 

Software Manager Reference 

or man pages. 

This method of adding or updating information in a keyword is 

called keyword expansion. 

Here’s another example. If the member main.c has the keywords 

$Author$ and $State$ embedded within it, checking out main.c 

and issuing the command 

returns 

ident main.c 

main.c: 

$author: paula_t $ 

$state: Exp $ 

The following VSky Software Manager commands contain 

keyword expansion options: 

Add Members 

Check Out 

Check In 

Resynchronize 

Revert Member 

Keyword expansion is configured using the Preferences dialog box 

in the graphical user interface or the si setprefs command in the 

command line interface. The command line interface settings and 

dialog boxes in the graphical user interface can override the default 

settings. 

settings. Note settings. 

Keyword expansion applies to text files only. It is disabled for binary 

files. 

Text before and after the keyword is preserved, making it suitable 

for use within expressions, as above, and within comments. 

If keyword expansion is enabled and you are checking out a text 

file that contains the string 

$Revision$ 

VSky Software Manager, when it encounters this string, 

automatically adds the value of the keyword $Revision$ in the 

format 

$Revision: value $ 

92 > > > > > > > > > > > > > >

Locating 

Keywords 

For more information 

about the ident command, 

see Vertical Sky Software 

Manager Reference or the 

online man pages. 


where value is the appropriate value of the keyword (in this case, 

the revision number). 

For example, including the statement 

char revnum[] = "$Revision$"; 

in a C source file creates a character string named revnum 

containing the file’s revision number. The program can then be 

configured to display this string when it starts up, automatically 

presenting the current revision of the program’s source file. 

Using the $Revision$ keyword to obtain the revision number of a 

file is one of the common applications of keywords. Other common 

applications include: 

The $Header$ keyword provides a one-line summary of useful 

information associated with a revision. Including this 

information in a comment makes the information available to 

anyone looking at the member. 

The $Log$ keyword supplies the same sort of information as 

$Header$ plus the revision description. The $Log$ keyword 

provides a complete list of changes that have been made to the 

member over time. 

You can use the ident command in the command line interface to 

locate and display keywords (expanded or unexpanded) in one or 

more members. 

This command displays the name of each member that contains 

keywords, as well as the keywords themselves. This provides an 

easy way to extract identification information from source files, as 

well as compiled object files. 

> > > > > > > > > > > > 93


Table of 

Keywords 

VSky Software Manager maintains several keywords that can be 

used in working files. The following table describes each keyword 

and what it expands to. 

Note 

Keywords are case-sensitive. 

Keyword Expands To 

$Author$ The author name of the user who checked in 

the revision. 

$Date$ The check in date and time of the revision 

(assigned at check in). The time is shown in 

Greenwich Mean Time (GMT/UTC). 

$Header$ The file name of the archive, as well as the 

revision number, date and time, author, state, 

and locker (if locked). 

$Id$ The same as $Header$. 

$Locker$ The user name of the user who locked the 

revision (empty if not locked). 

$Log$ The revision description supplied during check 

in, preceded by the archive’s member name, 

revision number, author, and revision date. 

Repeated check out operations append 

revision descriptions, rather than replacing 

existing ones. 

$Name$ The revision label (or labels) attached to a 

revision. 

$ProjectName$ The fully qualified name of the project of which 

the archive is a member of. 

$ProjectRevision$ The revision number of the project with which 

the archive is related with. 

$RCSfile$ The archive’s unqualified member name. 

$Revision$ The revision number. 

$Source$ The same as $RCSfile$. 

$State$ The revision’s state setting. 

94 > > > > > > > > > > > > > >

Managing Projects, 

Sandboxes, 

and Members 

4 

Vertical Sky Software Manager allows you to perform a variety of 

functions to manage your projects, sandboxes, and members during 

your development cycle. For example, you can freeze members to 

prevent changes and thaw them to allow changes. You can also 

checkpoint projects to provide a snapshot of their contents at 

particular development points, so you can always reproduce 

complete project configurations (including the files and the 

directory trees they reside in) at any time in the future. 


viewing and editing project and sandbox information 

viewing a project history 

viewing and editing member information 

updating a member revision 

adding and removing project and member labels 

promoting and demoting projects and members 

freezing and thawing project members 

checkpointing a project 

using VSky Software Manager Reporter 

> > > > > > > > > > > > 95

Managing Projects, Sandboxes, and Members 

Viewing and Editing Project Information 

To view or edit project information in the graphical user 

interface 


sandbox. 

2 From a Project window, choose Project > Project Information. 

From a Sandbox window, choose Sandbox > Project 

Information. 

The Project Information dialog box appears. 

3 View or make changes to the project information as required. 

The General tab displays general project information. 

Project Name is the path and name of the project. 

Server is the Vertical Sky Server name and port number 

where the project resides. 

Revision is the project’s current revision number. 

Last Checkpointed is the last date and time the project was 

checkpointed. 

Members is the number of members in the project. 

Subprojects is the number of subprojects in the project. 

Description is a free-form text description of the master 

project. Edit the existing description, or enter a description. 

96 > > > > > > > > > > > > > >

Viewing and 

Editing Project 

Attributes 

Viewing and Editing Project Information 

Attributes define local variables or set options. You can set master 

project attributes that apply across an entire project or sandbox 

attributes that apply only in your workspace, sometimes 

overriding project attributes. They have either of the following 

formats: 

variable 

variable=value 

To view or edit project attribute information in the graphical 


1 Click the Attributes tab. 

The Attributes panel appears. 

2 In the Variable field, enter a variable, for example, OS. 

3 In the Value field, enter a value, for example, Win32. 

4 To add the attribute, click Add. To remove attributes, select 

them, then click Remove. 

The attributes appear in the attributes list. 

Viewing and Editing Development Path Information 

The Development Paths tab shows a selectable list of different 

development paths created from the current project. 

> > > > > > > > > > > > 97


To create a development 

path, see “Creating a 

Development Path” on 

page 72. 

To view or edit project development path information in the 

graphical user interface 

1 Click the Development Paths tab. 

The Development Paths panel appears. 

2 To delete a development path, select one from the list. 

3 Click Delete. 

Note 

You can also remove development paths using the Remove 

Development Path command. For more information, see “Removing a 

Development Path” on page 73. 

The development path is removed from the list. 

To save project information in the graphical user interface 

To accept any changes you have made, click OK. To cancel the 


The project information is saved. 

To view project information in the command line interface 

Use the si projectinfo command, for example: 

si projectinfo --project=value 

where 

98 > > > > > > > > > > > > > >

For a complete list of each 

command’s options, see 



man pages. 

Viewing Sandbox Information 

--project=value specifies the project whose information you want 

to view, for example, --project=c:/Docs Vertical Sky Server/ 


VSky Software Manager displays the project’s information, for 

example: 

Project Name: c:/Docs Vertical Sky Server/Projects/ 

masterdemo/project.pj 

Server: localhost:7005 

Revision: 1.1 

Last Checkpointed: Apr 18, 2000 - 2:21 PM 

Members: 3 

Sub-Projects: 1 

Description: master demo files 

Attributes: OS=Win32 

Development Paths: Variant Project 

To edit project information in the command line interface 

To set the project description, use the si setprojectdescription 

command. 

To add project attributes, use the si addprojectattr command. 

To remove project attributes, use the si dropprojectattr 

command. 

To create a development path, see “Creating a Development Path” 

on page 72. 

To remove a development path, see “Removing a Development 

Path” on page 73. 


To view sandbox information in the graphical user interface 

Note 

You cannot edit sandbox information. 

1 With a Sandbox window open, select the sandbox. 

2 Choose Sandbox > Sandbox Information. 

> > > > > > > > > > > > 99


The Sandbox Information dialog box appears. 

The General tab displays general sandbox information. 

Sandbox Name is the path and name of the sandbox. 

Project Name is the path and name of the master project. 

Server is the Vertical Sky Server name and port number 

where the master project resides. 

Revision is the master project’s current revision number. 

Last Checkpointed is the last date and time the master 

project was checkpointed. 

Members is the number of members in the sandbox. 

Subsandboxes is the number of subsandboxes in the 

sandbox. 

Project Description is a description of the master project. 

To view project attributes in the graphical user interface 

1 Click the Project Attributes tab. 

100 > > > > > > > > > > > > > >

The Project Attributes panel appears. 


2 To close the Sandbox Information dialog box, click OK or Cancel. 

To view sandbox information in the command line interface 

Use the si sandboxinfo command, for example: 

si sandboxinfo --sandbox=value 

where 

--sandbox=value specifies the sandbox whose information you 

want to view, for example, --sandbox=c:/sandboxdemo/ 

project.pj 

VSky Software Manager displays the sandbox’s information, for 

example: 

Sandbox Name: c:/sandboxdemo/project.pj 

Project Name: c:/masterdemo/project.pj 

Server: localhost:7005 

Revision: 1.1 

Last Checkpoint: Apr 18, 2000 - 2:21 PM 

Members: 3 

Subsandboxes: 1 

Description: master demo files 

Project Attributes: OS=Win32 

> > > > > > > > > > > > 101


Viewing a Project History 

When you want to view the history of a project, you can open its 

project history. Opening the project history of a sandbox is the same 

as viewing the project history of its master project. 

To view a project history in the graphical user interface 


sandbox. 

2 From a Project window, choose Project > View Project History. 

From a Sandbox window, choose Sandbox > View Project 

History. 

The Project History window appears. 

To view a project history in the command line interface 

Use the si viewprojecthistory command, for example: 

si viewprojecthistory --project=value 

where 

--project=value specifies the path and name of the project whose 

history you want to view, for example, --project=c:/Docs 

Vertical Sky Server/Projects/masterdemo/project.pj 

VSky Software Manager displays the project history, for example: 

c:/Docs Vertical Sky Server/Projects/masterdemo/ 

project.pj 

1.2 knovak Sep 12, 2000 - 11:14 AM Exp Beta Fixes 

made beta fix changes 

1.1 knovak Sep 12, 2000 - 10:22 AM Exp 

c:/Docs Vertical Sky Server/Projects/masterdemo/ 

project.trn 

102 > > > > > > > > > > > > > >

Viewing and Editing Member Information 


states, see “Promoting 

Members” on page 113. 


To view or edit member information in the graphical user 

interface 

1 With a Project or Sandbox window open, select the member 

whose information you want to view or edit. 

2 Choose Member > Member Information, or click . 

The Member Information dialog box appears. 

3 View or make changes to the member information as required. 

Member Name is the path and name of the member. 

Project/Sandbox Name is the path and name of the 

member’s project or sandbox. 

Member Revision is the displayed member revision. To 

select another member revision, choose a revision from the 

Member Revision drop-down list. 

Created By is the name of the user who created the revision 

and the date and time it was created. 

State is the state assigned to the revision. To change the 

state of the revision, choose a state from the State dropdown 

list. 

> > > > > > > > > > > > 103


Viewing and 

Editing Member 

Attributes 


attributes, see Vertical Sky 



Revision Description is a brief description of the revision. 

You cannot change an existing revision description from 

this dialog box, but you can append additional comments 

to it. To do so, enter any supplemental information in the 

Revision Description field below the present information 

(indicated by a line if an existing description is present). 

Within the Member Information dialog box, you can also add or 

remove member attributes that allow you to categorize members, 

and then perform an operation on them as a group. 

For example, you could use the Select command to highlight only 

those members with the attribute sys=dos and then check them out 

as a group. 

Every project member can have any number of attribute statements 

that define variables for the member. Attributes have either of the 

formats: 

variable 

variable=value 

To view or edit member attributes in the graphical user 

interface 

1 Click the Attributes tab. 

The Attributes panel appears. 

104 > > > > > > > > > > > > > >

Viewing and Editing Member Labels 

You can also add labels to a 

revision using the Add 

Label command. For more 

information, see “Adding 

Labels to Members” on 

page 109. 


2 In the Variable field, enter a variable, for example, sys. 

3 In the Value field, enter a value, for example, dos. 

4 To add the attribute, click Add. To remove an attribute, select 

them, then click Remove. 

The attributes appear in the attributes list. 

Labels are unique text that describe and refer to a revision of a 

member. Labels can be based on the product release the revision 

was included in, on the content of the revision, on changes made to 

the revision, or any other sort of information that would be useful 

in identifying that particular revision. 

Although you generally assign a label to a new revision upon check 

in, there may be times when you want to add an additional label or 

change the label assigned to a revision. 

To view or edit a member’s label in the graphical user 

interface 

1 Click the Labels tab. 

The Labels panel appears. 

2 In the Label field, enter a label for the member revision, for 


> > > > > > > > > > > > 105


For a complete list of each 




man pages. 

3 To add the label, click Add. 

4 To remove an existing label, select it from the list of labels, then 

click Remove. 

To save member information in the graphical user interface 

When you are finished viewing or editing the member information, 

click OK to accept the changes. To cancel the operation, click Cancel. 

The member information is saved. 

To view member information in the command line interface 

Use the si memberinfo command, for example: 

si memberinfo --sandbox=value member 

where 


whose information you want to view, for example, 


member specifies the member whose information you want to 

view, for example, demoapp.c 

VSky Software Manager displays the member’s information, for 

example: 

Member Name: c:/sandboxdemo/demoapp.c 


Member Revision: 1.2 

Created By: gmiller on Apr 24, 2000 - 3:49 PM 

State: Exp 

Revision Description: 

fixed anchoring problem 

Labels: Draft1 

Attributes: sys=dos 

To edit member information in the command line interface 

To change a member’s state, see “Promoting Members” on page 113 

and “Demoting Members” on page 115. 

To append a revision description to the member, use the 

si appendrevdesc command. 

To add member attributes, use the si addmemberattr command. 

To remove member attributes, use the si dropmemberattr 

command. 

106 > > > > > > > > > > > > > >

Updating a Member’s Revision 

To add or remove member labels, see “Adding Labels to Members” 

on page 109 and “Deleting Member Labels” on page 110. 

Updating a Member’s Revision 

Within the graphical user interface, you can use the Update Member 

Revision option when you are checking in a member to ensure the 

most recent revision of each member is added to the list of 

members in the project. 

If this option is not enabled, the project list might not reflect the 

most current revision of each member’s history. 

For example, if the current project member is revision 2.7 of an 

archived file, but a newer revision (revision 2.8) has been added to 

the member’s history, you can update the member to the new 

revision. 

To update a member’s revision in the graphical user interface 


members to update. 

2 Choose Member > Update Revision. 

The Set Member Revision dialog box appears. 

> > > > > > > > > > > > 107


3 Click an option tab, if necessary, then fill in or modify the set 

member revision options. 

The Selection tab allows you to select a revision to update to. 

To select a pre-defined revision to update, click Pre-Defined 

Revision, then choose a pre-defined revision from the dropdown 

list. The available pre-defined revisions are: 

Head updates the member revision to the member’s head 

revision. 

Trunk Tip updates the member revision to the latest 

revision in the trunk, independent of default branch 

settings. 

Member Branch Tip updates the member revision to the 

latest revision along the member’s current branch of 

development. 

To select a specific revision, click Specific Revision, then click 

the Revisions or Labels tabs to choose a revision. 

The Revisions tab allows you to select a specific revision to 

make the member revision. 

The Labels tab allows you to make a specific labeled 

revision the member revision. 

4 To set the member revision, click OK (for multiple members, 

click OK to All). To cancel the operation, click Cancel. 

The member is updated. 

To update a member revision in the command line interface 

Use the si updaterevision command, for example: 

si updaterevision --sandbox=value --revision=value 

member 

where 


you want to update, for example, c:/sandboxdemo/ 

project.pj 

--revision=value specifies the revision number you want to 

update, for example, 1.2 

member specifies the member you want to update, for example, 

demoapp.ico 

108 > > > > > > > > > > > > > >

Adding Labels to Members 

Adding Labels to Members 

VSky Software Manager confirms the member is updated. 

Labels are unique text that describe and refer to a revision. Labels 

can be based on the product release the revision was included in, 

on the content of the revision, on changes made to the revision, or 

any other sort of information that would be useful in identifying 

that particular revision. 

Although you generally add a label to a new revision upon check 



To add a label to a member in the graphical user interface 


members to label. 

2 Choose Member > Add Label. 

The Add Label dialog box appears. 

Note 

:member appears in the Revision field indicating the label will be 

applied to the member revision. 

> > > > > > > > > > > > 109


3 In the Label field, enter a label for the member, for example, 

Draft1. 

Note 

You can also add labels to the member in the Member Information 

dialog box. 

4 To move the label, if it already exists on another revision, select 

the Move Existing Label checkbox. 

5 To accept the new label, click OK (for multiple members, click 

OK to All). To cancel the operation, click Cancel. 

The member is labeled. 

To add a label to a member in the command line interface 

Use the si addlabel command, for example: 

si addlabel --sandbox=value --label=value member 

where 

Deleting Member Labels 


you want to label, for example, c:/sandboxdemo/project.pj 

--label=value specifies the label you want to apply to the 

member, for example, Draft1 

member specifies the member you want to label, for example, 

demoapp.ico 

VSky Software Manager confirms the member is labeled. 

Sometimes you may want to delete a label revision. For instance, 

you may decide the label no longer accurately reflects that 

particular revision. In addition, if you have assigned the same label 

to a number of members, you might want to remove them all with 

one command. 

To delete a member label in the graphical user interface 


members to delete labels from. 

110 > > > > > > > > > > > > > >

2 Choose Member > Delete Label. 

The Delete Label dialog box appears. 

3 Select a label to delete from the Label drop-down list. 

Deleting Member Labels 

Note 

You can also delete a member’s labels in the Member Information dialog 

box. 

4 To accept the deletion, click OK (for multiple members, click OK 

to All). To cancel the operation, click Cancel. 

The member label is deleted. 

To delete a member label in the command line interface 

Use the si deletelabel command, for example: 

si deletelabel --sandbox=value --label=value member 

where 


you want to delete a label from, for example, c:/sandboxdemo/ 

project.pj 

--label=value specifies the label you want to delete from the 


member specifies the member you want to delete a label from, 

for example, demoapp.ico 

VSky Software Manager confirms the member label is deleted. 

> > > > > > > > > > > > 111


Adding Labels to Projects 

Just as you can with project members, you can add labels to project 

revisions. 

To add a label to a project in the graphical user interface 

1 With a Project History window open, select the revision you 

want to label. 

2 Choose History > Add Label, or click . 

The Add Project Label dialog box appears. 

3 In the Label field, enter a label for the project, for example, Bug 

Fixes. 

4 To move a label, if it already exists, onto another revision, select 

the Move Existing Label checkbox. 

5 To accept the new label, click OK. To cancel the operation, click 

Cancel. 

The project revision is labeled. 

To add a label to a project in the command line interface 

Use the si addprojectlabel command, for example: 

where 

si addprojectlabel --project=value --label=value 


want to add a label to, for example, c:/masterdemo/ 

project.pj 

--label=value specifies the label you want to add to the project, 

for example, Bug Fixes 

VSky Software Manager confirms the label is added to the project. 

112 > > > > > > > > > > > > > >

Deleting Project Labels 

Deleting Project Labels 

Just as you can with project members, you can delete project labels. 

To delete a project label in the graphical user interface 

1 With a Project History window open, choose History > Delete 

Label, or click . 

The Delete Project Label dialog box appears. 

2 From the Label drop-down list, choose a label to delete from the 

project, for example, Bug Fixes. 

3 To confirm the deletion, click OK. To cancel the operation, click 

Cancel. 

The project label is deleted. 

To delete a project label in the command line interface 

Use the si deleteprojectlabel command, for example: 

si deleteprojectlabel --project=value --label=value 

where 

Promoting Members 


want to delete a label from, for example, c:/masterdemo/ 

project.pj 


project, for example, Bug Fixes 

VSky Software Manager confirms the project label is deleted. 

At particular milestones, project members are ready to move to the 

next stage of their development cycle (for example, from 

Development to Testing). 

> > > > > > > > > > > > 113


If no state is assigned to a revision at check-in, a default value of 

Exp (for Experimental) is used. 

To promote a member in the graphical user interface 


members to promote. 

2 Choose Member > Promote. 

The Promote Member dialog box appears. 

Note 

:member appears in the Revision field indicating the member revision 

will be promoted. 

3 Select a new state from the Promote to State drop-down list, for 

example, Beta. 

4 To accept the new promotion state, click OK (for multiple 

members, click OK to All). To cancel the operation, click Cancel. 

The member is promoted. 

To promote a member in the command line interface 

Use the si promote command, for example: 

si promote --sandbox=value --state=value member 

where 


you want to promote, for example, c:/sandboxdemo/ 

project.pj 

--state=value specifies the state you want to promote the 

member to, for example, Beta 

114 > > > > > > > > > > > > > >

Demoting Members 

member specifies the member you want to promote, for 

example, demoapp.c 

Demoting Members 

VSky Software Manager confirms the member is promoted. 

Project members can also be demoted to a predefined lower state of 

development. 

To demote a member in the graphical user interface 


members to demote. 

2 Choose Member > Demote. 

The Demote Member dialog box appears. 

Note 

:member appears in the Revision field indicating the member revision 

will be demoted. 

3 Select a new state from the Demote to State drop-down list, for 

example, Alpha. 

4 To accept the new state, click OK (for multiple members, click 


The member is demoted. 

> > > > > > > > > > > > 115


To demote a member in the command line interface 

Use the si demote command, for example: 

si demote --sandbox=value --state=value member 

where 

Promoting a Project 


you want to demote, for example, c:/sandboxdemo/ 

project.pj 

--state=value specifies the state you want to demote the 

member to, for example, Alpha 

member specifies the member you want to demote, for example, 

demoapp.ico 

VSky Software Manager confirms the member is demoted. 

Just as you can with a project member, you can promote the project 

itself (change its state, in other words). This can assist in 

management of an entire project through a development cycle, 

especially if the promotion functions are restricted to key project 

personnel. 

Normally, you promote a project (set its state) when you checkpoint 

it, but you can do so at any time. 

Only the project is promoted, not the members of the project. 

To promote a project in the graphical user interface 


want to promote. 

2 Choose History > Promote, or click . 

116 > > > > > > > > > > > > > >

The Promote Project dialog box appears. 

Demoting a Project 



4 To accept the new state, click OK. To cancel the operation, click 

Cancel. 

The project is promoted. 

To promote a project in the command line interface 

Use the si promoteproject command, for example: 

si promoteproject --project=value 

--projectRevision=value --state=value 

where 

Demoting a Project 


want to promote, for example, c:/Docs Vertical Sky 

Server/Projects/masterdemo/project.pj 

--projectRevision=value specifies the revision number of the 

project you want to promote, for example, 1.2 


project to, for example, Beta 

VSky Software Manager confirms the project is promoted. 

Just as you can with a project member, you can demote the project 

itself (change its state, in other words). 

Normally, you demote a project (set its state) when you checkpoint 

it, but you can do so at any time. 

Only the project is demoted, not the members of the project. 

> > > > > > > > > > > > 117


To demote a project in the graphical user interface 


want to demote. 

2 Choose History > Demote, or click . 

The Demote Project dialog box appears. 

3 Select a state from the Demote to State drop-down list, for 

example, Alpha. 

4 To accept the new state, click OK. To cancel the operation, click 

Cancel. 

The project is demoted. 

To demote a project in the command line interface 

Use the si demoteproject command, for example: 

si demoteproject --project=value 

--projectRevision=value --state=value 

where 


want to demote, for example, c:/Docs Vertical Sky 

Server/Projects/masterdemo/project.pj 

--projectRevision=value specifies the revision number of the 

project you want to demote, for example, 1.2 


project to, for example, Alpha 

VSky Software Manager confirms the project is demoted. 

118 > > > > > > > > > > > > > >

Freezing Members 

Freezing Members 

When your development team has largely finished some portion of 

a project and some project members are in a stable state, you can 

freeze individual members within a project or sandbox. Freezing 

restricts member information from being updated, preventing 

these members from being changed by accident. For example, if 

new revisions are checked into the member’s archive, 

VSky Software Manager does not update the project’s member 

revision. 

Freezing prevents VSky Software Manager from changing member 

information in the member’s project, but does not affect a member 

file itself. Revisions can still be checked out, modified, and checked 

in. 

You can change the label or state of frozen members, but not their 

attributes. 

Freezing can be used immediately before a checkpoint operation to 

ensure no one changes the project or its members before the 

checkpoint is complete. 

When you want to allow project members to be changed, you can 

thaw them (see “Thawing Members” on page 120). 

VSky Software Manager reports the availability of new revisions 

when anyone checks them into the archive. VSky Software 

Manager does not update the project to the latest revision, so an 

appropriate person must make the decision to lift the freeze and 

update the project. 

To freeze a member in the graphical user interface 


you want to freeze. 

2 Choose Member > Freeze. 

> > > > > > > > > > > > 119


A snowflake symbol appears beside the selected member. 

To freeze a member in the command line interface 

Use the si freeze command, for example: 

si freeze --sandbox=value member 

where 

Thawing Members 


you want to freeze, for example, c:/sandboxdemo/project.pj 

member specifies the member you want to freeze, for example, 

demoapp.ico 

VSky Software Manager confirms the member is frozen. 

When you decide to allow project members to evolve again, you 

can thaw any frozen ones. Thawing removes the restriction on 

changing member information in the project. 

To thaw a member in the graphical user interface 


you want to thaw (the member that has a snowflake symbol 

beside it). 

120 > > > > > > > > > > > > > >

Checkpointing a Project 

2 Choose Member > Thaw. 

The snowflake symbol beside the selected member disappears. 

To thaw a member in the command line interface 

Use the si thaw command, for example: 

si thaw --sandbox=value member 

where 


you want to thaw, for example, c:/sandboxdemo/project.pj 

member specifies the member you want to thaw, for example, 

demoapp.ico 

VSky Software Manager confirms the member is thawed. 

Note 


Thawing a member does not automatically update the project to later 

revisions of frozen members. Use si updaterevision or set 

member revision in member history using the graphical user interface. 

See “Setting the Member Revision” on page 148. 

Just as you check in a source file to preserve the changes made to it 

from one revision to another, you must also be able to track the 

evolution of a project. In VSky Software Manager, this process is 

called checkpointing. 

> > > > > > > > > > > > 121


Checkpointing saves a copy of the project in the project’s history as 

a revision, including the list of members along with their revision 

numbers and project and member attributes. 

You can use the project’s revision number to keep track of your 

projects, but to simplify post-release maintenance, use a label to 

identify significant project development milestones when you 

checkpoint a project. 

For example, if you checkpoint a project and label it with a release 

identifier (for example, Release 6.2), you can find and recreate 

that particular development state more easily. 

Note 

Checkpointing a project affects the project only; it does not check in 

every member of the project. 

If you are working in a sandbox, issuing a checkpoint command 

checkpoints the sandbox’s master project. 

If you want to create a variant or build sandbox, you must have a 

checkpointed project to start with. 

To checkpoint a project in the graphical user interface 


sandbox. 

2 From a Project window, choose Project > Checkpoint Project, or 

click . 

From a Sandbox window, choose Sandbox > Checkpoint Project, 

or click . 

122 > > > > > > > > > > > > > >

To add labels to a project 

from a Project or Sandbox 

window, see “Adding 

Labels to Projects” on 

page 112. 

The Checkpoint dialog box appears. 


3 Click an option tab, if necessary, then fill in or modify the 

checkpoint options: 

In the Checkpoint Description field, enter a description of the 

checkpoint, for example, Ready for peer review. 

The General tab specifies general checkpoint options. 

Label is a unique text string that identifies the new project 

revision, for example, Draft1. 

Apply Label to All Members applies the checkpoint label to 

all project members. 

State is a one-word description of a new revision’s status. 

Select a state from the State drop-down list, for example, 

Beta. 

Apply State to All Members applies the checkpoint state to 

all project members. 

The Advanced tab specifies advanced checkpoint options. 

Recurse into Subprojects recursively checkpoints 

subprojects. 

Author is the author name applied to the checkpoint. Your 

user name appears by default. 

> > > > > > > > > > > > 123


Revision Number is the revision number of the project. If 

you choose to specify a revision number, the number you 

supply must be higher than the head revision number (if 

you are checkpointing the main project), or the tip revision 

number (if you are checkpointing a variant project). 

4 To accept the checkpoint, click OK. To cancel the operation, 

click Cancel. 

The project is checkpointed. 

To checkpoint a project in the command line interface 

Use the si checkpoint command, for example: 

si checkpoint --project=value --description=value 

where 


want to checkpoint, for example, --project=c:/Docs 

Vertical Sky Server/Projects/masterdemo/project.pj 

--description=value specifies a description of the 

checkpointed project, for example, --description=Ready for 

peer review 

VSky Software Manager confirms the project is checkpointed. 

VSky Software Manager Reporter 

For information on 

accessing the reporting 

features through the 

command line interface, 

see “Creating a Report” on 

page 128. 

About the 

Report 

Information 

In the graphical user interface, VSky Software Manager Reporter 

analyzes projects, their members, or individual archives, and 

allows you to generate a variety of reports and graphs based on its 

findings. Reports and graphs can be printed or viewed on the 

screen. To use Reporter, you must have a default printer installed. 

Reporter calculates a summary of the changes to a project or 

archive, then displays or prints the summary as text or, for some 

reports, as a graph. Customized reports, created using Microsoft 

Access, can also be produced. 

Reporter’s data files (containing the results of its project or archive 

analysis) can be saved as text files that can be read by most 

database applications. 

124 > > > > > > > > > > > > > >

About Graphs 

Report Types 

Reporter generates: 

changes introduced by individual authors 


changes between the member revision and a revision with a 

particular label 

changes between the member revision and any other revision 

a list of locked members and the names of users who locked 

them 

a list of revisions with a particular label or state 

project member history (including revision descriptions) by file 

Whenever graphs are available in Reporter, you are given the 

option of displaying the report in a text version (the default) or as a 

graph. If you display a report as a graph, you can define how you 

want it to look. Using graphs, you can give reports a custom look to 

suit your preferences or for quick, project-specific identification. 

Reporter allows you to generate different types of reports based on 

the information VSky Software Manager maintains about project 

members and revisions in the archives. Reporter can generate the 

following report types: 

Changes Grouped by Author 

This type of report lists changes to members or revisions grouped 

by the person who made them. For example, if both Fred and Ethel 

made changes to several members, the report would include two 

sections, one for Fred and one for Ethel. Each section of the report 

shows: 

name of the member 

revision number of changed revisions 

date the change was made 

number of lines (or bytes for binary files) that were added or 

deleted 

This type of report offers two additional options: 

The report can be on a single, specified author, or all authors. 

It can be restricted to changes made before or after a specified 

date. 

> > > > > > > > > > > > 125


Changes Grouped by Author (Summary) 

This type of report shows a brief summary of changes made by 

each user. Each type of project member (Text, Binary, Auto-Detect) 

appears in a separate section of the report, subdivided according to 

the person who made the changes. The information summarized 

includes: 


total number of revisions changed by each person 

total number of lines (or bytes for binary files) that were added 

or deleted by each person 

This report type offers two additional options: 

The report can be on a single, specified author, or all authors. 

It can be restricted to changes made before or after a specified 

date. 

Revisions Newer Than Member Revision 

This report tells you which members have more recent revisions 

available. For example, if a member revision is revision number 1.3, 

but the archive contains revisions numbered 1.4, 1.5, and 1.6, this 

report lists the newer available revisions and information about 

each, including: 


revision numbers of newer revisions in the archive 

date of the newer revisions 

revision description for each newer revision 

Changes From Member Revision to Label 

This report lists all revisions in a member’s archive between the 

member revision and another revision with a specified label. This 

report can be generated for a single member, or for all project 

members. For each member, the report shows: 


revision numbers of all the revisions between the member and 

the labeled revision 

author of each revision 

date of each revision 

126 > > > > > > > > > > > > > >

evision description for each revision 


Changes From Member Revision to Revision 

This report lists all revisions in the member archive between the 

member revision and another revision with a specified revision 

number. This report can be generated for a single member, or for all 

project members. For each member, the report shows: 


revision numbers of all the revisions between the member 

revision and the selected revision number 

author of each revision 

date of each revision 

revision description for each revision 

List Locked Revisions 

This report lists all locked revisions in a project or archive. For each 

locked revision, the report lists: 


revision number 

person who has it locked 

List Revisions Associated with Labels 

This report scans the archives of all project members and extracts 

any labels they contain. For each label it finds, the report lists: 

name of the label 

name of the member archive 

revision number the label is associated with 

List Revisions Associated with States 

This report scans the archives of all project members and extracts 

any state settings they contain. For each state setting it finds, the 

report lists: 

state setting 

name of the member archive 

most recent revision with which the state is associated 

> > > > > > > > > > > > 127


Creating a Report 

Project Member History 

This report displays all the revisions of a specified project member. 

For each revision, it shows: 


revision date 

revision description 

When you choose the member to report on, you can specify that the 

information should be sorted according to Revision Number or 

Revision Date, in either ascending or descending order. 

To create a report in the graphical user interface 


sandbox you want to report on. 

2 From a Project window, choose Project > Reports. 

From a Sandbox window, choose Sandbox > Reports. 

The Select Report Type dialog box appears. 

3 To save the results of the Reporter’s analysis to data files that 

can be read by most database applications, select the Save Data 

Files checkbox. 

4 If you have created customized reports with Microsoft Access 

that you want to use with Reporter, select the Show Customized 

Reports checkbox, then specify the report name with the 

Custom Reports selector. 

128 > > > > > > > > > > > > > >


using VSky Software 

Manager Reporter, see 

Reporter Online Help. 


5 From the Report Type list, select a report type to generate, as 

described in “Report Types” on page 125. 

6 Click OK. 

If the report type requires additional information (for example, 

a range of revisions), a second dialog box appears to collect it. 

Reports appear in plain text format by default. Some report 

types, however, allow you to display the information 

graphically. 

7 To display a report as a report, click Report. To display a report 

as a graph, click Graph. 

8 If necessary, fill in any additional information. 

9 Click OK. 

The report or graph appears in a scrollable, scalable window. 

> > > > > > > > > > > > 129




Manager Reporter, see 

Reporter Online Help. 

To create a report in the command line interface 

Use the si report command, for example: 

si report --sandbox=value 

where 


you want to report on, for example, --sandbox=c:/ 

sandboxdemo/project.pj. 

The Select Report Type dialog box appears. 

Fill in the options, as described above. 

130 > > > > > > > > > > > > > >

Managing Member 

Histories 

and Revisions 

5 

While sandboxes and projects allow you to manage and access 

project members and the contents of individual members—the 

history of changes are saved in member histories. 

Vertical Sky Software Manager lets you save and recreate every 

stage (or revision) in the development of each member you use. 

When you make changes to a project member and check it back in, 

your changes are automatically added to the member history. If you 

ever need to see that version of the member again, check out the 

appropriate revision, and VSky Software Manager rebuilds an exact 

copy for you. 


viewing a member history 

viewing and editing archive information 

viewing and editing revision information 

adding and removing revision labels 

viewing and editing working files and revisions 

promoting and demoting revisions 

locking and unlocking revisions 

setting the member revision 

deleting revisions 

comparing and merging revisions 

> > > > > > > > > > > > 131

Managing Member Histories and Revisions 

Viewing a Member History 

To view a member history in the graphical user interface 


whose history you want to view. 

2 Choose Member > View Member History, or click . 

The member history appears in a Member History window. 

To view a member history in the command line interface 

Use the si viewhistory command, for example: 

si viewhistory --sandbox=value member 

where 

value specifies the path and name of the sandbox containing the 

member whose history you want to view, for example, c:/ 

sandboxdemo/project.pj 

member specifies the member whose history you want to view, 


VSky Software Manager displays the member history, for example: 

c:/sandboxdemo/demoapp.ico 

1.3 knovak Sep 12, 2000 - 3:22 PM Exp fixed printing 

bug 

1.2 knovak Sep 12, 2000 - 2:13 PM Exp Draft1 minor 

changes 

1.1.1.1 knovak Sep 12, 2000 - 1:19 PM Exp 

1.1 knovak Sep 12, 2000 - 10:51 AM Exp Initial 

revision 

132 > > > > > > > > > > > > > >

Viewing and Editing Archive Information 

Viewing and Editing Archive Information 

Just as it maintains information about each project member, 

VSky Software Manager also maintains information about each 

member archive called archive information. An archive is also where 

the history for a member is stored. 

To view or edit archive information in the graphical user 

interface 

1 With a Member History window open, choose History > Archive 

Information, or click . 

The Archive Information dialog box appears. 

2 Click an option tab, if necessary, then view or modify the 

archive information: 

The General tab specifies general archive information options. 

Member Name is the path and name of the member that the 

archive is for. 



Archive Name is the path and name of the archive whose 

information is displayed. 

Archive Type displays the type of data stored in the archive. 

> > > > > > > > > > > > 133


Default Branch specifies the starting point of the default 

branch. To specify a default branch, enter a branch number 

in the Default Branch field, for example, 2.1.1. 

Compressed specifies if the archive is compressed. To 

compress the archive, select the Compressed checkbox. 

Strict Locking specifies if a strict locking policy is in effect 

for the archive. To enable strict locking, select the Strict 

Locking checkbox. 

Store by Reference causes each revision to be saved to a 

separate file, instead of saving all revisions to one file. This 

feature improves performance for archives that contain 

large binary files. To store the archive by reference, select 

the Store by Reference checkbox. 

Archive Description describes the archive. If necessary, 

enter or edit a description. 

The Labels tab displays a list of revision labels in the archive, 

for example, Draft1 1.1. 

The Locks tab displays a list of users who have locks on 

revisions in the archive, for example, gmiller 1.2. 

3 To save your changes, click OK. To cancel the operation, click 

Cancel. 

The archive information is saved. 

To view archive information in the command line interface 

Use the si archiveinfo command, for example: 

where 

si archiveinfo --sandbox=value member 

value specifies the path and name of the sandbox containing the 

member whose archive information you want to view, for 

example, c:/sandboxdemo/project.pj 

member specifies the member whose archive information you 

want to view, for example, demoapp.ico 

VSky Software Manager displays the member’s archive 

information, for example: 

Member Name: c:/sandboxdemo/demoapp.ico 


Archive Name: c:/Docs Vertical Sky Server/Projects/ 

134 > > > > > > > > > > > > > >

Viewing and Editing Revision Information 

rcs/demoapp.ico 

Archive Type: Text 

Strict Locking 

Archive Description: made beta fix changes 

Labels: 

Draft1 1.1 

Locks: gmiller 1.2 

To edit archive information in the command line interface 

Use the si updatearchive command. 

For a complete list of the command’s options, see the Vertical Sky 

Software Manager Reference or the man pages. 


VSky Software Manager maintains detailed information about each 

member revision in a member history. In the graphical user 

interface, this revision information is displayed in columns in the 

Member History window. It can also be viewed and modified with 

the Revision Information command. 

To view or edit revision information in the graphical user 

interface 

1 With a Member History window open, select the revision 

whose information you want to view or edit. 

2 Choose History > Revision Information, or click . 

> > > > > > > > > > > > 135


The Revision Information dialog box appears. 

3 View or make changes to the member information as allowed. 

Member Name is the path and name of the member. 



Revision is the revision the information is displayed for. 

Created By is the name of the user who created the revision, 

and the date and time it was created. 

Locked By is the name of the user who locked the revision, 

and the date and time it was locked. 

Note 

Locked By information only appears if the revision is locked. 

State is the state assigned to the member. To apply a 

different state to the member, choose a state from the State 


Revision Description is a brief description of the revision. 

You cannot change an existing revision description from 

this dialog box, but you can append additional comments 

136 > > > > > > > > > > > > > >

Viewing and Editing Revision Labels 


to it. To do so, enter any supplemental information in the 

Revision Description field below the present information 

(indicated by a line if an existing description is present). 


in, there may be times you want to add an additional label or 


To view or edit revision labels in the graphical user interface 

1 Click the Labels tab. 

The Labels panel appears. 

2 In the Label field, enter a label for the revision, for example, 

Draft2. 

3 To add the label, click Add. 

4 To remove an existing label, select it from the list, then click 

Remove. 

To save revision information in the graphical user interface 

When you are finished viewing or editing the revision information, 

click OK to accept the changes. To cancel the operation, click Cancel. 

The revision information is saved. 

> > > > > > > > > > > > 137


For a complete list of the 

si appendrevdesc 




man pages. 

To view revision information in the command line interface 

Use the si revisioninfo command, for example: 

si revisioninfo --sandbox=value --revision=value member 

where 


containing the member whose revision information you want 

to view, for example, c:/sandboxdemo/project.pj 

--revision=value specifies the revision number whose revision 

information you want to view, for example, 1.2 

member specifies the member whose revision information you 

want to view, for example, demoapp.c 

VSky Software Manager displays the member’s revision 




Revision: 1.2 

Created By: knovak on Sep 12, 2000 - 11:09 AM 

State: Exp 


made Beta fix changes 

Labels: Beta Fixes 

To edit revision information in the command line interface 

To promote a revision, see “Promoting Revisions” on page 143. 

To demote a revision, see “Demoting Revisions” on page 144. 

To add a description to a revision, use the si appendrevdesc 

command. 

To add a label to a revision, see “Adding Labels to Revisions” on 

page 139. 

To delete a revision label, see “Deleting Revision Labels” on 

page 140. 

138 > > > > > > > > > > > > > >

Adding Labels to Revisions 

Adding Labels to Revisions 




To add a label to a revision in the graphical user interface 

1 With a Member History window open, select the revision you 

want to label. 

2 Choose History > Add Label, or click . 

Tip 

You can also use the Revision Information dialog box, as described in 

“Viewing and Editing Revision Information” on page 135. 

The Add Label dialog box appears. 

3 In the Label field, enter a label for the revision, for example, 

Draft1. 

4 To move an existing label from the revision, select the Move 

Existing Label checkbox. 

5 To accept a label, if it already exists, on to another revision, 

click OK (for multiple members, click OK to All). To cancel the 


The revision is labeled. 

> > > > > > > > > > > > 139


To add a label to a revision in the command line interface 

Use the si addlabel command, for example: 

si addlabel --sandbox=value --revision=value 

--label=value member 

where 

Deleting Revision Labels 


you want to label, for example, c:/sandboxdemo/project.pj 


label, for example, 1.2 

--label=value specifies the label you want to add to the 


member specifies the member you want to label, for example, 

demoapp.ico 

VSky Software Manager confirms the revision is labeled. 

To delete a revision label from a revision in the graphical user 

interface 

1 With a Member History window open, choose History > Delete 

Label, or click . 

Tip 

You can also use the Revision Information dialog box, as described in 

“Viewing and Editing Revision Information” on page 135. 

The Delete Label dialog box appears. 

140 > > > > > > > > > > > > > >

Viewing a Member’s Working File or Revision 

2 From the Label drop-down list, choose a label to delete, for 


3 To accept the deleted label, click OK (for multiple members, 

click OK to All). To cancel the operation, click Cancel. 

The revision label is deleted. 

To delete a label in the command line interface 

Use the si deletelabel command, for example: 

si deletelabel --sandbox=value --label=value member 

where 


whose label you want to delete, for example, c:/sandboxdemo/ 

project.pj 


member, for example, Beta Fixes 

member specifies the member whose label you want to delete, 


VSky Software Manager confirms the revision label is deleted. 

Viewing a Member’s Working File or 

Revision 

To view a member’s working file or revision in the graphical 


1 With a Member History window open, select the working file 

or revision you want to view. 

2 With a working file selected, choose History > View Working 

File, or click . 

With a revision selected, choose History > View Revision, or click 

. 

The member’s working file or revision is opened in your 

default editor or in the editor associated with the file’s 

extension. 

> > > > > > > > > > > > 141


To view a member’s working file or revision in the command 

line interface 

Use the si edit command, for example: 

si edit --sandbox=value --revision=value member 

where 


you want to view or edit, for example, c:/sandboxdemo/ 

project.pj 

--revision=value specifies the revision you want to view or 

edit, for example, 1.3 

member specifies the member whose working file or revision 

you want to view or edit, for example, demoapp.ico 

VSky Software Manager launches your default editor, displaying 

the working file or revision you want to view, or the editor 

associated with the member’s extension. 

Note 

The default editor that launches and opens the member depends on 

your settings in the General tab of the Preferences dialog box. To 

configure your default editor, see “Setting Preferences” on page 26. 

Although it can be used to show the contents of any revision in an 

archive, this command is typically used with the working file, since 

it provides a mechanism to open the member without leaving the 

VSky Software Manager application environment. 

When you view a revision, VSky Software Manager copies the 

revision to a read-only temporary file and opens it for you. 

Note 

The temporary file is not the revision. If you make changes to the file 

and want to save it, the actual revision is not modified. 

142 > > > > > > > > > > > > > >

Promoting Revisions 

Promoting Revisions 

Normally, you promote a member’s revision (set its state) when 

you checkpoint its master project, but you can do so at any time. 

To promote a revision in the graphical user interface 

1 With a Member History window open, select a revision to 

promote. 

2 Choose History > Promote Revision, or click . 

The Promote Member dialog box appears. 



Note 

The next highest state appears in the Promote to State drop-down list. 



The revision is promoted. 

To promote a revision in the command line interface 

Use the si promote command, for example: 

si promote --sandbox=value --revision=value 

--state=value member 

where 


you want to promote, for example, c:/sandboxdemo/ 

project.pj 

> > > > > > > > > > > > 143


Demoting Revisions 


promote, for example, 1.1 


member to, for example, Beta 

member specifies the member you want to promote, for example, 

demoapp.ico 

VSky Software Manager confirms the member is promoted. 

To demote a revision in the graphical user interface 

1 With a Member History window open, select a revision to 

demote. 

2 Choose History > Demote Revision, or click . 

The Demote Member dialog box appears. 

3 Select a new state from the Demote to State drop-down list. 

Note 

The next lowest state appears in the Demote to State drop-down list. 



The revision is demoted. 

144 > > > > > > > > > > > > > >

To demote a revision in the command line interface 

Use the si demote command, for example: 

si demote --sandbox=value --revision=value 

--state=value member 

where 

Locking Revisions 

Locking Revisions 


you want to demote, for example, c:/sandboxdemo/ 

project.pj 


demote, for example, 1.3 


member to, for example, Alpha 

member specifies the member you want to demote, for example, 

demoapp.ico 

VSky Software Manager confirms the revision is demoted. 

Revisions are normally locked at check-out time, but you can lock a 

revision without checking it out of the archive. Locking a revision 

ensures you alone are allowed to modify the revision. 

To lock a revision in the graphical user interface 

1 With a Member History window open, select a revision to lock. 

2 Choose History > Lock Revision, or click . 

A padlock symbol appears next to the revision number to 

inform you the revision is locked, and your user name and the 

date and time you locked out the revision appears in the 

Locked column. 

> > > > > > > > > > > > 145


To lock a revision in the command line interface 


si lock --sandbox=value --revision=value member 

where 

Unlocking Revisions 


you want to lock, for example, c:/sandboxdemo/project.pj 


lock, for example, 1.2 


demoapp.ico 


You can unlock a revision without checking it back into the archive. 

Unlocking a revision does not discard any changes you have made; 

however, resynchronizing or reverting the member would. 

146 > > > > > > > > > > > > > >

Unlocking Revisions 

If you attempt to unlock a revision that is locked by another user, a 

message warns you that you are about to break someone else’s 

lock. 

Note 

Although you may not be prohibited from breaking someone else’s 

lock, you should be cautious about doing so, because it can result in 

confusion and duplication of effort in shared working environments. 

For information on permissions, see Vertical Sky Software Manager 


To unlock a revision in the graphical user interface 

1 With a Member History window open, select a locked revision 

to unlock, one that has a padlock symbol. 

2 Choose History > Unlock Revision, or click . 

3 If the lock is not held by you, you will be asked to confirm 

breaking the lock. Confirm that you want to break the lock by 

clicking Yes. 

The padlock symbol and the name of the user who had the 

revision locked both disappear. 

To unlock a revision in the command line interface 

Use the si unlock command, for example: 

si unlock --sandbox=value --revision=value member 

where 


you want to unlock, for example, c:/sandboxdemo/ 

project.pj 

> > > > > > > > > > > > 147


Setting the Member Revision 


unlock, for example, 1.2 

Note 

You only need to specify the revision if the revision is not the member 

revision. 

member specifies the member you want to unlock, for example, 

demoapp.ico 

VSky Software Manager confirms the member is unlocked. 

Setting a revision as the member revision makes the revision the 

default revision in other sandboxes for users to work with. For 

example, if demoapp.c 1.1 is the member revision, setting 1.2 as 

the member revision makes it the default revision in all sandboxes. 

To set the member revision in the graphical user interface 


want to make the member revision. 

2 Choose History > Set Member Revision, or click . 

148 > > > > > > > > > > > > > >

Deleting Revisions 

The selected revision becomes the member revision, indicated 

by a member revision icon. 

To set the member revision in the command line interface 

Use the si updaterevision command, for example: 

si updaterevision --sandbox=value --revision=value 

member 

where 

Deleting Revisions 


you want to make the member revision, for example, c:/ 

sandboxdemo/project.pj 


make the member revision, for example, 1.2 

member specifies the member you want to make the member 

revision, for example, demoapp.ico 

VSky Software Manager confirms the revision is now the member 

revision. 

If you know you will never use a revision again, you can delete it. 

Note 

Only delete a revision when you are absolutely certain you will never 

need it again. Once you delete a revision, it cannot be retrieved. A 

revision cannot be deleted if it is locked or if it is the starting point 

(root) of a branch. You should never delete the head revision of an 

archive. 

> > > > > > > > > > > > 149


To delete a revision in the graphical user interface 


want to delete. 

Note 

You can only delete one revision at a time in the graphical user 

interface. 

2 Choose History > Delete Revision, or click . 

VSky Software Manager asks you to confirm the deletion. 

3 To delete the selected revision, click Yes. To keep the selected 

revision, click No. To cancel the operation, click Cancel. 

VSky Software Manager deletes the revision. 

To delete a revision in the command line interface 

Use the si deleterevision command, for example: 

si deleterevision --sandbox=value --range=value member 

where 


whose revision you want to delete, for example, 


--range=value specifies the revision range you want to delete. 

You can delete a single revision, for example --range=1.4, a 

range of revisions, for example, --range=1.2-1.4., or a nonsequential 

range of revisions, for example, --range=1.2, 1.4, 

1.6 

member specifies the member whose revision you want to delete, 


To confirm you want to delete the revision, enter Y. 

VSky Software Manager confirms the revision is deleted. 

150 > > > > > > > > > > > > > >

Comparing Revisions 

Comparing Revisions 

When you are working with an evolving body of source files, you 

can compare two revisions to see what changes you made from one 

revision to the next. 

With VSky Software Manager you can compare: 

any two text-based revisions in a history 

a text-based revision and its associated working file in a 

sandbox 

any two text files 

The commands discussed in this section use VSky Software 

Manager Visual Difference, which calculates the differences 

between working files or revisions and displays them side by side 

in their own window, along with a summary of the differences 

between them. Using Visual Difference, you can also interactively 

merge two members or revisions. 

Unlike most features of VSky Software Manager, Visual Difference 

is a standalone application that compares and merges members 

and revisions. 

To compare two revisions in the graphical user interface 

1 With a Member History window open, select two revisions to 

compare, or a revision and the working file. To select two 

revisions, select the first revision, then hold down or 

and click a second revision. 

2 Choose History > Differences, or click . 

The Visual Difference window appears. Both revisions and a 

summary of the differences between them are shown in the 

Visual Difference window. 

> > > > > > > > > > > > 151




Manager Visual Difference, 

see Visual Difference Online 

Help. 

To compare two revisions in the command line interface 

Use the si diff command, for example: 

si diff --sandbox=value -r value -r value member 

where 


whose revisions you want to compare, for example, 


-r value -r value specifies the revision numbers you want to 

compare, for example, -r 1.1 -r 1.2 

member specifies the member whose revisions you want to 

compare, for example, demoapp.c 

VSky Software Manager displays the differences between the two 

revisions, for example: 

Showing differences: ... 

c:/sandboxdemo/demoapp.c“c:/sandboxdemo/demoapp.c”: 

Differences between Revision 1.1 and Revision 1.2 

5c5 

> * (c) 1999 ABC Systems Inc. 

--- 

< * (c) 2000 ABC Systems Inc. 

9c9,11 

< * 

--- 

> * Second Draft: Geoff Miller 

> * Date: September 2000 

> 

< 

152 > > > > > > > > > > > > > >

Merging Revisions 

Merging Revisions 

You can use VSky Software Manager Visual Difference to merge 

differences between two revisions. The graphical user interface 

allows you to merge differences between two revisions, but the 

command line interface allows you to merge differences between 

three revisions. 

Note 

The member whose revisions you want to merge must be checked out. 

To merge two revisions in the graphical user interface 

1 Compare two revisions whose differences you want to merge, 

as described in “Comparing Revisions” on page 151. 

2 In Visual Difference, choose File > Merge, or click . 

A summary of the differences between the two revisions 

appear in the bottom pane of the Visual Difference window. 

3 Choose File > Save Merge As, or click . 

A dialog box appears informing you the merged file has not 

been modified. 

4 Confirm that you want to save the merged file by clicking Yes. 

The Save Merged File As dialog box appears. 

> > > > > > > > > > > > 153


5 Browse to the sandbox directory where you want to save the 

merged file. 

6 Enter the name of the merged file (the member name) in the 

File Name field. 

7 To save the merged file, click OK. 

8 Confirm that you want to save the merged file as the same 

name of the pre-existing file by clicking Yes. 

9 In VSky Software Manager, check in the member. 

The new revision is saved. 

To merge three revisions in the command line interface 

Use the si merge command, for example: 

si merge --sandbox=value -outputFile=value -r value 

value member 

where 


whose revisions you want to merge, for example, 


-outputFile=value specifies the target revision for merging, for 

example, -outputFile=1.3 

-r value value specifies the two revisions you want to merge 

with the target revision, for example, -r 1.1 1.2 

member specifies the member whose revisions you want to 

merge, for example, demoapp.c 

VSky Software Manager merges the differences between the three 

revisions and saves them to the target revision’s working file. 

To save the merged revision, check in the member. 

The new revision is saved. 

154 > > > > > > > > > > > > > >


Manager Integrations 

For instructions on 

installing integrations, see 

Vertical Sky Evolution 

Management Solution 

Installation. 

6 

Vertical Sky Software Manager integrations transparently blend 

VSky Software Manager’s functionality into the Integrated 

Development Environments (IDEs) you use, allowing you to work 

within your favorite development environment. VSky Software 

Manager integrations enable you to access the functionality 

available in the core product, right from within the host 

environment. 

This chapter explains how VSky Software Manager interacts with 

your IDEs and provides specific information about interacting with 

the following host environments: 

Microsoft Visual Basic 5.0 and 6.0 

Microsoft Visual C++ 5.0 and 6.0 

Microsoft Visual J++ 6.0 

Sybase PowerBuilder 7.0 

Borland JBuilder 3.0 

WebGain Visual Café 4.0 

IBM Visual Age for Java 3.5 

Rational Rose 2000 

Starbase CodeWright 6.5 

> > > > > > > > > > > > 155

Vertical Sky Software Manager Integrations 

Introducing Vertical Sky Software Manager 

Integrations 

VSky Software Manager integrations provide seamless access to 

many basic VSky Software Manager commands, such as creating a 

VSky Software Manager project or checking out a member. More 

advanced commands that cannot be performed with the 

integrations, such as setting the member revision, can be performed 

in VSky Software Manager, which can be invoked from the IDE 

you are working in. 

When you perform a source control command in an IDE, such as 

check in, the relevant VSky Software Manager dialog box or 

window appears. Some of the commands you can perform include: 

Create Project 

Take files that form a single body of work and group them in a 

related project. VSky Software Manager’s project-oriented 

approach to configuration management makes it easier to 

control the evolution of your files. 

Typically, when you create a project, you create the project, 

sandbox, and add members to the sandbox at the same time. 

Create Sandbox 

A reflection of the master project, a sandbox provides a way for 

you to work in a personal, protected workspace without 

interfering with the master project. This way, changes can be 

made and tested before being merged into the master project. 

If you want to work with a particular revision of the project to 

maintain past releases of a product, you can create a variant 

sandbox and work without interference on your own 

development path. 

If you want to use a project for building or testing, but not for 

further development, you can create a static sandbox based 

upon a specific revision of the master project. 

Add Members 

IDE files can be added to your project. 

156 > > > > > > > > > > > > > >

Using Integrations 

Using Integrations 

Check Out 

Extract the contents of a revision in an archive and copy it to a 

working file. Any revision can be checked out by its revision 

number or label. 

Check In 

Add a new revision of the file to its archive. 

To use VSky Software Manager with your IDE 

1 Add your IDE project to source control by creating a 

VSky Software Manager project and sandbox using the IDE. 

Note 

When you create a VSky Software Manager project and sandbox, the 

project can reside anywhere on the Vertical Sky Server, but the 

sandbox should reside in the same directory as the IDE project file 

(such as, .vep, .pbl, .dsp) or the IDE project file must be in the tree 

that is visible to the sandbox. 

2 Check out the IDE project file. 

3 Add IDE project files to the VSky Software Manager sandbox. 

VSky Software Manager prompts you to create an archive for 

each file. 

4 Check in the IDE project file. 

5 Checkpoint the project. 

6 Check out files as you need them. 

VSky Software Manager creates a working file from the 

selected revision in the archive. 

7 Make changes to the sandbox members from within the IDE. 

8 Check in modified files. 

This creates a new revision in the member’s archive. The new 

revision becomes the archive’s head revision unless you 

specifically check in the file to a revision other than the head 

> > > > > > > > > > > > 157


revision. When you check in a file to a revision other than the 

head revision, a new branch is created. 

Microsoft Visual Basic 5.0 and 6.0 

Integration 

This section describes how to access VSky Software Manager 

through Microsoft Visual Basic 5.0 and 6.0. 

Access version control functionality from within Visual Basic by 

choosing Tools > VSky Software Manager SCC Extension, then the 

command that corresponds to the VSky Software Manager function 

you want to perform. 

Command Function 

Get Latest Version Equivalent to the VSky Software Manager 

Resynchronize command. 

Gets the latest version of the selected file and 

puts it in your working directory. 

The Resynchronize dialog box appears. 

Check Out Equivalent to the VSky Software Manager 

Check Out command. 

Checks out a revision of the currently active 

file in the Visual Basic window, either locked 

(for editing) or unlocked (read-only). 


Check In Equivalent to the VSky Software Manager 

Check In command. 

Checks in the currently active file in the Visual 

Basic window. 


Undo Check Out Equivalent to the VSky Software Manager 

Revert command. 

Replaces the selected working file with the 

revision that was checked out, as it appeared 

prior to modification, and unlocks the file. 

The Revert dialog box appears. 

158 > > > > > > > > > > > > > >


Microsoft Visual Basic 5.0 and 6.0 Integration 

Show History Equivalent to the VSky Software Manager 

View Member History command. 

Displays the revision history of the currently 

active file in the Visual Basic window. 

The Member History window appears. 

Show Differences Equivalent to the VSky Software Manager 

Differences command. 

Compares the selected working file with the 


The Member Diff dialog box appears. 

VSky Software 

Manager SCC 

Extension Properties 

Add Project to 



Extension 

Add Files to 



Extension 

Create Project from 



Extension 

Run VSky Software 


Extension 

Equivalent to the VSky Software Manager 

Member Information command. 

Displays the selected file’s member 

information. 

The Member Information dialog box 

appears. 


New Project command. 

Brings the current Visual Basic project under 

source control. 



Add Members command. 

Adds the currently active file in the Visual 

Basic window to the sandbox. 



Create Sandbox command. 

Creates a sandbox from a project under 



Equivalent to launching the graphical user 

interface or the VSky Software Manager 

Open Sandbox command. 

Invokes the VSky Software Manager 

graphical user interface. If a Visual Basic 

project is currently loaded, and it is under 

version control, a Sandbox window appears. 

> > > > > > > > > > > > 159


Creating a 

Vertical Sky 

Software 


Project 


Options Equivalent to the VSky Software Manager 

Preferences command. 

Configures how VSky Software Manager will 

work, both within Visual Basic and by itself. 


Refresh File Status Equivalent to the VSky Software Manager 

Scan for Changes command. 

Updates the status and archive information of 

the selected file. 

The Visual Basic Project window is enhanced with version control 

features and indicators. For example, a check mark beside a file 

icon indicates the file is currently checked out. When a file is readonly, 

a small lock appears next to the file icon in the project 

window. 

Note 

You can also perform some member-specific commands on a selected 

file by right-clicking and choosing a command from the shortcut 

menu. 

To create a VSky Software Manager project in Visual Basic 

1 Open the Visual Basic project you want to put under version 

control. 

2 Choose Tools > VSky Software Manager SCC Extension > Add 

Project to VSky Software Manager SCC Extension. 


3 Create a project, as described in “Using Integrations” on 

page 157. 

After you create a project, the Create Sandbox Wizard appears. 

160 > > > > > > > > > > > > > >

Creating a 

Sandbox 

Adding 

Members to a 

Project 

Checking Out 

Members 

Microsoft Visual Basic 5.0 and 6.0 Integration 

4 Create a sandbox, as described in “Creating a Sandbox” on 

page 48. 

The Add Files to VSky Software Manager SCC Extension dialog 

box appears. 

5 Select the files you want to add to the sandbox. 

6 Click OK. 


7 If necessary, fill in or modify the Create Archive options, as 

described in“Adding Members to a Project” on page 62. 

To create a sandbox in Visual Basic 

1 Open the Visual Basic project you have under version control. 

2 Choose Tools > VSky Software Manager SCC Extension > Create 

a Project from VSky Software Manager SCC Extension. 



page 48. 

To add members to a project in Visual Basic 

1 Bring any files you want to add to the VSky Software Manager 

project into focus in the Visual Basic environment. 

2 Choose Tools > VSky Software Manager SCC Extension > Add 

Files to VSky Software Manager SCC Extension. 


3 Add members to the project, as described in “Adding Members 

to a Project” on page 62. 

To check out members in Visual Basic 

1 Bring any files you want to check out into focus in the Visual 

Basic environment. 

2 Choose Tools > VSky Software Manager SCC Extension > Check 

Out. 

A list of all files that can be checked out appears. 

You may choose additional files to check out from this list by 

selecting their check boxes. 

> > > > > > > > > > > > 161


Checking In 

Members 

3 Click OK. 


4 If necessary, fill in or modify the check out options, as 

described in “Checking Out a Member” on page 75. 

To check in members in Visual Basic 

1 Bring any files you want to check in into focus in the Visual 

Basic environment. 

2 Choose Tools > VSky Software Manager SCC Extension > Check 

In. 

A list of all files that can be checked in appears. 

You may choose additional files to check in from this list by 


3 Click OK. 


4 If necessary, fill in or modify the check in options, as described 

in “Checking In a Member” on page 80. 

Microsoft Visual C++ 5.0 and 6.0 Integration 


through Microsoft Visual C++ 5.0 and 6.0. 

Access version control functionality from within Visual C++ by 

choosing Project > Source Control, then the command that 

corresponds to the VSky Software Manager function you want to 

perform. 







162 > > > > > > > > > > > > > >






file in the Visual C++ window. 





C++ window. 








Add to Source 

Control 

Remove from Source 

Control 


New Project command or the VSky Software 

Manager Add Members command. 

If you select a .dsp or .dsw file in Visual C++, 

then choose Add to Source Control, the 

Visual C++ project is placed under source 

control. 

If you select a regular Visual C++ project file, 

then choose Add to Source Control, the file 

is added to source control. 

The Specify a Project dialog box appears or 

the Add Members Wizard appears. 


Drop Members command. 

Removes the currently active file from 

VSky Software Manager. Its member archive 

remains accessible from the VSky Software 

Manager Project window. 




active file in the Visual C++ window. 


> > > > > > > > > > > > 163










Extension Properties 




information. 


Refresh Status Equivalent to the VSky Software Manager 






Extension 


interface or the VSky Software Manager Open 

Sandbox command. 

Invokes the VSky Software Manager graphical 

user interface. If a Visual C++ project is 

currently loaded, and it is under version 

control, a Sandbox window appears. 

The Microsoft Visual C++ Project Workspace window is also 

enhanced with version control features and indicators. For 

example, a file’s icon turns gray once the file is placed under 

version control, and a red check mark beside a file’s icon indicates 

the file is currently checked out. 

164 > > > > > > > > > > > > > >

Creating a 




Project 

Note 




menu. 

To create a VSky Software Manager project in Visual C++ 

1 In the Workspace window, select the Visual C++ project file you 

want to put under version control, for example, 

vc_project.dsp. 

2 Choose Project > Source Control > Add to Source Control. 


3 Create a project, as described in “Creating a Project” on 

page 46. 



page 48. 


box appears. 


6 Click OK. 


> > > > > > > > > > > > 165


Creating a 

Sandbox 

Adding 

Members to a 

Project 

Checking Out 

Members 


described in “Adding Members to a Project” on page 62. 

To create a sandbox in Visual C++ 

1 Choose File > Open Workspace. 

The Open Workspace dialog box appears. 

2 Select the Visual C++ project you want to create a sandbox 

from. 

3 Click Source Control. 



page 48. 

Note 

To add the project’s members to the sandbox, select the Populate 

Sandbox option. 

To add members to a project in Visual C++ 


project into focus in the Visual C++ environment. 

2 Choose Tools > Source Control > Add to Source Control. 




To check out members in Visual C++ 

1 Bring one or more files that you want to check out into focus in 

the Visual C++ environment. 

2 Choose Project > Source Control > Check Out. 




166 > > > > > > > > > > > > > >

Checking In 

Members 

Microsoft Visual J++ 6.0 Integration 

3 Click OK. 




To check in members in Visual C++ 

1 Bring one or more files that you want to check in into focus in 

the Visual C++ environment. 

2 Choose Project > Source Control > Check In. 




3 Click OK. 






through Microsoft Visual J++ 6.0. 

Access version control functionality from within Visual J++ by 

choosing Project > Source Control, then the command that 


perform. 


Add to Source 

Control 


New Project command or the VSky Software 

Manager Add Members command. 

Brings the current Visual J++ project or 

selected files under source control. 

The Specify a Project dialog box appears or 

the Add Members Wizard appears. 

> > > > > > > > > > > > 167






file in the Visual J++ window. 





J++ window. 


Compare Versions Equivalent to the VSky Software Manager 





Properties Equivalent to the VSky Software Manager 



information. 


History Equivalent to the VSky Software Manager 



active file in the Visual J++ window. 




Extension 




user interface. If a Visual J++ project is 






user interface. If a Visual J++ project is 



168 > > > > > > > > > > > > > >

Creating a 




Project 



Change Connection Specifies source control connection 

properties. 

The Microsoft Visual J++ Project Explorer window is also enhanced 

with version control features and indicators. For example, a file’s 

icon turns gray once the file is placed under version control, and a 

red check mark beside a file’s icon indicates the file is currently 

checked out. 

Note 



menu. 

To create a VSky Software Manager project in Visual J++ 

1 In the Project Explorer window, select the Visual J++ project file 

you want to put under version control. 

2 Choose Project > Source Control > Add to Source Control. 



page 46. 



page 48. 


box appears. 


> > > > > > > > > > > > 169


Creating a 

Sandbox 

Adding 

Members to a 

Project 

Checking Out 

Members 

6 Click OK. 




To create a sandbox in Visual J++ 

1 Choose File > Open Project. 

The Open Workspace dialog box appears. 

2 Select the Visual J++ project you want to create a sandbox from. 

3 Click Source Control. 



page 48. 

Note 

To add the project’s members to the sandbox, select the Populate 

Sandbox option. 

To add members to a project in Visual J++ 


project into focus in the Visual J++ environment. 

2 Choose Tools > Source Control > Add to Source Control. 




To check out members in Visual J++ 


the Visual J++ environment. 

2 Choose Project > Source Control > Check Out. 




170 > > > > > > > > > > > > > >

Checking in 

Members 

Sybase PowerBuilder 7.0 Integration 

3 Click OK. 




To check in members in Visual J++ 


the Visual J++ environment. 

2 Choose Project > Source Control > Check In. 




3 Click OK. 






through Sybase PowerBuilder 7.0. 

You can access version control functionality through the Source 

menu. Select the command that corresponds to the VSky Software 

Manager function you want to perform. 


Register Equivalent to the VSky Software Manager 


Adds the selected file to your sandbox. 




Checks in the currently active file. 


> > > > > > > > > > > > 171






file. 






Synchronize Equivalent to the VSky Software Manager 



puts it in your working PowerBuilder library 

(.pbl) directory. 


Compare Differences Equivalent to the VSky Software Manager 





SCC Administration Equivalent to launching the graphical user 




graphical user interface. If a PowerBuilder 

project is currently loaded, and it is under 

version control, a Sandbox window appears. 

Note 

When you perform a VSky Software Manager command on multiple 

members, PowerBuilder asks you to confirm the command for each 

member. When asked to confirm the command for each member, 

clicking OK to All is equivalent to OK. 

172 > > > > > > > > > > > > > >

Creating a 




Project 

Creating a 

Sandbox 


To create a VSky Software Manager project in PowerBuilder 

Note 

You must create a folder for the VSky Software Manager project and 

sandbox before you create them. 

1 Open the PowerBuilder project you want to put under version 

control. 

2 Choose Window > Library Painter. 

The Choose SCC Provider dialog box appears. 

3 From the Vendors list, select VSky Software Manager SCC 

Extension. 

4 Click OK. 

5 Confirm you want to create a new configuration file by clicking 

Yes. 

6 Set up the SCC provider, as described in the PowerBuilder 

online help. 



page 46. 


Note 

The sandbox must be created “in-tree” of the PowerBuilder library 

(.pbl) file. For example, c:/pb/si/project.pj and c:/pb/ 

project.pbl. 


page 48. 

To create a sandbox in PowerBuilder 

Create a sandbox, as described in “Creating a Sandbox” on page 48. 

> > > > > > > > > > > > 173


Adding 

Members to a 

Project 

Checking Out 

Members 

Checking In 

Members 

To add files to a project in PowerBuilder 

1 Bring any files you want to add to a sandbox into focus in the 

PowerBuilder environment. 

2 Choose Source > Register. 


3 Add members to the sandbox, as described in “Adding 

Members to a Project” on page 62. 

To check out members in PowerBuilder 

1 Bring any files you want to check out into focus in the 


2 Choose Source > Check Out. 

The Check Out Libraries dialog box appears. 

3 Browse to the PowerBuilder library where you want to save the 

working copy of the file you are checking out. 

4 Click Open. 




To check in members in PowerBuilder 

1 Bring any files you want to check in into focus in the 


2 Choose Source > Check In. 




Borland JBuilder 3.0 Integration 


through Borland JBuilder 3.0. 

174 > > > > > > > > > > > > > >


Access version control functionality from within JBuilder by 

choosing VSky Software Manager, then the command that 


perform. 





file in the JBuilder window. 




Checks in the currently active file in the 

JBuilder window. 


Resynchronize Equivalent to the VSky Software Manager 





Revert Equivalent to the VSky Software Manager 






New Project and 

Sandbox 


Create Project command. 

Brings the current JBuilder project under 



New Sandbox Equivalent to the VSky Software Manager 

Create Sandbox command. 

Creates a sandbox from a master project. 

The Sandbox Wizard appears. 

> > > > > > > > > > > > 175



Add Member Equivalent to the VSky Software Manager 


Adds the currently active file in the JBuilder 

window to the sandbox. 


Drop Member Equivalent to the VSky Software Manager 






Differences Equivalent to the VSky Software Manager 





View Member History Equivalent to the VSky Software Manager 

Member History command. 

Displays the selected file’s member history. 


Member Information Equivalent to the VSky Software Manager 



information. 

The Member Information dialog box 

appears. 

Open Sandbox Equivalent to the VSky Software Manager 


Invokes the Sandbox window. 

Sandbox Information Equivalent to the VSky Software Manager 

Sandbox Information command. 

Displays the project’s sandbox information. 

The Sandbox Information dialog box 

appears. 

176 > > > > > > > > > > > > > >

Creating a 




Project 

Creating a 

Sandbox 


Launch 



Note 


You can rename a locked or checked out file under source control by 

selecting the file, then choosing File > Rename. Once you rename the 

file, you can add the file to source control; the old file is still under 

version control. If you rename the new file back to the name of the old 

file, you can check it in. 

To create a VSky Software Manager project in JBuilder 

1 Open the JBuilder project you want to put under version 

control. 

2 Choose VSky Software Manager > New Project and Sandbox. 



page 46. 



page 48. 

To create a sandbox in JBuilder 





graphical user interface. If a JBuilder project is 



Preferences Equivalent to the VSky Software Manager 



Preferences dialog box. 

1 Open the JBuilder project you want to put under version 

control. 

> > > > > > > > > > > > 177


Adding 

Members to a 

Project 

Checking Out 

Members 

Checking in 

Members 

2 Choose VSky Software Manager > New Sandbox. 



page 48. 

To add members to a project in JBuilder 

1 Bring one or more files that you want to add to a sandbox into 

focus in the JBuilder environment. 

2 Choose VSky Software Manager > Add Member. 


3 Add members to the sandbox, as described in “Adding 

Members to a Project” on page 62. 

To check out members in JBuilder 


the JBuilder environment. 

2 Choose VSky Software Manager > Check Out. 




To check in members in JBuilder 


the JBuilder environment. 

2 Choose VSky Software Manager > Check In. 




178 > > > > > > > > > > > > > >

WebGain VisualCafé 4.0 Integration 



through WebGain VisualCafé 4.0. 

Access version control functionality from within VisualCafé by 

choosing Tools > Version Control, then the command that 


perform. 

Note 

After you choose a VSky Software Manager command from the 

Version Control menu, a dialog box may appear with a list of files 

(members) to choose. Choose files by enabling their check boxes, then 

click OK. 








Checks out a revision of the currently selected 

file in the VisualCafé Project window, either 

locked (for editing) or unlocked (read-only). 




Checks in the currently selected file in the 

VisualCafé Project window. 







> > > > > > > > > > > > 179



Add to Version 

Control 



Adds the currently selected file in the 

VisualCafé Project window to the sandbox. 

The Create Archive appears. 




active file in the VisualCafé Project window. 







Vertical Sky SCC 

Integration 

Properties 




information. 






Options Equivalent to the VSky Software Manager 



work, both within VisualCafé and by itself. 

From the Version Control Options dialog 

box, click Advanced. 


Vertical Sky SCC 

Extension 





user interface. If a VisualCafé project is 



180 > > > > > > > > > > > > > >

Creating a 




Project 


The VisualCafé Project window is enhanced with version control 

features and indicators. For example, under the VCS column, 

Checked out appears if the file is currently checked out. 

Note 


file by right-clicking, choosing VCS, then selecting a command from 

the shortcut menu. 

To create a VSky Software Manager project in VisualCafé 

1 Open the VisualCafé project you want to put under version 

control. 

2 Choose Project > Options. 

The Project Options dialog box appears. 

3 Click Version Control. 

4 From the Version control providers list, choose SCC Provider: 

Vertical Sky Software Manager SCC Integration. 

5 Click OK. 

The Version Control Options dialog box appears. 

6 If necessary, fill in or modify the version control options. 

7 Click OK. 


> > > > > > > > > > > > 181


Creating a 

Sandbox 


page 46. 



page 48. 

After you create a sandbox, a list of files that will be added to 

the sandbox appears. 


Note 

Make sure the VisualCafé project file (.vep) is selected. 

11 Click OK. 




To create a sandbox in VisualCafé 

1 In VSky Software Manager, create a sandbox, as described in 

“Creating a Sandbox” on page 48. 

After you create a sandbox, a list of files that you can add to the 

sandbox appears. 


Note 

Make sure the VisualCafé project file (.vep) is selected. 

3 Click OK. 




182 > > > > > > > > > > > > > >

Adding 

Members to a 

Project 

Checking Out 

Members 

To add members to a project in VisualCafé 

Caution 


Adding files to an SCC enabled project in VisualCafé prompts you to 

resynchronize the project. Choosing to resynchronize the project will 

undo any changes to unlocked files. To avoid this, choose Tools > 

Source Control > Options and clear the Prompt to get files when opening 

the project check box. You can also choose Tools > Source Control > 

Options, click Advanced > Commands, then disable the Resynchronize 

check box. 


project into focus in the VisualCafé environment. 

2 Choose Tools > Version Control > Add to Version Control. 

A list of all files you can add to the project appears. 



3 Click OK. 




To check out members in VisualCafé 

1 Bring any files you want to check out into focus in the 

VisualCafé environment. 

2 Choose Tools > Version Control > Check Out. 




3 Click OK. 




> > > > > > > > > > > > 183


Checking In 

Members 

To check in members in VisualCafé 

1 Bring any files you want to check in into focus in the 

VisualCafé environment. 

2 Choose Tools > Version Control > Check In. 




3 Click OK. 




IBM Visual Age for Java 3.5 Integration 


through IBM Visual Age for Java 3.5. 

Note 

For complete information about Visual Age for Java’s external version 

control capabilities, refer to the IBM Visual Age for Java 3.5 

documentation. 

Access version control functionality from within Visual Age for 

Java by choosing Selected > Tools > External Version Control from 

the Workspace window, then the command that corresponds to the 

VSky Software Manager function you want to perform. 



Control 


New Project command. 

Brings the current Visual Age for Java project 

under source control. 


184 > > > > > > > > > > > > > >



Refresh Project Equivalent to the VSky Software Manager 


Gets the latest version of files and puts them 

in your working directory. 

Remove from 

Version Control 

Drops the project from Visual Age for Java 

version control. 

After the project has been removed from 

Visual Age for Java version control, drop the 

project/sandbox in VSky Software Manager. 



Checks in the currently selected file in Visual 

Age for Java. 





file in Visual Age for Java, either locked (for 

editing) or unlocked (read-only). 







Add Equivalent to the VSky Software Manager 


Adds the currently selected file in Visual Age 

for Java to the sandbox. 


Delete Equivalent to the VSky Software Manager 






> > > > > > > > > > > > 185






work, both within Visual Age for Java and by 

itself. 

From the Properties dialog box for the project, 

click Microsoft SCCI, then Advanced. 


Open Version 

Control 





user interface. If a Visual Age for Java project 

is currently loaded, and it is under version 


The Visual Age for Java Projects panel is enhanced with version 

control features and indicators. For example, a green arrow appears 

beside the project to indicate it is under version control. 

Note 


file by right-clicking, choosing Tools > External Version Control, then 

selecting a command from the shortcut menu. 

186 > > > > > > > > > > > > > >

Creating a 




Project 

Creating a 

Sandbox 


To create a VSky Software Manager project in Visual Age for 

Java 

1 Start the Visual Age for Java Remote Access Server, as 

described in the Visual Age for Java documentation. 

2 From the Projects tab, select the project you want to put under 

version control and choose Selected > Tools > External Version 

Control > Add to Version Control. 

The Add to Version Control dialog box appears. 

3 Select Microsoft SCCI. 

4 Click OK. 

The Select SCM System dialog box appears. 

5 Choose Vertical Sky Software Manager SCC Integration. 

6 Click OK. 



page 46. 



page 48. 

The Select local directory dialog box appears. 

9 Select the local directory where the Visual Age for Java project 

is saved. 

10 Click OK. 

The Add to Version Control SmartGuide appears. 

11 To add the members of the Visual Age for Java project to 

version control, complete the SmartGuide, as described in the 

Visual Age for Java documentation. 




To create a sandbox in Visual Age for Java 

In VSky Software Manager, create a sandbox, as described in 


> > > > > > > > > > > > 187


Adding 

Members to a 

Project 

Checking Out 

Members 

Checking In 

Members 

To add members to a project in Visual Age for Java 


project into focus in the Visual Age for Java environment. 

2 Choose Selected > Tools > External Version Control > Add. 

A list of all files that will be added to the project appears. 

3 Click OK. 




A Summary dialog box appears. 

5 Click OK. 

To check out members in Visual Age for Java 

1 Bring any files you want to check out into focus in the Visual 

Age for Java environment. 

2 Choose Selected > Tools > External Version Control > Check Out. 

A list of all files that will be checked out appears. 

3 Click OK. 





5 Click OK. 

To check in members in Visual Age for Java 

1 Bring any files you want to check in into focus in the Visual 

Age for Java environment. 

2 Choose Selected > Tools > External Version Control > Check In. 

A list of all files that will be checked in appears. 

3 Click OK. 


188 > > > > > > > > > > > > > >

Rational Rose 2000 Integration 




5 Click OK. 



through Rational Rose 2000 Enterprise Edition - 7.0.9420.17. 

Access version control functionality from within Rational Rose by 



perform. 



Control 

Remove from 


Start Version Control 

Explorer 


New Project and Add Members commands. 

Brings the current Rational Rose project or file 

under version control. 

For Rational Rose project files, the Specify a 

Project dialog box appears. For Rational 

Rose project members, the Create Archive 

dialog box appears. 

Drops the Rational Rose project or member 

from VSky Software Manager version control. 

A Confirm Drop dialog box appears. 





user interface. If a Rational Rose project is 



> > > > > > > > > > > > 189





Checks in the currently selected file in 

Rational Rose. 





file in Rational Rose, either locked (for editing) 

or unlocked (read-only). 







Get Latest Equivalent to the VSky Software Manager 


Gets the latest version of a file and puts it in 

your working directory. 

File Properties Equivalent to the VSky Software Manager 



information. 


File History Equivalent to the VSky Software Manager 


Displays the selected file’s member history. 



Options 

Displays Rational Rose version control 

options. 

The Rational Rose Browser panel is enhanced with version control 

features and indicators. For example, a red check-mark appears 

beside the project to indicate it is under version control. 

190 > > > > > > > > > > > > > >

Creating a 




Project 

Note 



file by right-clicking, then selecting a command from the shortcut 

menu. 

To create a VSky Software Manager project in Rational Rose 

1 Select the Rational Rose project you want to put under version 

control and choose Tools > Version Control > Add to Version 

Control. 

A dialog box appears displaying the project file that will be 

placed under version control. 

2 Click OK. 



page 46. 



page 48. 







> > > > > > > > > > > > 191


Creating a 

Sandbox 

Adding 

Members to a 

Project 

Checking Out 

Members 

Checking In 

Members 

To create a sandbox in Rational Rose 



To add members to a project in Rational Rose 


project into focus in the Rational Rose environment. 

2 Choose Tools > Version Control > Add to Version Control. 

A list of all files that will be added to the project appears. 

3 Click OK. 




5 Click OK. 

To check out members in Rational Rose 

1 Bring any files you want to check out into focus in the Rational 

Rose environment. 

2 Choose Tools > Version Control > Check Out. 

A list of all files that will be checked out appears. 

3 Click OK. 




To check in members in Rational Rose 

1 Bring any files you want to check in into focus in the Rational 

Rose environment. 

2 Choose Tools > Version Control > Check In. 

A list of all files that will be checked in appears. 

3 Click OK. 


192 > > > > > > > > > > > > > >

Starbase CodeWright 6.5 Integration 





through Starbase CodeWright 6.5. 

Access version control functionality from within CodeWright by 



perform. 


Maintenance Displays CodeWright source control options. 

The Maintenance dialog box appears. 

Put Equivalent to the VSky Software Manager 


Checks in the currently active file in the 

CodeWright window. 


Get Equivalent to the VSky Software Manager 




Get With Lock Equivalent to the VSky Software Manager 



file in the CodeWright window, locked for 

editing. 


Unlock Equivalent to the VSky Software Manager 





> > > > > > > > > > > > 193



Add Equivalent to the VSky Software Manager 


Adds the currently active file in the 

CodeWright window to the sandbox. 


Remove Drops the member from VSky Software 

Manager version control. 

A Confirm Drop dialog box appears. 

History Equivalent to the VSky Software Manager 



active file in the CodeWright window. 


Difference Equivalent to the VSky Software Manager 




The two files are displayed in Visual 

Difference. 




information. 


Manager Equivalent to launching the graphical user 




user interface. If a CodeWright project is 

currently loaded, and is under version control, 

a Sandbox window appears. 

Setup Equivalent to the VSky Software Manager 



work, both within CodeWright and by itself. 

From the Version Control Setup dialog box, 

click Advanced. 


194 > > > > > > > > > > > > > >

Creating a 




Project 

Creating a 

Sandbox 

Note 




menu. 

To create a VSky Software Manager project in CodeWright 

1 In CodeWright, create a workspace. 

2 Create a CodeWright project that you want to put under 

version control. 

3 Choose Tools > Version Control > Setup. 

The Version Control Setup dialog box appears. 

4 If not already selected, under SCC Service Provider, select 

Vertical Sky Software Manager SCC Integration. 

5 Click Open Project. 

The Select a Source Code Control Project dialog box appears. 

6 Click Create a new project. 

7 Click OK. 

The Select One or More Projects dialog box appears. 


page 46. 



page 48. 

10 Close the Version Control Setup dialog box by clicking OK. 

To create a sandbox in CodeWright 



> > > > > > > > > > > > 195


Adding 

Members to a 

Project 

Checking Out 

Members 

Checking In 

Members 

To add members to a project in CodeWright 

1 In the CodeWright environment, select the files you want to 

add to the VSky Software Manager project. 

2 Choose Tools > Version Control > Add. 




4 Click OK. 

To check out members in CodeWright 


check out. 

2 Choose Tools > Version Control > Get With Lock. 




To check in members in CodeWright 


check in. 

2 Choose Tools > Version Control > Put. 

The Revision Comment dialog box appears. 

3 Click OK. 




196 > > > > > > > > > > > > > >

Integrated Version 

Control 

7 

As part of the integration with Vertical Sky Collaboration 

Manager, you can add members to an issue’s change package 

(issues track changes in the software development cycle). 

A change package allows you to specify groups of members that are 

affected by an issue type. For example, a solution’s change package 

might contain files that need to be changed in order to satisfy a 

problem. 

Administrators define what issue types can use change packages 

and configure Vertical Sky Software Manager to allow change 

packages. To add change package to an issue, VSky Software 

Manager user must be assigned to this issue. 


adding members to an issue’s change package 

viewing change package information in VSky Software 


viewing change packages in VSky Collaboration Manager 

> > > > > > > > > > > > 197

Integrated Version Control 

Adding Members to an Issue’s Change 

Package 

Once your administrator configures VSky Software Manager to 

allow change packages, you can add members to an issue’s change 

package. 

You can associate members with an issue’s change package upon a 

check out or a check in operation, locking a member, or when 

adding members to a project. 

To add a member to an issue’s change package upon check 

out using the graphical user interface 


check out. 

2 Choose Member > Check Out, or click . 


198 > > > > > > > > > > > > > >

For available check out 

options, see “Checking 

Out a Member” on 

page 75. 

Note 

Adding Members to an Issue’s Change Package 

The Change Package list appears only if lock tracking is enabled. It is 

disabled unless you are locking the member. Contact your 

administrator for more information on lock tracking. 

3 From the Change Package list, select a change package to 

associate the member with, for example, 7: Floating tool bar 

does not anchor to application. 

4 To check out the member, click OK. To check out all remaining 

members, click OK to All. To cancel the check out without 

checking out the member, click Cancel. 

The member is checked out and added to the issue’s change 

package. The issue’s ID appears in the member’s C.P. ID 

column after the check in. 

To add a member to an issue’s change package upon check 

out using the command line interface 

Use the si co command, for example: 

si co --sandbox=value --revision=value 

--changePackageId=value member 

where 

--sandbox=value specifies the sandbox containing the 

member you want to check out, for example, c:/sandboxdemo/ 

project.pj 

--revision=value specifies the revision you want to check 

out, for example, 1.1 

> > > > > > > > > > > > 199


--changePackageId=value specifies the ID of the change 

package to associate the member with, for example, 7 

member specifies the member you want to check out, for 


VSky Software Manager confirms the member is checked out. 

To verify the member is added to the issue’s change package, use 

the si memberinfo command. 

To add a member to an issue’s change package upon check in 

using the graphical user interface 


check in. 

2 Choose Member > Check In, or click . 


Note 

If you are using PointBase database, limit the revision description to a 

maximum of 500 words. If you are using Oracle database, limit your 

revision description to a maximum of 4,000 characters. 

200 > > > > > > > > > > > > > >

For available check in 

options, see “Checking In a 

Member” on page 80. 





4 To check in the revision or member, click OK. To check in all 

remaining revisions or members, click OK to All. To cancel the 

check in without checking in any revisions or members, click 

Cancel. 

The member is checked in and added to the issue’s change 


column. 

To add a member to an issue’s change package upon check in 

using the command line interface 

While creating an archive, use the si ci command, for example: 

si ci --sandbox=value --revision=value 


where 


member you want to check in, for example, c:/sandboxdemo/ 

project.pj 

--revision=value specifies the member revision number you 

want to check in, for example, 1.1. 



> > > > > > > > > > > > 201


member specifies the member you want to check in, for 


Note 

If you are using PointBase database, limit the revision description to a 

maximum of 500 words. If you are using Oracle database, limit your 

revision description to a maximum of 4,000 characters. 

VSky Software Manager confirms the member is checked in. 



To add a member to an issue’s change package upon locking 

the member using the graphical user interface 


lock. 

2 Choose Member > Lock, or click . 

The Lock Member Revision dialog box appears. 

Note 

:member appears in the Revision field to indicate the member revision 

will be locked. 




202 > > > > > > > > > > > > > >

For available locking 

options, see “Locking a 

Member” on page 89. 


4 To lock the revision and add it to the issue’s change package, 

click OK (for multiple members, click OK to All). To cancel the 


The member is locked and added to the issue’s change 


column after the check in. 

To add a member to an issue’s change package upon locking 

the member using the the command line interface 


si lock --sandbox=value --revision=value 


where 


member you want to lock, for example, c:/sandboxdemo/ 

project.pj 


lock, for example, 1.2 




demoapp.ico 




> > > > > > > > > > > > 203


For more information 

about adding member to a 

project, see “Adding 

Members to a Project” on 

page 62. 

To add a member to an issue’s change package upon adding 

the member to a project in the graphical user interface 

1 With a Sandbox window open, select the sandbox. 

2 Choose Sandbox > Add Members, or click . 


3 Complete the Add Members Wizard options. 


Note 

If you are re-adding a dropped archive, the Create Archive dialog box 

does not appear. 




5 If necessary, fill in or modify the Create Archive options. 

204 > > > > > > > > > > > > > >


6 To accept the information, click OK. To accept the information 

for all members, click OK to All. To cancel the operation, click 

Cancel. 

The member is added to the sandbox and the issue’s change 


column. 

To add a member to an issue’s change package upon adding 

the member to a project in the command line interface 

Use the si add command, for example: 

si add --sandbox=value --changePackageId=value member 

where 


you are adding members to, for example, 


--changePackageId=value specifies the ID of the issue you 

want to associate with the project member, for example, 7 

member specifies the member you want to add to the sandbox, 

for example, demoapp.h 

VSky Software Manager confirms the member is added to the 

sandbox. 

To verify the issue is associated with the member, use the si 

memberinfo command. 

> > > > > > > > > > > > 205




Once you associate project members with an issue’s change 

package, you can view a member or revision’s change package 

information in VSky Software Manager. 

To view a member’s change package information using the 



whose information you want to view. 

2 Choose Member > Member Information, or click . 


3 Click the Change Package tab. 

206 > > > > > > > > > > > > > >

Viewing Change Packages in Vertical Sky Software Manager 

The Change Package panel appears. 

The issue’s ID and summary are displayed. If the member is 

not associated with a change package, No Change Package 

Information Available appears in the Change Package 

panel. 

4 When you are finished viewing the member information, click 

OK or Cancel. 

To view a member’s change package information using the 


Use the si memberinfo command, for example: 

si memberinfo --sandbox=value member 

where 


whose information you want to view, for example, 


member specifies the member whose information you want to 

view, for example, demoapp.c 

VSky Software Manager displays the member’s information, for 

example: 



Member Revision: 1.2 

> > > > > > > > > > > > 207


Created By: vskyler on Sep 24, 2000 - 3:49 PM 

State: Exp 



Labels: none 

Change Package: 

ID: 7 

Summary: Floating tool bar does not anchor to 

application 

Attributes: none 

To view a revision’s change package information using the 


1 With a Member History window open, select the revision 

whose information you want to view. 

2 Choose History > Revision Information, or click . 

The Revision Information dialog box appears. 


208 > > > > > > > > > > > > > >

Viewing Change Packages in Vertical Sky Software Manager 


The issue’s ID and summary are displayed. If the member is 

not associated with a change package, No Change Package 

Information Available appears in the Change Package 

panel. 

4 When you are finished viewing the revision information, click 

OK or Cancel. 

To view a revision’s change package information using the 


Use the si revisioninfo command, for example: 

si revisioninfo --sandbox=value --revision=value 

member 

where 


containing the member whose revision information you want 

to view, for example, c:/sandboxdemo/project.pj 

--revision=value specifies the revision number whose 

revision information you want to view, for example, 1.2 

member specifies the member whose revision information you 

want to view, for example, demoapp.c 

> > > > > > > > > > > > 209


VSky Software Manager displays the member’s revision 




Revision: 1.2 

Created By: g 

on Apr 24, 2000 - 3:49 AM 

State: Exp 



Labels: none 

Change Package: 

ID: 7 

Summary: Floating tool bar does not anchor to 

application 


Collaboration Manager 


Vertical Sky Collaboration 

Manager User Guide. 

Once you associate project members with an issue’s change 

package, you can view the issue’s change package information in 

the VSky Collaboration Manager graphical user interface and Web 

interface. 

To view an issue’s change package information in the 


1 Select the issue. 

210 > > > > > > > > > > > > > >


Vertical Sky Collaboration 

Manager User Guide. 

Viewing Change Packages in Vertical Sky Collaboration Manager 

The issue opens in the Issue Details. 



The Change Package panel displays the project the member belongs 

to, member name, revision number, author name, lock status, 

revision date, revision description, and the archive path and name. 

To view an issue’s change package information in the Web 

interface 

1 Select the issue. 

> > > > > > > > > > > > 211


The issue opens in the Issue Details page. 



The Change Package panel displays the project the member belongs 

to, member name, revision number, author name, lock status, 

revision date, revision description, and the archive path and name. 

212 > > > > > > > > > > > > > >

A P P E N D I X 

Glossary 

archive A file containing the history of a member (a record of all the 

changes made to it since it was put under revision control). From 

the information contained in the history, VSky Software Manager 

can reconstruct any previous version of the member. 

The archive is sometimes referred to as the RCS file, for historical 

reasons. 

archive description Text that describes the purpose of an archive. You are asked to enter 

an archive description when an archive is created. 

archive information In addition to an archive’s contents, VSky Software Manager also 

maintains detailed information about each archive, including: 

a list of revision labels used in the archive 

a list of users who have locks on revisions in the archive 

the starting point of the default branch revision 

the type of data stored in the archive (that is, text or binary) 

whether the archive is compressed 

whether a strict-locking policy is applied to the archive 

a description of the archive 

author name The name you associate with revisions upon check in. By default, 

your author name is your user name. 

binary file A file containing unprintable characters, or lines too long to be 

handled by text editors. 

branch A revision path that diverges from the main line of development (or 

trunk) in a member or project’s history. A branch is typically 

created by checking in a file to a revision other than the head 

revision. The most recent revision of a branch is called the tip 

revision. 

> > > > > > > > > > > > 213

Glossary 

build sandbox A sandbox based upon a specific revision of a project, used for 

building or testing the project, not for further development. 

change package A change package allows you to specify groups of revisions that are 

affected by an issue (issues track changes in the software 

development cycle), for example, a solution’s change package 

might contain files that need to be changed in order to satisfy a 

problem. 

check in Creates a new revision of a member and adds it to the member 

history. When a member is checked in to a revision other than the 

head revision or a branch tip revision, a new branch is created. 

check out Extracts the contents of a revision in a member history and copies it 

to a working file. You can check out any revision by specifying 

either its revision number or label. 

checkpointing Creates a new revision of a project and adds it to the project history. 

When you checkpoint a project, you save all the information 

needed to recreate the project completely at any time in the future. 

The saved information includes the project structure and the list of 

members with their revision numbers. 

Compare window A Visual Difference window in which two text-based files or 

revisions are displayed for comparison, along with a summary of 

the differences between them. 

data types The data preserved in VSky Software Manager histories can be one 

of two types: 

Binary is a file containing unprintable characters, or lines too 

long to be handled by text editors. 

Text is the file format expected by MS-DOS and Windows text 

file editors. When a file of type “Text” is checked out, 

VSky Software Manager adds a carriage return at the end of 

each line. 

default branch The branch VSky Software Manager tries to check in files to. If 

unspecified, files are checked in to the trunk. 

default editor The editor used to display a working file or revision. 

214 > > > > > > > > > > > > > >

deltas The differences (stored in a history) between one revision and its 

immediate ancestor. A history contains all the deltas needed to 

reconstruct any revision. 

demoting Changing a revision’s promotion state setting from a higher to a 

lower level. 

drop (a project or 

sandbox) 

To unregister a project or sandbox. Once a project or sandbox is 

dropped, it cannot be accessed with VSky Software Manager. 

freezing (a member) To place a member in a state that prevents changes being made to 

the member information that resides in the project file. For 

example, you cannot update the member revision or change the 

attributes of a frozen member. The opposite of thaw. 

head revision The tip revision on the default branch, or the trunk, if no default 

branch is defined. 

importing (a project or 

sandbox) 

Integrated 

Development 

Environment (IDE) 

To register a project or sandbox created with an older version of 

VSky Software Manager. Once a project or sandbox is imported, 

VSky Software Manager commands can be performed upon the 

project or sandbox. 

A supported development application, such as Sybase 

PowerBuilder, that allows you to access VSky Software Manager 

functionality by installing the appropriate extension. 

keyword A special variable (for example, $Date$, $Author$, $State$) used 

to represent textual information in a working file. Keywords can be 

expanded (that is, replaced with their literal values) when a 

revision is checked out. 

keyword expansion The process of automatically adding or updating information to a 

keyword reference when a revision is checked out or viewed. 

label See revision label. 

locking Preventing more than one user from simultaneously making 

changes to the same revision. When a revision is locked, no one 

other than the locker can check in changes to that revision. 

locker The person who has a revision locked. 

> > > > > > > > > > > > 215

Glossary 


window 

In the graphical user interface, a window that displays the revision 

history of a project member. 

metadata Information about a revision or archive, as opposed to the 

information that is part of the object. For example, a revision’s 

Revision Description is metadata since it is information about the 

revision, while the contents of the revision is part of the revision 

itself and, hence, is not metadata. 

project A group of files that, taken together, forms a single body of work. 

Projects are presented in Project Windows, which list the members 

of the project and provide access to them. 

project member Any file that is included in a project. 

Project members are displayed in a Project window. 

Project History 

window 

In the graphical user interface, a window that displays the revision 

history of a project. 

Project window In the graphical user interface, a window that displays the 

members and subprojects of a project. 

promoting Managing data as it moves through a structured development 

cycle. Any project (whether it is software development, document 

production, or any other type of data management) goes through 

recognizable phases: from inception, through development, testing, 

quality assurance, and completion. 

Using promotion, you can define the phases (or states) of your 

development cycle and track and manage the progress of each file 

as it moves through the process. 

Registered Projects 

window 

Registered Sandboxes 

window 

In the graphical user interface, a window that displays registered 

projects. 

In the graphical user interface, a window that displays registered 

sandboxes. 

resynchronizing Updating a working file to the current member revision (in a 

Sandbox window). 

reverting Discard any changes made to a member’s working file since it was 

checked out and unlocks it. 

216 > > > > > > > > > > > > > >

evision A version of a file. Revisions are contained in a history. 

A new revision is produced in the history each time a working file 

is checked in. 

revision description Free-form comments describing a revision. The revision description 

can contain anything from a detailed description of changes, to 

instructions for the next person who will work on the file. 

The revision description is attached to a new revision at check in 

time. 

revision label A textual name that describes and refers to revisions in a history. 

When a file is checked in, you are given the option of assigning it a 

revision label. Revisions in a history can be displayed and selected 

either by revision number or revision label. 

revision number A unique number used to identify a revision in a history. Revisions 

on the trunk are numbered as two-part decimals (such as, 1.1, 1.2, 

1.3, 1.4, …). Revisions on a branch are numbered by adding twopart 

decimals to the number of the revision they branch from. 

For example, if a branch is started from revision 1.3, its revisions 

would be numbered 

1.3.1.3 

1.3.1.2 

1.3.1.1 

and so on. 

sandbox A mirror image of a VSky Software Manager project. Although it 

looks and acts like the project it mirrors, it is actually a collection of 

pointers to its real-life counterparts in the master project. 

Sandboxes provide a way for developers to work on projects in a 

personal, protected workspace, without immediately impacting the 

condition of the project or disrupting the work patterns of other 

project developers. 

With sandboxes, each user creates a personal workspace for a 

project where changes can be made and tested before being merged 

back into the master project. 

Sandbox window In the graphical user interface, a window that displays the 

members and subsandboxes of a single sandbox. 

> > > > > > > > > > > > 217

Glossary 

state A textual description, defined by the administrator, used to classify 

the condition of a revision in a history. For example, a document 

could initially have a state of “Draft”. As work progresses it might 

be changed to “Review” and eventually “Complete”. If no state is 

assigned to a revision, a default value of “Exp” (for Experimental) 

is used. 

strict locking A policy that enforces users to have a lock on a revision to perform 

a check in operation. 

subproject A project within a project. Subprojects are typically smaller 

components of a project, such as documentation or graphic files. 

subsandbox A sandbox within a sandbox. Subsandboxes are typically smaller 

components of a sandbox, such as documentation or graphic files. 

thawing Remove the frozen state of a member so that changes can again be 

made to the member information. The opposite of freezing. 

tip revision The most recent revision on a branch in a history. 

updating a member 

revision 

trunk The primary line of a file’s change history in a history. The first 

member of the trunk is always the original file checked into the 

archive. 

Ensures the most recent revision of a member is added to the list of 

members in a project/sandbox when checking in a member. 

user name The name VSky Software Manager knows you by. By default, user 

name is used as the author during check in. 

variant sandbox A sandbox that is created from a previous project checkpoint rather 

than the current contents of a project. When you want to branch to 

a variant development path, you create a variant sandbox . It is 

similar to creating a branch archive. 

Visual Difference 

window 

The main window of VSky Software Manager Visual Difference 

used to display the differences between text-based files or 

revisions. 

working file A file that contains a working copy of a checked out revision. Users 

edit and change the working file, not the revision itself. Changes to 

the working file are added to the history (as a new revision) when 

the working file is checked in. 

218 > > > > > > > > > > > > > >

Index 

A 

adding labels 

to members 109 

to projects 112 

to revisions 139 

adding members 

to a project 62 

using Borland JBuilder 178 

using IBM Visual Age for Java 188 

using Microsoft Visual Basic 161 

using Microsoft Visual C++ 166 

using Microsoft Visual J++ 170 

using Rational Rose 192 

using Starbase CodeWright 196 

using Sybase PowerBuilder 174 

using WebGain VisualCafé 183 

to change package 198, 203, 205 

administrator 

described 1 

all members 

filter 20 

any member deltas 

filter 21 

application window 

described 9 

archive 

described 213 

archive description 

described 213 

archive information 

described 213 

editing 133 

viewing 133 

assigning 

revision descriptions 82 

revision numbers 81 

Author keyword 94 

author name 

described 213 

B 

before starting 

VSky Software Manager 8 

binary files 

described 213 

Borland JBuilder integration 174 

adding members to a project 178 

checking in members 178 

checking out members 178 

creating a sandbox 177 

creating a VSky Software Manager 

project 177 

branch 

described 213 

starting during check in 81 

build sandbox 

creating 48 

described 74, 214 

buttons 

toolbar 10 

C 

change package 

described 214 

change packages 

adding members to 198, 203, 205 

upon check in 200 

upon check out 198 

upon locking a member 202 

viewing 206, 210 

changes 

scanning a sandbox for 79 

check in 

described 214 

check out 

described 214 

checking in 

adding members to change package 200 

> > > > > > > > > > > > 

219

Index 

members 80 



using Microsoft Visual Basic 162, 196 






checking out 


members 75 










checkpointing 

a project 121 

described 214 


described 21 

using the graphical user interface 22 

command prompts 

described 22 

commands 

ident 93 

syntax 22 

viewing 21 

Compare window 

described 214 

comparing 

revisions 151 

working file to member revision 85 

configuring 


connection preferences 28 

creating 

a build sandbox 48 

a development path 72 

a project 46 

a report 128 

a sandbox 48 

a subproject 69 

a variant sanbox 48 

D 

data types 

described 214 

Date keyword 94 

default branch 

described 214 

default editor 

described 214 

deleting 

member labels 110 

project labels 113 

revisions 149 

deltas 

described 215 

demoting 

a project 117 

described 215 

revisions 144 

development path 

creating 72 

described 71 

removing 73 

development path information 

editing 97 

viewing 97 

discarding 

changes to a working file 87 

dropping 

a project 55 

described 215 

a sandbox 57 

described 215 

E 

editing 

archive information 133 

development path information 97 

member attributes 104 

member information 103 


220 > > > > > > > > > > > > > >

members 78 

project attributes 97 

project information 96 

revision information 135 

revision labels 137 

F 

filter list 

described 13 

filters 

all members 20 

any member deltas 21 

frozen members 21 

locked members 21 

members locked by me 21 

members with label 21 

members with state 21 

modified working files 21 

out of sync members 21 

using 20 

freezing 

members 119 

described 215 

frozen members 

filter 21 

G 

general 

preferences 26 

toolbar buttons 10 

glossary of terms 213 


described 9 

using in the command line interface 22 

graphs 

Reporter 125 

H 

head revision 

described 215 

Header keyword 94 

I 

IBM Visual Age for Java integration 184 





project 187 

Id keyword 94 

ident command 93 

importing 

a project 47 

a sandbox 54 

described 215 

integrated development environment 

described 215 

integrations 

Borland JBuilder 174 

described 156 

IBM Visual Age for Java 184 

Microsoft Visual Basic 158 

Microsoft Visual C++ 162 

Microsoft Visual J++ 167 

Rational Rose 189 

Starbase CodeWright 193 

Sybase PowerBuilder 171 

using 157 

VSky Collaboration Manager 197 

WebGain VisualCafé 179 

K 

keyword 

Author 94 

Date 94 

described 215 

Header 94 

Id 94 

Locker 94 

Log 94 

Name 94 

ProjectName 94 

ProjectRevision 94 

RCSfile 94 

Revision 94 

Source 94 

State 94 

Index 

> > > > > > > > > > > > 221

Index 

keyword expansion 

described 215 

keywords 

locating 93 

table of 94 

using 91 

L 

label 

deleting from revisions 140 

described 215 

labeling 

members 109 

projects 112 

revisions 139 

launching 


locating keywords 93 

locked members 

filter 21 

locker 

described 215 

Locker keyword 94 

locking 


described 215 

members 89 

revisions 145 

Log keyword 94 

logging in 24 

logging out 41 

M 

member 

reverting 87 

member attributes 

editing 104 

viewing 104 

member history 

viewing 132 

Member History window 



member information 

editing 103 

saving 106 

viewing 103 

member labels 

editing 105 

viewing 105 

member name arguments 

described 22 

member revision 

setting 148 

updating 107 

members 

adding labels to 109 

adding to a project 62 

adding to change package 198 

checking in 80 

checking out 75 

deleting labels 110 

demoting 115 

editing 78 

freezing 119 

locking 89 

promoting 113 

removing from a project 68 

resynchronizing 88, 107 

selecting 66 

thawing 120 

unlocking 90 

updating 88 

viewing 78 

members locked by me 

filter 21 

members with label 

filter 21 

members with state 

filter 21 

menu bar 

described 9 

merging 

revisions 153 

metadata 

described 216 

Microsoft Visual Basic integration 158 


checking in members 162, 196 


222 > > > > > > > > > > > > > >



project 160 

Microsoft Visual C++ integration 162 






project 165 

Microsoft Visual J++ integration 167 






project 169 

modified working files 

filter 21 

N 

Name keyword 94 

O 

opening 

a member history 132 

a project 58 

a sandbox 60 

out of sync members 

filter 21 

P 

preferences 

connection 28 

general 26 

saving 41 

setting 26 

view 39 

product terms 

defined 213 

project 


adding members 62 

checkpointing 121 

creating 46 


using IBM Rational Rose 191 









demoting 117 

described 216 

dropping 55 

importing 47 

opening 58 

promoting 116 

removing members 68 

viewing 58 

project attributes 

editing 97 

viewing 97, 100 

project history 

viewing 102 

Project History window 



project information 

editing 96 

saving 98 

viewing 96 

project member 

described 216 

Project window 



ProjectName keyword 94 

ProjectRevision keyword 94 

promoting 

a project 116 

described 216 

members 113 

revisions 143 

Index 

> > > > > > > > > > > > 223

Index 

Q 

quitting 

a session 41, 42 

R 

Rational Rose integration 189 






project 191 

RCSfile keyword 94 

Registered Projects dialog box 

described 14 

Registered Projects window 

described 216 

Registered Sandboxes dialog box 

described 14 

Registered Sandboxes window 

described 216 

removing 

a development path 73 

members 68 

report 

creating 128 

types 125 

report information 

about 124 

Reporter 

described 124 

graphs 125 

resynchronizing 

described 216 

members 88, 107 

reverting 

a member 87 

described 216 

revision 

described 217 

revision description 

assigning 82 

described 217 

revision information 

editing 135 

saving 137 

viewing 135 

Revision keyword 94 

revision label 

described 217 

editing 137 

viewing 137 


described 217 

revision numbers 

assigning 81 

valid 81 

revisions 


comparing 151 

deleting 149 


demoting 144 

locking 145 

merging 153 

promoting 143 

unlocking 146 

viewing 141 

S 

sandbox 

build 74 

creating 48 










dropping 57 

importing 54 

opening 60 

scanning for changes 79 

types 51 

viewing 60 

sandbox information 

viewing 99 

224 > > > > > > > > > > > > > >

Sandbox window 



sandboxes 

described 217 

saving 





scanning sandboxes 

for changes 79 

selecting 

members 66 

session 

quitting 41, 42 

setting 

member revision 148 


shortcut menu 

described 14 

Source keyword 94 

Starbase CodeWright integration 193 





project 195 

starting 

a session 24 

branch during check in 81 


state 

described 218 

State keyword 94 

status bar 

described 14 

strict locking 

described 218 

subproject 

creating 69 

described 218 

subsandbox 

described 218 

Sybase PowerBuilder integration 171 






project 173 

T 

table 

of keywords 94 

terms 

defined 213 

thawing 

described 218 

members 120 

tip revision 

described 218 

toolbar 

described 10 

toolbar buttons 

described 10 

general 10 

Member History window 12 

Project History window 13 

Project window 11 

Sandbox window 11 

trunk 

described 218 

types 

reports 125 

sandboxes 51 

U 

unlocking 

members 90 

revisions 146 

updating 

a member’s revision 107 

members 88 

updating a member revision, described 218 

user 

described 1 

user name 

described 218 

using 

Index 

> > > > > > > > > > > > 225

Index 

filters 20 

integrations 157 

keywords 91 

V 

variant sandbox 

creating 48 


view preferences 39 

viewing 

a project 58 

a sandbox 60 

archive information 133 

change packages 206, 210 

commands 21 

development path information 97 

member attributes 104 

member history 132 



members 78 

project attributes 97, 100 

project history 

opening 102 



revision labels 137 

revisions 141 

sandbox information 99 

working files 141 

Visual Age for Java 


Visual Difference window 

described 218 

VSky Software Manager 

before starting 8 

configuring 26 

graphical user interface 9 

starting 8 

VSky Software Manager integrations 

described 156 

using 157 

W 

WebGain VisualCafé integration 179 






project 181 

working file 

comparing to member revision 85 

described 218 

discarding changes 87 

working files 

viewing 141 

workspace 

described 13 

226 > > > > > > > > > > > > > >

The Vertical Sky Software Manager User Guide - MKS

Create successful ePaper yourself

Delete template?

Save as template?