Skip to content

deprecation: Notify downstream systems about v0.3.0.0 API changes #220

Description

@kcenon

5W1H Specification

  • Who: Maintainers
  • What: Notify all downstream system maintainers about deprecated APIs in common_system
  • Where: All dependent repositories (see list below)
  • When: Before v2.x final release
  • Why: Ensure downstream systems have time to migrate before v3.0.0 breaks them
  • How: Create tracking issues in each downstream repository

Parent Issue

Part of #213 - Deprecated API Removal Plan for v3.0.0

Downstream Systems to Notify

System Repository Status Issue
thread_system kcenon/thread_system [x] Notified #331
logger_system kcenon/logger_system [x] Notified #248
monitoring_system kcenon/monitoring_system [x] Notified #269
pacs_system kcenon/pacs_system [x] Notified #399
database_system kcenon/database_system [x] Notified #276

Notification Content

Each downstream system should be informed about:

  1. Legacy logger method deprecation

    • log(log_level, const std::string&, const std::string&, int, const std::string&)
    • Migrate to: log(log_level, std::string_view, const source_location&)
  2. THREAD_LOG_ macros* deprecation

    • THREAD_LOG_TRACE, THREAD_LOG_DEBUG, THREAD_LOG_INFO, etc.
    • Migrate to: LOG_TRACE, LOG_DEBUG, LOG_INFO, etc.

Migration Resources

Acceptance Criteria

  • Issues created in all downstream repositories
  • Each issue includes migration guide links
  • Timeline communicated (removal in v3.0.0)

Metadata

Metadata

Assignees

Labels

architectureArchitectural changes and design

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions