At no point has that ever been communicated to partners. Are you serious?!
Atlassian is going to forcibly plaster public marketplace Connect apps with end-user warning messages THREE SIX whole months before EOS and you’re only informing partners now, in this thread exposing a screw-up, and with THREE ONE month notice?! Surely you’ve miscommunicated something in your reply here?
!!!
The date at which you forcibly plaster a warning message on an app is the date which developers would consider to be an absolute and final hard migration deadline which needs to be communicated clearly with precise dates and abundant forewarning. If that’s not obvious to Atlassian it speaks volumes.
EOS (end of support) has always been communicated as a date beyond which platform support ends but apps still function as ~expected until some unknown EOL date. Warning messages for EOL (end of life) would make sense because the apps would stop functioning completely.
Warning messages applied prior or shortly after EOS could risk EXTREME LEGAL DAMAGES to partners if, for instance, customers cancel their subscriptions due to the unnecessary scaremongering of these warning messages.
The migration blockers are widely documented despite the ongoing gaslighting.
Hell, I’m still waiting for the fundamentals of versioning and updates to be finalised:
Let that sink in: versioning is not yet finalised on Forge!!!
You’re force-ramming everyone to migrate to a platform that hasn’t yet sorted out versioning and which inevitably results in zombie apps. Truly unfathomable disaster.