[
https://issues.jboss.org/browse/JBTIS-358?page=com.atlassian.jira.plugin....
]
Nick Boldt commented on JBTIS-358:
----------------------------------
Part of the reason I thought we were moving to fewer Marketplace entries for IS was
because we were ALSO moving to having fewer installers. Seemed logical that we wanted less
entry points [1 installer, 1 marketplace entry] for the first rollout, as that would
simplify both the QE experience and also that of the user.
And I also assumed that we'd want one marketplace entry for JBTIS with all the
individual features (like we do for JBT), then one marketplace entry for JBDS IS, with all
the individual products (like we do for JBDS, with its single product).
TL;DR: I assumed we wanted a parallel release process for JBTIS/JBDSIS as for JBT/JBDS so
that we could have a similar user experience for both community and product.
Aside: what are discovery centrals? Max, sometimes your clarifications need clarification.
:)
Use wrapper features to simplify the install and clean up the
Marketplace UI?
-----------------------------------------------------------------------------
Key: JBTIS-358
URL:
https://issues.jboss.org/browse/JBTIS-358
Project: JBoss Tools Integration Stack
Issue Type: Bug
Components: distribution
Affects Versions: 7.0.3.GA
Reporter: Nick Boldt
Fix For: 7.1.0.GA-JBDSIS
Attachments: is-marketplace1.png, is-marketplace2.png
For 7.1.0, could consider having wrapper features to simplify the install and clean up
the Marketplace UI. Doing so would mean instead of a laundry list of features in the UI,
we could list only 3 features.
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)