We are following this planning process:

1. Collect issues that require breaking changes or large refactors
2. Walk through each issue to determine that we want to take it in the next major version release, marking it with milestone investigation
3. Each issue will then be investigated, resulting in a one-pager that captures the following:
   1. The implementation cost of the change
   2. The importance (the customer impact) of the change
   3. Whether the change will cause a conflict with another change, require leveraging another change, and/or require implementation before another change can be implemented
   4. The actual proposed change as the result of the investigation
   5. The "digging in" that the investigator needed to do in order to document the above point
4. Once each issue is investigated, the costs will be aggregated and a target release date will be determine
5. We will then start the implementation on each issue according to the design from the one-pagers
6. Once the target date is reached, we will release the new major version regardless of what implementations still remain