Jump to main content

Product Documentation

Customer Support Software Academy Community Forums

HCL VersionVault 3.0.2

HCL VersionVault V3.0.2
Overview
Installing
Upgrading
Administering
Developing
Managing change and releases
Integrating
Tutorials
Extending product function
Reference
Glossary

Home
Managing change and releases
Learn how to manage change and release in the product.
Managing software projects
Working in base VersionVault
Implementing project development policies

Managing change and releases
Learn how to manage change and release in the product.

Implementing project development policies

These topics present scenarios that implement policies in a base VersionVault project.

About implementing project development policies
Good documentation of changes is required
All source files require a progress indicator
Label all versions used in key configurations
Isolate work on release bugs to a branch
Avoid disrupting the work of other developers
Deny access to project data when necessary
Notify team members of relevant changes
All source files must meet project standards
Associate changes with change orders
Associate project requirements with source files
Prevent use of certain commands
Certain branches are shared among HCL VersionVault MultiSite sites
Sharing triggers among different types of platform

Rate this topic

5 stars 4 stars 3 stars 2 stars 1 star

Share: Email
Twitter

Disclaimer
Privacy
Terms of use
Cookie Preferences