[jbosstools-issues] [JBoss JIRA] (JBDS-3276) JBDS-IS Installer support

[Paul Leacu (JIRA)]

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

Paul Leacu edited comment on JBDS-3276 at 11/19/15 9:19 AM:
------------------------------------------------------------

Greetings all watchers...
[~maxandersen] [~ldimaggio] [~nickboldt] [~dgolovin] [~crobson] [~ganandan-Redhat] [~mhusnain] [~akazakov]
What do we collectively want to do with this Jira from here?  The prototype JBDSIS standalone installer works well and does facilitate the installation of integration stack tooling (like Fuse Tooling or Teiid Designer).   The latest user experience testing has shown that the latest batch of users didn't find the
existing install scenario that different from using the standalone installer.  (They had more issues with quickstarts, etc than with the actual IS installation).
That being said - it does make things easier so I would say lets go with it.  If we reach consensus on that then the following question need to be answered.

1.  Should we have 2 standalone installers (one for JBDS and one for JBDSIS) or just 1?
     My opinion is that we stay with 2.  The JBDSIS installer is a superset of the JBDS installer and allows users to pick what they want.  Also - given the
     asynchronous release schedule of JBDS and JBDSIS (even if we try to sync as close as possible) - the JBDSIS installer still must be built from the IS
     devstudio POM.  We don't want the situation of the IS components appearing, disappearing and then appearing again.  I think the doc/ QE impact is
     manageable.
2.  Should we restrict the JBDSIS component content to released plugins only or can it have early access content?
     My opinion is that we stay with released content only.  In theory if the installer was made available from a clearly marked EA URL then it's no different
     than the user selecting 'Enable Early Access' - but it's probably safer to restrict the content to released IS components.
3.  There are no blocker issues with this.  I can create a separate Jira for the second screen-shot issue above (minor).  The first has been addressed.

WDYT



was (Author: pleacu):
Greetings all watchers...

What do we collectively want to do with this Jira from here?  The prototype JBDSIS standalone installer works well and does facilitate the installation of integration stack tooling (like Fuse Tooling or Teiid Designer).   The latest user experience testing has shown that the latest batch of users didn't find the
existing install scenario that different from using the standalone installer.  (They had more issues with quickstarts, etc than with the actual IS installation).
That being said - it does make things easier so I would say lets go with it.  If we reach consensus on that then the following question need to be answered.

1.  Should we have 2 standalone installers (one for JBDS and one for JBDSIS) or just 1?
     My opinion is that we stay with 2.  The JBDSIS installer is a superset of the JBDS installer and allows users to pick what they want.  Also - given the
     asynchronous release schedule of JBDS and JBDSIS (even if we try to sync as close as possible) - the JBDSIS installer still must be built from the IS
     devstudio POM.  We don't want the situation of the IS components appearing, disappearing and then appearing again.  I think the doc/ QE impact is
     manageable.
2.  Should we restrict the JBDSIS component content to released plugins only or can it have early access content?
     My opinion is that we stay with released content only.  In theory if the installer was made available from a clearly marked EA URL then it's no different
     than the user selecting 'Enable Early Access' - but it's probably safer to restrict the content to released IS components.
3.  There are no blocker issues with this.  I can create a separate Jira for the second screen-shot issue above (minor).  The first has been addressed.

WDYT


> JBDS-IS Installer support
> -------------------------
>
>                 Key: JBDS-3276
>                 URL: https://issues.jboss.org/browse/JBDS-3276
>             Project: Developer Studio (JBoss Developer Studio)
>          Issue Type: Feature Request
>          Components: installer, integration-platform, requirements
>    Affects Versions: 8.0.0.GA
>            Reporter: Burr Sutter
>            Assignee: Paul Leacu
>             Fix For: 9.1.0.Beta1
>
>         Attachments:  Red Hat JBoss Developer Studio 9.0.0.Alpha2_105.png, EA.png, jbds-is-about.png, JBDSIS_installer_9.png, JBDSIS_installer_space.png, mirroringlog.txt, sai1.png
>
>
> As a Fuse, integration-focused developer, I need a downloadable installer that will allow me to quickly and easily install JBDS with Fuse capabilities.



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