Hey @christoffer, these are all great questions!
Once the program gets going, you’ll be able to submit a DC-compatible version of your app as a separate version on your Marketplace listing. This will trigger the review process, which (unlike a typical review) will include looking at the results of your readiness checklist and testing results. You should expect this process to take a longer (think 4-6 weeks rather than 5 days), and there might very well be some back-and-forth with Atlassian. Once it’s approved your DC version will be available in Marketplace as a full-fledged version (vs just a badge as it is today).
Now, you rightly ask what we’re going to do with all the existing apps with the old badge, which is set via the
atlassian-data-center-compatible parameter. That parameter has been serving two purposes:
- Letting customers know (via the badge) that the vendor declares the app to be DC compatible
- Letting the UPM know that the app is DC compatible, and is therefore valid to be installed / updated in a DC instance
Re #1, Since we’re introducing a new, more robust program for declaring DC readiness, it might be confusing to have both the badge (old program) and full-fledged DC versions (new program). But to provide a bridge for all the existing apps in Markteplace, we’re carefully considering how to handle what we display to customers. OCNB, we haven’t yet decided the best approach.
Re #2, given all the customers that have these apps installed, we are duty bound to have UPM continue recognizing the DC parameter for existing apps. So you can expect that for some period of time we will keep the DC parameter in our data model for existing apps and UPM will continue treating it as it does today.
We’ll be providing more details on the specifics of the program in the coming months. Please watch this space.