[ https://issues.jboss.org/browse/JBTIS-510?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen commented on JBTIS-510: ------------------------------------------- [~nickboldt] I hoped we were pass getting back to discussing merging EA content into GA content site. It should simply not happen. But to iterate again: A) Earlyaccess should not become available to users without them actually opting in - if we add EA to GA site then it will be available from "Help > Install" with no indication of it being earlyaccess before actually installed. B) Check for updates should not bring in EA content - EA could have overlapping/new versions of bundles that is not GA (we have not done this yet, but it is designed to allow for that), if we add EA to GA site then check for updates does this Also see: 26. Sep. 2014: https://issues.jboss.org/browse/JBIDE-18239?focusedCommentId=13006365&... {quote} And no, early access and central updatesites CANNOT be in the same updatesite - that have been discussed ad libitum before how that is not okey since: A) Earlyaccess IS NOT central B) if you add earlyaccess into central then users running Help > Check for updates (or install) will get earlyaccess content even though they have not enabled it. I would really appreciate if we stop having to return to that item again - central IS NOT earlyaccess and vice versa thus they cannot be intermingled. {quote} -- This message was sent by Atlassian JIRA (v6.4.11#64026)