Thank you for posting this topic @ibuchanan. First of all, I second the points highlighted by @remie and @aragot. It’s dizzying to navigate between changelog, CAC, CDAC and the partner portal when there is no apparent policy for what will appear where.
Here are some of my thoughts.
The platform 7 communication has been very hard to follow with a number of CDAC threads, even some changelog entries. Some threads have apparently died, and overlapping threads makes it really hard to follow where updated information will come. A platform 7 topic on CDAC with more high-level posts and less comments on scattered threads would probably be an improvement.
I also feel that the communication would benefit from more openness on estimated date schedules, and coordination between the different teams. Continuing on the Platform 7 topic, it was very confusing for us that the different Data Center teams had such different communication strategies. The Confluence team has had an ongoing communication in a thread with incremental EAP releases. Jira was early communicating, but haven’t implemented platform 7, but it still felt good to have a thread and somewhere we could start asking questions. Meanwhile the Bitbucket and Bamboo teams didn’t make any sound. We could only assume that they were ages from being ready since no communications had been made yet. When they finally added CDAC posts, they have come with extremely short timelines for compatibility testing. They gave the impression of being oblivious to the amount of effort that’s required of the Marketplace partners for compatibility work. I would have loved to get more consistent timeline communications.
A note on the RFC program. No RFC came for Two-Step verification for Data Center: Two-step verification login for Data Center - #25 by MateuszMiodek. It would have been natural to get an RFC of the concept before the EAP announcement, and our feedback and concerns would have been implemented into the first EAP. However, the team has been open to changes and quite transparent in their EAP communications, so kudos to them for that!