Software Engineering · Odoo glossary

Version Control

Version control records changes to files. Learn how Git commits and branches support review, release traceability and controlled code rollback.

Definition

In general ERP practice

Version control records changes to files over time so that earlier states can be inspected and compared. It helps a team understand what changed and collaborate without relying on manually named copies.

Git is a distributed version control system. Commits record changes in history; branches let work proceed separately before integration. A repository is useful only if the team can identify which code was actually deployed.

In Odoo

For Odoo custom modules, a repository can track source code, deployment scripts and versioned configuration. Separate branches give the client a place to review proposed repairs before release.

Reverting code does not necessarily reverse changes to database records, schema or external systems. Code versioning and data recovery need coordinated plans; a Git repository is not a substitute for database backups.

Repository review during an incident

  1. Trace the release

    Identify the deployed commit and the changes introduced since the last working release.

  2. Inspect the branches

    Separate proposed work from accepted code and identify incomplete or unreviewed changes.

  3. Assess reversal

    Determine which code changes can be reverted and which data changes need separate recovery.

Engineering references

The definitions draw on the primary engineering references below. The Odoo context explains their application to custom development, not a version-specific feature guarantee.