[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
Sun Jul 13 23:18:29 EDT 2014


     [ https://issues.jboss.org/browse/JBDS-3085?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Nick Boldt updated JBDS-3085:
-----------------------------

    Attachment: 128_jbds_icon_beta.png
                splash_beta.png


{quote}There is zero difference here from any other earlyaccess content.{quote}

One difference is that updating a *PRODUCT* (not just a collection of features) can be problematic because *uninstalling* that product is likely to fail. Or, if you're moving from one Eclipse baseline to another (eg., from Kepler to Luna, or from Luna to Mars) there's a good chance the resulting installation will be completed borked.

I agree it *should* work, but I'm not sure it DOES work today, or that users would really expect that. Has anyone ever tried to update from Windows 7 to 8 on the same machine? Or to do an OSX upgrade w/o problems happening? (Admittedly Fedora upgrades DO work, as long as you don't wait too long ... I can't upgrade F16 any more because it's not on the servers.) 

And sure, Eclipse isn't an OS, but it's an eco-system, and as we've said for years, there are no guarantees that if you update the product you won't break half the 3rd party extras you installed on top.

{quote}All that being said I don't think first attempt at this would be FULL JBDS update - but simply parts of it.{quote}

In other words, we will potentially support BYOE/Marketplace users who want to upgrade from 8 to 8.x (or even 9?), but NOT installer users, because that would require a FULL JBDS update.

If a user upgrades from .GA to .Beta, should we have some branding plugin that changes the branding to drop a "Beta" marker stuff?

!128_jbds_icon_beta.png!

!splash_beta.png!

> 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