feat: Update rollout documentation for UIKit-removal spike to clarify migration strategy and feedback process
This commit is contained in:
@@ -10,6 +10,9 @@
|
||||
- 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 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
|
||||
|
||||
---
|
||||
|
||||
|
||||
Reference in New Issue
Block a user