[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=12984975#comment-12984975 ] 

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

{quote}
Customer: "You upgraded me to this version now X isn't working"
GSS: "yeah, Alpha releases aren't supported but I'll raise this to engineering to get it fixed in the GA"
Customer: "ermm, in the meantime how do I continue working on this critical project?"
GSS: "Can you reinstall JBDS GA across all your developer machines and waste your week doing this and setting everything up again?" <dramatics for added affect>
{quote}

just to be clear - for this to happen all the developers would have had to go manually enable earlyaccess, read the warnings and still do the update on all the machines...

I don't think that will happen ;)

{quote}
Allowing upgrades to newer early access components if customers have installed them already is okay, but this JIRA is talking about upgrading JBDS to an unsupported version, not upgrading one plugin to an unsupported one.

So in my opinion, we can never do this unless we have some serious warnings and pop ups but that doesn't make sense to me. We should just have separate downloads for non GA releases."
{quote}

I fell like the above paragraphs you write are contradictory.

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)


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