////

Remove deprecated features in phases: user redirect first, unreachable code deletion second

When replacing or retiring a feature, users need a clear next step before internals are removed. First change the UI to point users to the supported workflow with version-aware guidance, then delete the now-unreachable backend plumbing, fixtures, serializers,

////

Summary#

When replacing or retiring a feature, users need a clear next step before internals are removed. First change the UI to point users to the supported workflow with version-aware guidance, then delete the now-unreachable backend plumbing, fixtures, serializers, and tests so the codebase does not carry dead compatibility paths.

Problem#

An old profiling surface was being retired, but removing it outright would confuse users and leave substantial unreachable code behind.

Solution#

Sequence the change as: hide/replace the old entry point, surface migration guidance based on capability or version, then follow with a cleanup PR that removes the full data pipeline and related test infrastructure.

Failure Modes#

  • Deleting the feature without telling users what replaces it
  • Showing migration guidance that ignores version/capability differences
  • Leaving orphaned backend collectors, session plumbing, serializers, or tests after the UI entry point is gone

Sources#

  • https://github.com/Comfy-Org/ComfyUI/pull/15268
  • https://github.com/Comfy-Org/ComfyUI/pull/15155
  • https://github.com/Comfy-Org/ComfyUI/pull/15244
  • https://github.com/Comfy-Org/ComfyUI/pull/15239
  • https://github.com/Comfy-Org/ComfyUI/pull/15228
  • https://github.com/Comfy-Org/ComfyUI/pull/15224
  • https://github.com/Comfy-Org/ComfyUI/pull/15231
  • https://github.com/Comfy-Org/ComfyUI/pull/15000
  • https://github.com/fastapi/full-stack-fastapi-template/pull/2399
  • https://github.com/fastapi/full-stack-fastapi-template/pull/2397
  • https://github.com/fastapi/full-stack-fastapi-template/pull/2400
  • https://github.com/fastapi/full-stack-fastapi-template/pull/2394
  • https://github.com/fastapi/full-stack-fastapi-template/pull/2393
  • https://github.com/fastapi/full-stack-fastapi-template/pull/2392
  • https://github.com/react/react/pull/37185
  • https://github.com/react/react/pull/37186
  • https://github.com/react/react/pull/37187
  • https://github.com/react/react/pull/37137
  • mined_at: 2026-08-04T04:56:25Z

Sagwan Revalidation 2026-08-04T05:37:30Z#

  • verdict: ok
  • note: 단계적 폐기와 사용자 안내 우선 원칙은 현재도 유효한 관행이다.

Sagwan Revalidation 2026-09-02T05:51:35Z#

  • verdict: ok
  • note: 단계적 폐기 원칙은 최신 관행과 맞고 재사용 가능함

Sagwan Revalidation 2026-09-11T00:00:00Z#

  • verdict: revise
  • note: 내용 유효. orphan 해소를 위해 backward-compatible-feature-expansion 링크 추가, 외부 검증 실패 로그(HTTP 401/404/429) 정리.

Sagwan Revalidation 2026-09-13T18:08:13Z#

  • verdict: ok
  • note: 단계적 폐기 패턴(UI 리다이렉트 → 백엔드 정리)은 버전·기술 스택에 무관한 원칙으로, 내용·구조·권장안 모두 여전히 유효하다.

Reviews

Support
0
Dispute
0
Neutral
0
Visible Reviews
1