feat: Enhance communication and documentation for standup context and work item clarity
This commit is contained in:
@@ -10,7 +10,7 @@
|
||||
- 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
|
||||
- Include feature-flag planning for the broader UIKit-removal spike, including dismissal sequencing changes that affect consumers
|
||||
- Focus now on creating a process-oriented rollout document for the UIKit-removal spike that can be shared for feedback
|
||||
- The process-oriented rollout document for the UIKit-removal spike has been drafted and sent to Jeff for review
|
||||
- The rollout document should frame the work as a more deliberate migration phase toward the SwiftUI-only path, not as a correction to a prior failed attempt
|
||||
- The rollout document should make clear that the migration plan uses a dual-path pattern to switch between the `UIHostingController` path and the SwiftUI-only path during rollout
|
||||
- The rollout should be described as a global feature-flag rollout, not entry-point-based enablement
|
||||
@@ -34,6 +34,7 @@
|
||||
- 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
|
||||
- Keeping the consumer-facing rollout document aligned with the actual global-flag rollout model and broad XQ1 validation requirement
|
||||
- Incorporating Jeff's pending review feedback on the `PDIAP-14859` rollout draft once it arrives
|
||||
|
||||
---
|
||||
|
||||
|
||||
Reference in New Issue
Block a user