Mailing-List: contact commits-help@airflow.incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@airflow.incubator.apache.org
Date: Wed, 27 Apr 2016 19:31:12 +0000 (UTC)
From: "Siddharth Anand (JIRA)" <jira@apache.org>
To: commits@airflow.incubator.apache.org
Message-ID: <JIRA.12963250.1461782412000.50833.1461785472932@Atlassian.JIRA>
In-Reply-To: <JIRA.12963250.1461782412000@Atlassian.JIRA>
References: <JIRA.12963250.1461782412000@Atlassian.JIRA>
 <JIRA.12963250.1461782412982@arcas>
Subject: [jira] [Comment Edited] (AIRFLOW-11) Migrate mailing list to Apache
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/AIRFLOW-11?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15260752#comment-15260752 ] 

Siddharth Anand edited comment on AIRFLOW-11 at 4/27/16 7:30 PM:
-----------------------------------------------------------------

How does this look as a draft?

{noformat}
Hey all,

As some of you already know, we're in the process of moving Airflow into the Apache incubator. This will involve a number of infrastructure and process changes. These changes will include:

1) Migration of airbnb/airflow code base to Apache's Git repository.
2) Migration of Google groups mailing list (this list) to Apache developer list.
3) Migration of Travis CI to use the Apache Git repository.
4) Migration of GitHub wiki to Apache Confluence wiki.
5) Migration of GitHub Issues to Apache Jira.

We are currently planning to do this migration over the next week, to finish on May 4, 2016.

What you should do:

* Sign up for the Apache dev and commit mailing lists (send emails to dev-subscribe@airflow.incubator.apache.org and commit-subscribe@airflow.incubator.apache.org)
* Sign up for an Apache JIRA account and re-open any issues that you care about in the Apache Airflow JIRA project (https://issues.apache.org/jira/browse/AIRFLOW)
* Sign up for an Apache Confluence account (https://cwiki.apache.org/confluence/display/AIRFLOW)
* Update any forks to point to the Apache GitHub repository (https://github.com/apache/incubator-airflow)
* Re-open any issues that you care about in the Apache Airflow JIRA project (https://issues.apache.org/jira/browse/AIRFLOW)

This Google group will go read-only on May 4, 2016.

Once the code migration happens, you should continue to use GitHub pull requests, as usual, but you must include an Apache JIRA number in the title with the format 'AIRFLOW-XXX: title of issue'. This will allow pull requests to get synced with the Apache JIRA. This will be required. We will publish a more detailed "how to send pull requests" note on the wiki shortly.

Cheers,
Chris
{noformat}


was (Author: criccomini):
How does this look as a draft?

{noformat}
Hey all,

As some of you already know, we're in the process of moving Airflow into the Apache incubator. This will involve a number of infrastructure and process changes. These changes will include:

1) Migration of airbnb/airflow code base to Apache's Git repository.
2) Migration of Google groups mailing list (this list) to Apache developer list.
3) Migration of Travis CI to use the Apache Git repository.
4) Migration of GitHub wiki to Apache Confluence wiki.
5) Migration of GitHub Issues to Apache Jira.

We are currently planning to do this migration over the next week, to finish on May 4, 2016.

What you should do:

* Sign up for the Apache mailing list (send an email to dev-subscribe@airflow.incubator.apache.org)
* Sign up for an Apache JIRA account and re-open any issues that you care about in the Apache Airflow JIRA project (https://issues.apache.org/jira/browse/AIRFLOW)
* Sign up for an Apache Confluence account (https://cwiki.apache.org/confluence/display/AIRFLOW)
* Update any forks to point to the Apache GitHub repository (https://github.com/apache/incubator-airflow)
* Re-open any issues that you care about in the Apache Airflow JIRA project (https://issues.apache.org/jira/browse/AIRFLOW)

This Google group will go read-only on May 4, 2016.

Once the code migration happens, you should continue to use GitHub pull requests, as usual, but you must include an Apache JIRA number in the title with the format 'AIRFLOW-XXX: title of issue'. This will allow pull requests to get synced with the Apache JIRA. This will be required. We will publish a more detailed "how to send pull requests" note on the wiki shortly.

Cheers,
Chris
{noformat}

> Migrate mailing list to Apache
> ------------------------------
>
>                 Key: AIRFLOW-11
>                 URL: https://issues.apache.org/jira/browse/AIRFLOW-11
>             Project: Apache Airflow
>          Issue Type: Bug
>            Reporter: Chris Riccomini
>            Assignee: Chris Riccomini
>


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)