[jbosstools-issues] [JBoss JIRA] (JBDS-3093) Should we allow users to install updates to individual JBDS features (not the whole product) via Early Access?

[Max Rydahl Andersen (JIRA)]

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

Max Rydahl Andersen edited comment on JBDS-3093 at 10/19/15 6:20 AM:
---------------------------------------------------------------------

I completely disagree on adding support for restoring for earlyaccess but not for JBDS core. That just don't make sense to me.

Earlyaccess if anything would be reliant on also being able to rollback to the exact matching JBDS core version it been tested with.

Earlyaccess is not at all a tiny site when you include that integrationstack is in there for periods of time.

[~akazakov] I'm fine closing this issue since it is not covering the actual problem that we do need to look at: how to handle multiple releases at different release schedules of our eclipse features  - today we have jbds core vs IS at different times; what happens when we add more into this. Then we can't just install all of JBDS all the time. 


was (Author: maxandersen):
I completely disagree on doing this for earlyaccess but not for JBDS core. That just don't make sense to me.

Earlyaccess if anything would be reliant on also being able to rollback to the exact matching JBDS core version it been tested with.

Earlyaccess is not at all a tiny site when you include that integrationstack is in there for periods of time.

[~akazakov] I'm fine closing this issue since it is not covering the actual problem that we do need to look at: how to handle multiple releases at different release schedules of our eclipse features  - today we have jbds core vs IS at different times; what happens when we add more into this. Then we can't just install all of JBDS all the time. 

> Should we allow users to install updates to individual JBDS features (not the whole product) via Early Access?
> --------------------------------------------------------------------------------------------------------------
>
>                 Key: JBDS-3093
>                 URL: https://issues.jboss.org/browse/JBDS-3093
>             Project: Developer Studio (JBoss Developer Studio)
>          Issue Type: Enhancement
>          Components: central, updatesite
>            Reporter: Nick Boldt
>            Assignee: Nick Boldt
>             Fix For: LATER
>
>
> Max said:
> {quote}
> This is continuation of JBDS-3009 which was discussing full updates of devstudio that made everyone focus on old limitations. 
> Thus lets discuss how far we are ok (in principle/not technical terms) early access goes
> A) in principle - are you ok we provide functionallity in devstudio to install additional early access features ?
> I assume YES because that is what the early access feature does that everyone was fine with before.
> B) in principle - are you ok we provide functionallity in devstudio to install early access features of things that are in addition to the default installed parts (i.e. not part of core, things like hybrid mobile tools ? )
> I assume YES since this has zero technical difference from A
> C) in principle - are you ok we provide functionallity in devstudio to install early access features of things that are part of the base install (i.e. we provide an early access of devstudio that has updates to hibernate tools and jaxrs that supports JavaEE 7 better - just as example) ?
> I hear you say NO to this even though it is EXACTLY the same mechanism we need to provide install/rollbacks for the above - we just don't have that in place yet but that IS doable to do if we choose to do so and make it clear what is installed (see
> But if you cannot even agree to it by principle then any technical discussion is pointless.
> Thus can you give Yes/No answers to the above please ?
> My answers are:
> A) Yes
> B) Yes
> C) Yes
> ...all with the assumption we make it clear that once you do this you are running in "early access" mode.
> For me there is zero difference between A/B/C if done properly. And of course we should not do any of these blindly and without ensuring it is as smooth as possible but the mere definition of "early access" is : "You install this on your own risk - please don't expect things to work completely fine afterwards".
> {quote}



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)