After a Cloud release moves from Early Access (EA) to General Availability (GA), Developer Studio still flags a target-version mismatch because the downloaded core source files' build.properties is marked with an '-EA' suffix — does this mean the environment (or the downloaded source) is actually still running Early Access code rather than GA?

All FAQ questions / Developer Studio, deployment, and upgrades

Answer

Not necessarily — the version value in build.properties reflects the code-generation engine's own version, not the actual application source code version. If the code generator itself didn't change between the EA and GA milestones of a release, that value can legitimately stay marked '-EA' even though the actual source code and your environment are genuinely on GA; IFS doesn't ship a new code-generator version (which requires regenerating every file) unless something in the generator itself actually changed. This build.properties value is really an internal process detail that happens to become visible through this particular Developer Studio target-version check, rather than a reliable EA-vs-GA indicator for the source code itself.

Documentation-based answer. Confirm the product and release before applying it. This answer has not been verified in an IFS environment.

← Browse Developer Studio, deployment, and upgrades questions