Audience: Security, procurement, enterprise architecture, DevOps
Scope: Maintenance, lifecycle, compatibility, upgrade guarantees, support model
The Enterprise Assurance commitments described on this page apply to subscribers on the Quantum tier or higher, as defined in the wxrks Software Order Form.
Architectural Compatibility Model (TMGMT-Based)
wxrks' Drupal integration is built as an extension of the TMGMT (Translation Management) module. Because of this:
Connector compatibility aligns directly with Drupal versions supported by TMGMT.
Based on TMGMT’s published roadmap and current releases, the connector is compatible with:
Drupal 10
Drupal 11
As TMGMT advances version support, wxrks maintains matching compatibility.
Active Maintenance and Version Upgrade
The Drupal connector plugin is continuously maintained by wxrks engineering and product teams, including:
Bug fixes
Security updates
Dependency and API adjustments
Enhancements based on subscriber needs
Maintenance is governed by wxrks' standard release and QA processes.
Minor Updates (Drupal and TMGMT)
Minor updates include releases such as Drupal 10.1 → 10.2 or routine TMGMT module updates. These updates introduce improvements, bug fixes, and non-breaking enhancements.
They are designed to be backward compatible, which means:
Existing features and integrations generally continue to function without modification.
The wxrks Connector typically does not require any changes.
Clients can choose when to adopt these updates based on their internal maintenance or deployment schedule.
wxrks requests 30 days’ advance notice before a minor Drupal or TMGMT update so we can run compatibility validation and apply adjustments if needed.
Major Updates (e.g., 10.x → 11.x)
Major versions introduce significant architectural changes, updated dependencies, or new APIs. These updates may include breaking changes, requiring module maintainers to review and adjust their code.
Because of this:
wxrks treats major version upgrades as controlled, high-impact events.
Clients must notify wxrks 120 days in advance before adopting a new major version.
This window allows for compatibility assessment, required module updates, and full QA validation before use in production.
Compatibility Validation Based on Subscriber Roadmaps
wxrks continuously monitors:
Drupal core development
TMGMT releases updates and deprecations
When a subscriber begins planning a migration to a new major version:
wxrks initiates full compatibility validation
Any necessary plugin updates are prepared
Compatibility is certified once TMGMT has published a compatible release
This ensures compatibility is never speculative and remains aligned with upstream TMGMT support.
Upgrade Coordination Policy
To ensure predictable and safe upgrades, wxrks requests:
Minimum 120 days’ advance notice for any planned major Drupal upgrade.
This window allows wxrks to:
Complete compatibility assessments
Validate behavior against real subscriber configurations
Deliver required updates if needed
Coordinate rollout to minimize operational risk
This assumes a compatible TMGMT release is already available for the target Drupal version.
Quality and Security Standards
All connector changes follow wxrks' internal SDLC and quality controls, including:
Formal code review
Regression testing
Validation in subscriber-aligned environments
Release governance aligned with wxrks' SOC 2 Type II certified controls
Enterprise clients may request a formal Security & Maintenance Statement.
Dedicated Support & SLA Coverage
Subscribers receive full support for the Drupal connector under wxrks' existing enterprise SLA, including:
Configuration and setup assistance
Troubleshooting and defect resolution
Upgrade planning and compatibility validation
Guidance on TMGMT workflows and provider behavior
For response times, escalation paths, and availability commitments, please refer to your wxrks SLA and Help Center support policies.
Distribution & Installation Expectations
The plugin is delivered by wxrks as part of the connector package.
Installation supports enterprise deployment practices (including Composer-based workflows) where required by subscriber DevOps policy.
wxrks provides the appropriate distribution method and access details during implementation.