Updates and Development

Update Policy

Взрыв4D software updates are released on a scheduled basis — once per quarter (or more frequently if required).

Update Contents

Each update may include:

• Bug fixes and defect resolution
• Performance improvements
• New features and capabilities
• User interface enhancements

What the Customer Receives

Component	Description
Changelog	Detailed description of all changes
Installation Guide	Update instructions
Release Notice	Information on significant changes
Updated Documentation	Where changes affect user workflows

Update Process

1. The developer releases a new version of the software package
2. The customer receives a release notification
3. The update is delivered centrally via an internal repository or as installation packages
4. Updates via Docker environments and internal image registries are supported

Version Control

• A version control system (Git) is maintained
• Change tracking and rollback capabilities are supported
• All changes undergo code review and testing

Update Testing

Type	Description
Unit tests	Automated verification of individual components
Integration tests	Verification of component interactions
Manual checks	For critical components with documented results

Feature Expansion

Expansion of functionality can be performed under a separate agreement:

1. The user submits a feature request with a technical justification
2. The product owner decides whether to include it in future releases
3. Implementation is agreed upon with the technical team

Roadmap

Feature development follows an agreed roadmap approved by the product owner.