A good git workflow is essential for managing third-party modules and ensuring a smooth Odoo experience. Here’s a recommended approach, even if you use modules from trusted sources like VentorTech.

Basic Setup

• Production Server: Your live Odoo environment.

• Staging Server: A separate environment for testing changes before deploying to production.

Key Principle: Test on Staging, Then Deploy to Production

Odoo setups are unique due to module interactions. Testing on staging helps catch unexpected issues before they impact your live system.

Updating a Third-Party Module

1. Create a new branch from your production branch for the module update.

2. Merge this branch to staging, deploy, and test thoroughly.

3. If all is well, merge the same branch to production and do a final check.

Special Case: VentorTech Ecosystem Subscribers

• VentorTech Modules: Updates are pushed to your ventor-tech-products branch (or version-specific branches like ventor-tech-products-16).

• Customizations: If we’ve made custom changes for you, they’ll be in a separate ventor-tech-customizations branch. Use this branch to ensure compatibility.

Why Separate Branches?

• Clean Updates: Keeping VentorTech modules separate makes it easier to apply updates without affecting your other customizations.

• Customization Safety: The ventor-tech-customizations branch includes both your custom code and the specific version of our product it was built for, preventing conflicts with newer releases.

Upgrading VentorTech Modules:

1. Merge ventor-tech-products to your staging branch.

2. Deploy and test on staging.

3. If successful, merge to production and do a final check.

Need More Help?

Contact us at https://support.ventor.tech/