For the past two months, I've been reporting to the TSC that the installer teams were having stability issues and have been unable to meet the requirements of MS3.1. There doesn't seem to be any common root cause. Instead, it seems to be multiple issues, unique to each installer.
The first adjustment we made was to move MS3.1 out by one week. Unfortunately, the stability issues have persisted, so we now need to consider moving the entire schedule out, beginning with MS5. Therefore, I am proposing a two week shift. This is based on a discussion with the installer PTLs at last week's release meeting.
See the attachment for the suggested revised schedule and please be prepared to discuss and vote at tomorrow's TSC meeting. Let me know if you have any questions or comments.