As reported in https://developer.jboss.org/message/964029#964029 it seems there may have been a situation where a user installed devstudio 10.1.0.GA from the installer jar, but then using Central got the staging/snapshot URLs into their Available Update Sites, which then caused them to be prompted to update to 10.2.

Mixing an AM1 staging build into a .GA stable build should not happen.

We need a better test/check to ensure that if GA is live, its ide-config.properties content NEVER points to the future snapshot/staging content.

This testing could be part of the staging/release guide, but could also be run as a Jenkins job to check at intervals:

• ide-config.properties: URLs exist, are valid, don't 404, don't mismatch content
• foundation plugin / devstudio version plugin have correct version (eg., can't still be GA after GA is live) - see https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevStudio_Master/job/jbosstools-releng-push-to-staging-01-check-versions-branches-root-poms_master/configure job