Support early access and production releases - distribution infrastructure. --------------------------------------------------------------------------- Key: JBTIS-379 URL: https://issues.jboss.org/browse/JBTIS-379 Project: JBoss Tools Integration Stack Issue Type: Feature Request Components: distribution Affects Versions: 8.0.0.GA Reporter: Paul Leacu Assignee: Paul Leacu It's necessary to split the IS update sites into strictly released content (.Final features) and early access content (.Final features + Beta, etc) * Need one p2 site for IS released stuff and a second one for EA stuff, in order to prevent a customer from accidentally installing EA (Alpha/Beta) content from a Final zip; also need two discovery sites/plugins/etc. * What do we call the zips? jbdevstudio-integration-stack-8.0.0-updatesite.zip jbdevstudio-integration-stack-8.0.0-updatesite-earlyaccess.zip jbdevstudio-integration-stack-8.0.1-updatesite.zip jbdevstudio-integration-stack-8.0.1-updatesite-earlyaccess.zip jbdevstudio-integration-stack-8.0.2-updatesite.zip (no EA after this) jbdevstudio-integration-stack-8.0.3-updatesite.zip (maintenance build) jbdevstudio-integration-stack-8.0.4-updatesite.zip (etc.) * Where do we put the content? https://devstudio.redhat.com/updates/8.0/devstudio-directory.xml (just need one plugin, but have it point to a composite site of the two IS sites (released + earlyaccess)) * Is in necessary to have two p2 community sites as well?