[
https://issues.jboss.org/browse/JBDS-2745?page=com.atlassian.jira.plugin....
]
Nick Boldt commented on JBDS-2745:
----------------------------------
* Controlling what gets in is a human thing (ie., PRD/ERD/Requirements JIRAs w/ ACKs).
That won't change.
* Being able to provide updates from [EA/Exp/Inc] to [Final/GA] has always been possible,
though we never included the EA/Exp/Inc content before. Ability to update won't
change.
* Labelling how pre-GA content appears is simply a user interface thing (aka *eye candy*).
That WILL change.
* Providing automation & testing to verify content is properly labelled / versioned is
new.
Does that make it clear what we need to do?
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
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