[ https://issues.jboss.org/browse/JBDS-3093?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen updated JBDS-3093: -------------------------------------- Description: This is continuation of JBDS-3009 which was discussing full updates of devstudio that made everyone focus on old limitations. Thus lets discuss how far we are ok (in principle/not technical terms) early access goes A) in principle - are you ok we provide functionallity in devstudio to install additional early access features ? I assume YES because that is what the early access feature does that everyone was fine with before. B) in principle - are you ok we provide functionallity in devstudio to install early access features of things that are in addition to the default installed parts (i.e. not part of core, things like hybrid mobile tools ? ) I assume YES since this has zero technical difference from A C) in principle - are you ok we provide functionallity in devstudio to install early access features of things that are part of the base install (i.e. we provide an early access of devstudio that has updates to hibernate tools and jaxrs that supports JavaEE 7 better - just as example) ? I hear you say NO to this even though it is EXACTLY the same mechanism we need to provide install/rollbacks for the above - we just don't have that in place yet but that IS doable to do if we choose to do so and make it clear what is installed (see But if you cannot even agree to it by principle then any technical discussion is pointless. Thus can you give Yes/No answers to the above please ? My answers are: A) Yes B) Yes C) Yes ...all with the assumption we make it clear that once you do this you are running in "early access" mode. For me there is zero difference between A/B/C if done properly. And of course we should not do any of these blindly and without ensuring it is as smooth as possible but the mere definition of "early access" is : "You install this on your own risk - please don't expect things to work completely fine afterwards". was: Max brought up a question on a call today: *Should we be able to update JBDS 8.0.0.GA -> 8.1.0.Alpha1 via Early Access?* This was supposedly in the original scope for the creation of a Early Access site, but I never saw that. So, in order to get some eyeballs on this idea, and to get buy-in from QE/doc/dev/PM/PgM/PL, I'm cc:'ing some people here so we can discuss the cons and cons of this idea. cc: [~mmusaji] [~mmurray] [~mmalina] [~maxandersen] [~mickael_istria][~ldimaggio] [~burrsutter] [~jpallich] [~rruss] [~fbricon] (Aside: has anyone noticed that there's an plethora of people with "M" names on this team?) Things to consider: a) what happens if an 8.0.0.GA user suddenly finds they've updated to an Alpha or Beta release? Can they uninstall? (Probably not, if they started with the installer; probably yes if they started from BYOE / Marketplace.) b) how will GSS support these "I was on GA but not I'm on Beta" users? c) What about project examples that might / might not be compatible between 8.0 and 8.x, eg., because of changes in Eclipse Luna or a new default runtime (EAP 6.3, 6.4) ? d) what could possibly go wrong? Component/s: central -- This message was sent by Atlassian JIRA (v6.2.6#6264)