Uploaded image for project: 'Tools (JBoss Tools)'
  1. Tools (JBoss Tools)
  2. JBIDE-17808

Identify which installed IUs are from Early Access vs. supported/tested versions

    XMLWordPrintable

Details

    Description

      manderse@redhat.com brought up a good point on a call today:

      we have no way from within JBDS of identifying which installed IUs were installed from Early Access vs. those what were installed from Central or another "supported" location.

      Thus we need some sort of UI to list installed IUs that are "Early Access".

      This could be... (brainstorming now):

      • a text file with the list of things installed from Early Access (features and plugins)
      • a set of asterisks added to the Help > About dialogs when browsing for installed features / plugins
      • a way to filter the plugin view (Help > About) to show only EA content (or exclude it)
      • ... ?

      Attachments

        Issue Links

          blocks

          Sub-task - The sub-task of the issue JBIDE-18165 For JBIDE 4.2.0.CR1: Code Freeze + Branch [Central]

          • Blocker - To be worked above all other priorities. This term is chosen when the severity of the issue is very high, has no workaround, or the effort for the change is comparatively low. Issues that may be very publicly visible and could generate significant media attention may also drive a higher priority.
          • Closed
          is related to

          Feature Request - Feature requests from customers and/or users JBDS-2745 Support installation of Early Access / Experimental / Incubating plugins

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Enhancement - An enhancement to or refactoring of existing functionality that is not configurable by an end user (typically a change made by an internal team that affects users) JBDS-3085 Should we be able to update JBDS 8.0.0.GA ("Branded Product") -> 8.1.0.Alpha1 via Early Access?

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Enhancement - An enhancement to or refactoring of existing functionality that is not configurable by an end user (typically a change made by an internal team that affects users) JBDS-3093 Should we allow users to install updates to individual JBDS features (not the whole product) via Early Access?

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Enhancement - An enhancement to or refactoring of existing functionality that is not configurable by an end user (typically a change made by an internal team that affects users) JBIDE-18001 Consider using a more pale shade of yellow to identify Early Access content in JBoss Central

          • Minor - To be worked after urgent, high, and medium priorities are resolved. This term is chosen when the severity of the issue is low, or the complexity or effort to correct it may be higher, relatively speaking. For low priority issues, known workarounds exist or are not needed due to the trivial effort needed to address the issue.
          • Closed

          Enhancement - An enhancement to or refactoring of existing functionality that is not configurable by an end user (typically a change made by an internal team that affects users) JBIDE-18217 Central editor asynchrnously call InstallationChecker

          • Minor - To be worked after urgent, high, and medium priorities are resolved. This term is chosen when the severity of the issue is low, or the complexity or effort to correct it may be higher, relatively speaking. For low priority issues, known workarounds exist or are not needed due to the trivial effort needed to address the issue.
          • Closed

          Activity

            People

              mistria@redhat.com Mickael Istria
              nickboldt Nick Boldt
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: