Plan migration from boost::process v1 to v2

[AnarManafov]

Status: Compatibility Resolved ✅ | Migration Planning Phase 📋

DDS currently uses boost::process v1 API. With the introduction of Boost 1.89+, where v2 became the default, DDS now has conditional compilation support that maintains compatibility with both old and new Boost versions.

Background

Boost.Process v2 provides significant improvements:

• Enhanced stability and ASIO integration
• Better async I/O handling
• Improved process lifecycle management
• Modern C++ design patterns

The v1 API is currently deprecated but still maintained and supported in modern Boost versions for backward compatibility.

Current Implementation

As of August 2025, DDS has implemented conditional compilation that:

• Uses boost/process/v1.hpp when available (Boost 1.85+)
• Falls back to original API for older Boost versions (1.75+)
• Provides seamless compatibility across Boost versions

Migration Goal

Evaluate and plan migration to boost::process v2 to:

• Take advantage of stability improvements
• Potentially resolve edge cases in child process handling
• Align with modern Boost library design
• Ensure long-term maintainability

Priority

Medium Priority - No immediate urgency as v1 API remains supported and stable. Migration should be planned and evaluated thoroughly.

[AnarManafov]

Updated Context & Migration Plan for boost::process v2

Current Status (August 2025)

✅ Compatibility Issue Resolved: DDS now builds successfully with Boost 1.89+ through conditional compilation that uses boost::process v1 API when available, providing backward compatibility with older Boost versions.

boost::process v1 Deprecation Timeline

From the official Boost documentation (Boost 1.86+):

Note: Process v1 will be deprecated in the future. Use v2 for new projects.

Key Points:

• Current Support: boost::process v1 is still fully supported and maintained in modern Boost versions
• Availability: v1 API remains available via boost/process/v1.hpp headers in Boost 1.85+
• Timeline: No specific deprecation or removal date has been announced by the Boost team
• Stability: v1 continues to receive bug fixes and is considered stable for production use

Migration Priority Assessment

🟡 MEDIUM PRIORITY - Not urgent, but should be planned for future releases

Reasons:

1. No Immediate Risk: v1 API is explicitly maintained for backward compatibility
2. Working Solution: Current conditional compilation provides seamless compatibility
3. Gradual Transition: Boost follows conservative deprecation policies with long transition periods
4. Production Stability: v1 is proven stable, v2 benefits need evaluation

Recommended Migration Strategy

Phase 1: Evaluation (v3.15-v3.16)

• Evaluate boost::process v2 benefits for DDS use cases
• Assess API differences and required code changes
• Test v2 stability with DDS workloads
• Compare performance characteristics

Phase 2: Implementation (Future Release)

• Create feature branch for v2 migration
• Update core process handling code
• Migrate test suites
• Update documentation
• Ensure backward compatibility during transition

Phase 3: Migration (Major Release)

• Default to v2 API while maintaining v1 fallback
• Deprecate v1 usage in DDS documentation
• Plan eventual removal of v1 compatibility code

Technical Benefits of v2 Migration

• Improved ASIO Integration: Better async I/O handling
• Enhanced Stability: Improved process lifecycle management
• Modern C++ Design: More consistent with current Boost libraries
• Potential Bug Fixes: May resolve edge cases in child process waiting

Conclusion

While migration to boost::process v2 is recommended for long-term maintainability, there's no immediate urgency. The current compatibility solution provides a solid foundation and allows for a planned, thorough migration when resources permit.

The priority should be on evaluating the actual benefits v2 would provide for DDS's specific use cases before committing to the migration effort.