[
https://issues.jboss.org/browse/JBDS-3093?page=com.atlassian.jira.plugin....
]
Nick Boldt commented on JBDS-3093:
----------------------------------
To achieve the option to "roll back" something between JBDS 9 and 9.x, we need,
simply, an update site with both the latest and previous versions on it.
We have in the past debated the performance impact of an update site which composites
8.0.0, 8.0.1, 8.1.0, etc. in the same site and it was decided IIRC NOT to do that because
of the performance hit for new users.
That said, if this issue is simply about having a composite site of old / current EARLY
ACCESS bits, we can totally do that with minimal performance hit for two reasons:
* EA is a tiny site, especially compared to the (JBDS + JBDS TP + JBDS Central) site
* EA is already subject to "this might break your machine" warnings, so making
it a bit slower to install/rollback shouldn't be a big deal IMHO.
So, if we want this for 9.x, we can add some instructions to the release guide for
JBT/JBDS/JBTIS/JBDSIS to clarify that new EA releases should simply be ADDED to the
/earlyaccess/ URLs, rather than replacing them.
OTOH, since this issue is over 1 year old, we could just close it as WONTFIX.
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)