Overview
We received feedback that our current mailing list is difficult to read and follow up on some issues. This document suggests a new scheme for mailing lists.
Goal
Each mailing has one or a similar purpose.
As-is
Name | Purpose | Note |
---|
users@zeppelin.apache.org | Issues and discussions for users |
|
dev@zeppelin.apache.org | Issues and discussions for developers, GitHub activities, and Jira activities | Mixed with different contexts and purpose |
commits@zeppelin.apache.org | Commits submitted to the master branch |
|
To-be
Name | Purpose | Note |
---|
users@zeppelin.apache.org | Issues and discussions for users |
|
dev@zeppelin.apache.org | Issues and discussions for developers, Jira creation/resolution | Similar to Kafka's dev style |
commits@zeppelin.apache.org | Commits submitted to the master branch |
|
reviews@zeppelin.apache.org | GitHub activities, Jira activities | Similar to Kafka's dev style |
Changes
Code Block |
---|
language | yml |
---|
title | .asf.yaml |
---|
linenumbers | true |
---|
|
notifications:
commits: commits@kafkacommits@zeppelin.apache.org
issues: jira@kafkareviews@zeppelin.apache.org
pullrequests: jira@kafkareviews@zeppelin.apache.org
jira_options: link label
|