feat: Enhance documentation for UIKit-removal spike and clarify work item dependencies
This commit is contained in:
@@ -11,3 +11,5 @@
|
|||||||
- When a documentation or root cause update directly supports a story, report it under that story instead of as a separate standup item.
|
- When a documentation or root cause update directly supports a story, report it under that story instead of as a separate standup item.
|
||||||
- In standups, format Jira references as `ID - Title` or `ID Title`, not `ID, Title`.
|
- In standups, format Jira references as `ID - Title` or `ID Title`, not `ID, Title`.
|
||||||
- Jeff clarified that `PDIAP-15838` is the next story to work on and `PDIAP-15836` comes later.
|
- Jeff clarified that `PDIAP-15838` is the next story to work on and `PDIAP-15836` comes later.
|
||||||
|
- Clarification: the feature-flag and rollout planning feedback applies to the broader UIKit-removal spike, not only to the dismissal sequencing changes; the sequencing work should fit into that same consumer rollout plan.
|
||||||
|
- Jeff said the remaining spike deliverable is a clear consumer-facing rollout plan covering risky entry points like FTTransfer, consumer communication, XQ1 validation, a 30-day production period with no reported bugs, and a follow-up release to remove the feature flag and old code; he suggested sending that process-oriented document to Quy for feedback when ready.
|
||||||
|
|||||||
@@ -9,6 +9,7 @@
|
|||||||
- Follow up on `PDIAP-15765`, `PDIAP-15836`, and `PDIAP-15838`
|
- Follow up on `PDIAP-15765`, `PDIAP-15836`, and `PDIAP-15838`
|
||||||
- Finalize `PDIAP-14859` with a dual UIKit/SwiftUI plan that removes `UIHostingController` dynamically while preserving both flows appropriately
|
- Finalize `PDIAP-14859` with a dual UIKit/SwiftUI plan that removes `UIHostingController` dynamically while preserving both flows appropriately
|
||||||
- Prioritize `PDIAP-15838` next; `PDIAP-15836` comes later
|
- Prioritize `PDIAP-15838` next; `PDIAP-15836` comes later
|
||||||
|
- Include feature-flag planning for the broader UIKit-removal spike, including dismissal sequencing changes that affect consumers
|
||||||
|
|
||||||
---
|
---
|
||||||
|
|
||||||
@@ -21,6 +22,7 @@
|
|||||||
- Preserving accurate context when summarizing work from another machine
|
- Preserving accurate context when summarizing work from another machine
|
||||||
- Validating dismissal sequencing changes across SwiftUI flows
|
- Validating dismissal sequencing changes across SwiftUI flows
|
||||||
- Keeping REST deprecation scope explicit while GraphQL fallback still exists
|
- Keeping REST deprecation scope explicit while GraphQL fallback still exists
|
||||||
|
- Defining a consumer rollout plan for UIKit-removal sequencing changes, including validation, communication, and feature-flag retirement
|
||||||
|
|
||||||
---
|
---
|
||||||
|
|
||||||
|
|||||||
@@ -10,7 +10,7 @@ Update it only with explicit, project-relevant information that is useful for fu
|
|||||||
Current note: root cause was documented; the DOB validation issue was confirmed on TeenIdentityCheck for authenticated users, and Jeff approved moving the story to Done once the new sprint starts.
|
Current note: root cause was documented; the DOB validation issue was confirmed on TeenIdentityCheck for authenticated users, and Jeff approved moving the story to Done once the new sprint starts.
|
||||||
|
|
||||||
- `PDIAP-15836` - Modernize dismissal delegate lifecycle sequencing for pure SwiftUI environment
|
- `PDIAP-15836` - Modernize dismissal delegate lifecycle sequencing for pure SwiftUI environment
|
||||||
Current note: story came out of the AccountLink root cause investigation and related root cause document update; it was sized at 8 points, aligned with epic `26Q2 - Updating XFlowSDK to Decouple and Fix ApexKit Dependencies (Split Part 2)`, is meant to cover SwiftUI dismissal sequencing validation, and should come after `PDIAP-15838`.
|
Current note: story came out of the AccountLink root cause investigation and related root cause document update; it was sized at 8 points, aligned with epic `26Q2 - Updating XFlowSDK to Decouple and Fix ApexKit Dependencies (Split Part 2)`, is meant to cover SwiftUI dismissal sequencing validation, should come after `PDIAP-15838`, and should use the same consumer-impact feature flag as the UIKit-removal rollout if possible.
|
||||||
|
|
||||||
- `PDIAP-15838` - Remove Apollo for iOS
|
- `PDIAP-15838` - Remove Apollo for iOS
|
||||||
Current note: approved at 8 points; description and ACs were filled in and Jeff approved the scope to remove Apollo, GraphQL-specific networking code, related tests and mocks, and transport feature flags so REST remains. This is the next story to work on before `PDIAP-15836`.
|
Current note: approved at 8 points; description and ACs were filled in and Jeff approved the scope to remove Apollo, GraphQL-specific networking code, related tests and mocks, and transport feature flags so REST remains. This is the next story to work on before `PDIAP-15836`.
|
||||||
|
|||||||
Reference in New Issue
Block a user