16.6 required stop planning

%16.6 IS NOT an upgrade stop.

%16.7 IS an upgrade stop.

The reasons are:

1. There isn't any technical requirements mentioned for %16.6 on this issue.
2. The number of database migrations is not a big concern for %16.7, and could be deferred to %16.7 for migration pressure relieving.
3. There might be a UX requirement from Distribution (Internal only) in %16.7 pending on internal discussion (Internal only).

===========================================================

Similar to 16.3 required stop planning (#415993 - closed), creating this planning issue to collect list of changes require stop @ 16.6.

You can review the Common scenarios that require stops and avoiding required stops to confirm, if you are still not sure after reviewing the documentation, please leave a comment with the link to your issue/epic in this issue for others to review.

If your change requires stop and cannot wait till %16.6, please reach out to @dorrino and @plu8.

To help to confirm whether %16.6 is actually a required stop, please try to list the issues below before 2023-11-03 (your local time).

List of changes require stop @ 16.6

• <insert Epic/Issue links below>