[jbosstools-issues] [JBoss JIRA] (JBDS-2745) Support installation of Early Access / Experimental / Incubating plugins

[Nick Boldt (JIRA)]

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

Nick Boldt commented on JBDS-2745:
----------------------------------

First kick at new UI is here: https://vidd.me/v/OFH (ref: https://issues.jboss.org/browse/JBIDE-16375?focusedCommentId=12960580&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-12960580 )

Ultimately, it's been decided that in order to better compartmentalize these EA features into a completely self-contained (and therefore more easily grown/destroyed) target platform, we need:

a) a new EA target platform to complement the Central TP

b) 2 new EA discovery plugins - 1 for each of JBT and JBDS, to complement the existing JBT and JBDS discovery plugins - we might only need 1 of these for now if the content will be the same in both places, to save code duplication

c) a new entry in the jbosstools-directory.xml and devstudio-directory.xml files, pointing at the appropriate discovery plugin for the release, once the content is ready to be released into Central

d) new release guide / scripts to ensure that this new EA entry is NOT overwritten each time an update to the JBT/JBDS plugin version is performed (ie., sed script will need adjusting), and that when a new plugin or TP needs to be created/QE-staged/released, there's doc to cover those workflow steps

e) a pair of new jobs (1 per master/stable branch) to build the new target platform

f) a pair of new jobs (1 per master/stable branch) to build staging discovery sites so we have something we can pass to QE to test

g) to remove Arquillian and VJET from the existing Central TP, as they'll have moved to the EA TP and EA discovery plugin.xml

h) to once again update the list of certification names listed here: https://devstudio.jboss.com/updates/7.0/central/ to replace the existing "Experimental" type with the new "Early Access" type, or to add a 5th type to the list, if Experimental will continue to exist. [~maxandersen] [~burrsutter] WDYT?
                
> Support installation of Early Access / Experimental / Incubating plugins
> ------------------------------------------------------------------------
>
>                 Key: JBDS-2745
>                 URL: https://issues.jboss.org/browse/JBDS-2745
>             Project: Developer Studio (JBoss Developer Studio)
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: central, requirements
>    Affects Versions: 7.1.0.Alpha1
>            Reporter: Nick Boldt
>            Assignee: Burr Sutter
>              Labels: JBDS80_Approved_Scope
>             Fix For: 8.0.0.Beta2
>
>
> It's been suggested that it would be nice to have Central available to install non-GA content. How might this appear?
>  [~burrsutter], [~maxandersen], are we talking about:
> * an additional dialog warning users about untested content? (that might be ignored / blindclicked)
> * an additional tab in Central for this type of content (what label would you use?)
> * relabelling the content's feature descriptions / titles / copyright / license terms to be clear it's unstable content? (might be ignored)
> * some other workflow?
> See also JBDS-2068.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira