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

[Nick Boldt (JIRA)]

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

Nick Boldt commented on JBDS-3085:
----------------------------------

{quote}so you are fine to install addons that makes the product unsupported and cannot be undone, but installing lets say "newer version of mobile tools" is not okey this way just because it is part of our initial install ?{quote}

No, you misunderstand. Everything in JBoss Central or EA *CAN* be uninstalled. Products can *NOT*. 

So I'm fine to install/uninstall extras (including both 3rd party and JBDS IS too from Central or EA), just *not the base JBDS install's "Branded Product" feature*. 

Uninstallation will be possible because all the "before I installed the dangerous stuff" target platform content will still be available, so p2 can resolve & recreate the previous state.

I also think that visually, *IFF we are going to support the idea of updating from JBDS BYOE/Marketplace ("Core Features" feature) 8.0.0.GA -> 8.x.y.non-GA*, we need to do more than just having the stuff in Central that is Early Access *{color:yellow}marked with yellow{color}*, since once it's installed it vanishes from the Central UI (unless you check "show installed"). 

I would update the splash and Help > About graphics just so it's obvious we've moved to an unsupported state. 

A supported platform w/ unsupported add-ons is one thing (like if you run RHEL and chose to manually install a beta version of Chrome). If a user contacts GSS they can say "uninstall that EA stuff and try again". But moving to a completely unsupported platform (eg., Fedora Rawhide) means you get NO support, and it should be visually obvious and there should be a daily reminder of that, IMHO.

> 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)