[jbosstools-issues] [JBoss JIRA] (JBDS-3085) Should we be able to update JBDS 8.0.0.GA -> 8.1.0.Alpha1 via Early Access?

[Mustafa Musaji (JIRA)]

    [ https://issues.jboss.org/browse/JBDS-3085?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12985018#comment-12985018 ] 

Mustafa Musaji edited comment on JBDS-3085 at 7/15/14 4:36 AM:
---------------------------------------------------------------

{quote}
You have to be more clear here - what do you think the early access feature in new JBoss Central is for if not for installing early access components the user haven't installed yet ? (With clear warnings of course)
{quote}

Perhaps my understanding is not clear, but, installing early access components is fine, but that shouldn't change the version of JBDS. Install all the early access components you want, none of them are supported etc. 

{quote}
so you are fine to install addons that makes the product unsupported and cannot be undone
{quote}

They make the components unsupported, not the product. If customer installs an early access version of "angularjs tooling" but then has an issue with his workspace for example, if he's running an Alpha release of JBDS it's not supported. If he's running JBDS GA with a early access of "angularjs tools", he's still supported with any issue not related to angularjs tooling.

If you want to upgrade the user to a non supported version, we have to have a way customer can go back to a supported version easily without it affecting their workspace/projects and existing tools. At the moment, I believe this is not possible or as [~nickboldt] says, is "problematic at best". I'm starting to think even with warnings and pop ups, this isn't a good idea.


was (Author: mmusaji):
{quote}
You have to be more clear here - what do you think the early access feature in new JBoss Central is for if not for installing early access components the user haven't installed yet ? (With clear warnings of course)
{quote}

Perhaps my understanding is not clear, but, installing early access components is fine, but that shouldn't change the version of JBDS. Install all the early access components you want, none of them are supported etc. 

{so you are fine to install addons that makes the product unsupported and cannot be undone}

They make the components unsupported, not the product. If customer installs an early access version of "angularjs tooling" but then has an issue with his workspace for example, if he's running an Alpha release of JBDS it's not supported. If he's running JBDS GA with a early access of "angularjs tools", he's still supported with any issue not related to angularjs tooling.

If you want to upgrade the user to a non supported version, we have to have a way customer can go back to a supported version easily without it affecting their workspace/projects and existing tools. At the moment, I believe this is not possible or as [~nickboldt] says, is "problematic at best". I'm starting to think even with warnings and pop ups, this isn't a good idea.

> Should we be able to update JBDS 8.0.0.GA -> 8.1.0.Alpha1 via Early Access?
> ---------------------------------------------------------------------------
>
>                 Key: JBDS-3085
>                 URL: https://issues.jboss.org/browse/JBDS-3085
>             Project: Developer Studio (JBoss Developer Studio)
>          Issue Type: Enhancement
>      Security Level: Public(Everyone can see) 
>          Components: updatesite
>            Reporter: Nick Boldt
>            Assignee: Max Rydahl Andersen
>         Attachments: 128_jbds_icon_beta.png, splash_beta.png
>
>
> 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?



--
This message was sent by Atlassian JIRA
(v6.2.6#6264)