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

[Max Rydahl Andersen (JIRA)]

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

Max Rydahl Andersen commented on JBDS-3085:
-------------------------------------------

{quote}
Right, and because uninstalling a product is problematic at best, my gut feeling here is we should NOT support the notion of upgrading from GA to non-GA. 
{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 ?

At what point is JBDS IS not going to be okey to have in early access then ? once it have gone GA for Luna it is not okey to provide earlyaccess installs from central for it ?

This seems very limiting and contradictory to me.

I'm completely fine saying "because of technical reason X we decide not to include earlyacccess of subpart Y" on a case by case basis but this "anything that is GA and we provide cannot be provided via early access" as a blanket rule makes the whole concept of earlyaccess in central of extremely little value and if that is the really the opinion of the team I do not think it makes sense to even provide this early access feature.

To be clear - I *DO* think it makes sens to provide early access via central and I *DO* think if it is technically possible we should provide early access to our own components this way. 

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