[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) issues at jboss.org
Wed Jul 16 16:10:29 EDT 2014


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

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

[~maxandersen] The initial statement in this JIRA, and in fact statements on the call w/ me that caused the JIRA to be opened, was about updating ALL of JBDS, not just parts of it. 

And, as you know, we cannot update parts of JBDS that are installed via the installer because p2 won't let us. There are ways to break that restriction, and allow users to do precisely that, but every time I've suggested it, I've been shot down - see JBDS-3073 for recent discussion. So we are reduced to (as always) two scenarios:

a) JBDS installer -- locked down collection of features; can only be upgraded en masse (like doing a Fedora 19 -> Fedora 20 upgrade -- it's all or nothing). Recommend NOT SUPPORTING update to non-GA, unless we ensure the UI is obviously changed to show the "beta" status (splash screen, Help > About) and we ensure customers are aware this is *PROBABLY NOT A REVERSIBLE PROCESS* (uninstall/revert config may break the install). Even with those caveats implemented I still wouldn't recommend this - customers who want to try a pre-GA version ought to install it from a separate installer into a separate folder so that if they need to go back to the old GA, the effort is negligible and guaranteed to work. And it's obvious that their 8.0.0.GA folder is not the same as their 8.1.0.Alpha folder.

b) JBDS BYOE/Marketplace -- one feature defines what gets installed, but users are free to cherry-pick which features they want to uninstall or upgrade. Recommend SUPPORTING update to non-GA provided that the UI is *obviously changed in some way to identify those non-GA pieces* and that they can be *uninstalled w/o breaking the install*.

Since the EA site will be available for BOTH installer-installed and BYOE/Marketplace-installed users, IMHO using EA for JBDS updates is a bad idea. (This does not mean that it can't be used for experimental stuff and pre-release JBDS IS content, since those are inherently uninstallable.)

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


More information about the jbosstools-issues mailing list