I appreciate that Platform 7 and RESTv2 is going to require a large amount of change. We’ve experienced this ourselves migrating several of our own internal apps. For what it’s worth, after migrating a couple apps, the migration starts to become automatic: bumping the same versions, changing the same code, fixing the same exceptions, etc. But I know it’s daunting to make these changes across several apps for several products. We’ve tried to make the necessary changes as clear as possible, but please let us know if our documentation needs more detail or clarity.
As you allude to, we were relying on the general platform announcements to communicate the most disruptive changes to Bitbucket 9. Nearly all the Bitbucket-specific API changes were communicated with deprecations over the 8.x release timeline.
There’s been a lot of discussion around the right timing for our EAP. Some partners gave feedback at TEAM 24 that “partial” EAPs weren’t terribly valuable. They wanted API-complete EAPs before starting work. If you think an earlier EAP with a partial set of changes would have helped, I’ll take that on board for the next Bitbucket major release.
We are actively monitoring this forum and are happy to help with specific problems adopting Platform 7 and/or RESTv2. I hope that will help accelerate the work.