Project: aptanastudio
Issue APSTUD-4703: Fix revert system
When we deploy a new Aptana (or Titanium) release, we deploy it to a new location each time on Amazon S3, or to the same location (but wiping the old contents) on download.appcelerator.com. It appears that the P2 system now requires the old update site to exist in order to be able to revert to the previous version. Suggest that we use the "mirror" task to merge in the previous versions (though Chris has suggested their might be a different approach to use as well) {code}	{code} So, when deploying 3.1.1, we merge in 3.1.0. We can keep the repos to merge in on the build server (we do them as tagged builds now) and update those references as part of updating version #s. However, maybe there is a better way to automatically figure out where these repos to merge in live. h3. Suggested Fix # Upgrade the two deployment scripts (the bash one for Titanium Studio and the Ruby release one for Studio 3) to take a list of versions and merge those into a new repo # Upload the new repo to the same location as before # Test the combined version by installing Version A, upgrading to version B, and being able to revert to version A (assuming A & B are both versions on the update site)
Story points: 20