Skip to content

Conversation

@Shaddoll
Copy link
Member

Summary

[Brief summary of the change, including the rationale and intended effect]

Type of Change

  • Add new API(s)
  • Add new data type(s)
  • Add new field(s) to existing data type
  • Remove field(s) from data type
  • Remove data type(s)
  • Remove API(s)
  • Other (please provide detailed description)

Data Effect

  • Does it change the data stored in database?

Detailed Description

Delete unused fields of active-active which are not supposed to be used

Impact Analysis

  • Backward Compatibility: No, but nobody should be using the field because the feature isn't publicly announced.
  • Forward Compatibility: Yes.

Testing Plan

  • Unit Tests: [Do we have unit test covering the change?]
  • Persistence Tests: [If the change is related to a data type which is persisted, do we have persistence tests covering the change?]
  • Integration Tests: [Do we have integration test covering the change?]
  • Compatibility Tests: [Have we done tests to test the backward and forward compatibility?]

Rollout Plan

  • What is the rollout plan?
  • Does the order of deployment matter?
  • Is it safe to rollback? Does the order of rollback matter?
  • Is there a kill switch to mitigate the impact immediately?

@Shaddoll Shaddoll merged commit 0857e50 into master Oct 27, 2025
5 of 6 checks passed
@Shaddoll Shaddoll deleted the aa branch October 27, 2025 20:01
Shaddoll added a commit that referenced this pull request Oct 30, 2025
Shaddoll added a commit that referenced this pull request Oct 30, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants