Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

The following page describes proposed changes to the Apache Ambari JIRA to better help categorize and organize JIRAs around components for tasks, bugs and improvements across the core project + contributions.

Components

agentshell"
CurrentProposed RenameDescriptionAction
alertsJIRAs related to Ambari Alerts system.
ambari-adminNew component specifically for Ambari Admin.
ambari-agentJIRAs related to the Ambari Agent.Rename this component from "agent" to "ambari-agent"
Ambari-SCOMcontribJIRAs related to contributions under "contrib", such as Ambari SCOM
  • Rename this component from "Ambari-SCOM" to "contrib"
  • Use a label with "contrib" component to categorize Ambari SCOM specific JIRAs.
    buildinfraJIRAs related to project infrastructure including builds, releases mechanics and automationRename this component from "build" to "infra"
    clientambari-clientJIRAs related to the Ambari Client.Rename this component from "client" to "ambari-client" 
    ambari-webNew component specifically for Ambari Web.
    • Create new component "ambari-web"
    metricsJIRAs related to Ambari Metrics system.
    ambari-controllerambari-serverJIRAs related to the Ambari Server.
    • Rename this component from "controller" to "ambari-server"
     
    ambari-shellNew component specifically for Ambari Shell.Create new component "
    ambari-web ambari-adminNew component specifically for Ambari Admin.
    • Create new component "ambari-admin"
    documentation<no change>JIRAs related to project documentation including the wiki. 
    site<no change>JIRAs related to the project site http://ambari.apache.org/ 
    stackstacksJIRAs related to Ambari Stacks.
    • Rename this component from "stack" to "stacks"
    • Use a label with "stacks" component to categorize stack-specific JIRAs, such as HDP.
    test<remove> 
    • Remove this component
    • Move all JIRAs into "infra" component
    Web.
    viewsambari-viewsJIRAs related to the Ambari Views framework. Specific Views that are built on the framework will be handled with labels.
  • Rename this component from "views" to "ambari-views"
  • Use a label with "ambari-views" component to categorize stack-specific JIRAs, such as "files" or "slider".
     blueprintsJIRAs related to Ambari Blueprints.
    • Create new component "blueprints"
     
    documentationJIRAs related to project documentation including the wiki.
    securityalertsJIRAs related to Ambari Alerts systemsecurity features, including Kerberos.
    siteJIRAs related to the project site http://ambari.apache.org/
    stacks
    • Create new component "alerts"
     metricsJIRAs related to Ambari Metrics systemStacks.
    • Create new component "metrics"
     
    securitytestJIRAs related to Ambari security features, including Kerberos.
    • Create new component "security"
    unit tests and test automation

    Use of Labels

    In certain cases, the component listed above is might be "too broad" and you want to designate JIRAs to a specific area of that component. To handle these scenarios, we propose use a combination of component + labels. Some examples:

    ...