Mailing Lists
| Topic | List address | Archive |
|---|---|---|
| User questions and deployment support | user@ambari.apache.org | User archive |
| Development and design discussion | dev@ambari.apache.org | Dev archive |
| JIRA issue discussion | issues@ambari.apache.org | Issues archive |
| Code review discussion | reviews@ambari.apache.org | Reviews archive |
| Commit notifications | commits@ambari.apache.org | Commits archive |
Ask A Useful Question
Use user@ambari.apache.org for installation and operation questions. Include
the candidate revision, operating system and architecture, separate Ambari and
Stack JDK choices, Python version and ABI, relevant logs, and the exact command
that failed. Before sending, remove passwords, access tokens, certificates,
private keys, internal hostnames, and other environment-specific secrets.
Use dev@ambari.apache.org for patches, API or behavior design, and source
build questions. After checking existing JIRA issues, send reproducible defects
to issues@ambari.apache.org. Put code-review requests and review feedback on
reviews@ambari.apache.org; commit traffic is delivered automatically to
commits@ambari.apache.org.
Search the archives first, use a subject that identifies the problem, and link to the relevant JIRA or code review. These lists provide a traceable record of community discussion; they do not replace release qualification, security policy, or environment testing. Public list traffic is not an incident-response channel. Follow the project's documented private reporting process for unreleased security vulnerabilities.