Re: Github Issue Triaging

2022-10-18 Thread Ferruzzi, Dennis
Invite received and accepted, thanks! I promise to use this power mostly for good. :P From: Kaxil Naik Sent: Tuesday, October 18, 2022 11:05 AM To: dev@airflow.apache.org Subject: RE: [EXTERNAL]Github Issue Triaging CAUTION: This email originated from

Re: Github Issue Triaging

2022-10-18 Thread Kaxil Naik
ast but without being able to add the tags >>> myself, it felt silly just tagging someone else to add the tags. >>> >>> >>> -- >>> *From:* Elad Kalif >>> *Sent:* Tuesday, October 11, 2022 11:50 PM >&g

Re: Github Issue Triaging

2022-10-18 Thread Jeambrun Pierre
- >> *From:* Elad Kalif >> *Sent:* Tuesday, October 11, 2022 11:50 PM >> *To:* dev@airflow.apache.org >> *Subject:* RE: [EXTERNAL]Github Issue Triaging >> >> >> *CAUTION*: This email originated from outside of the organization. Do >> no

Re: Github Issue Triaging

2022-10-18 Thread Kaxil Naik
se to add the tags. > > > -- > *From:* Elad Kalif > *Sent:* Tuesday, October 11, 2022 11:50 PM > *To:* dev@airflow.apache.org > *Subject:* RE: [EXTERNAL]Github Issue Triaging > > > *CAUTION*: This email originated from outside of the org

Re: Github Issue Triaging

2022-10-17 Thread Ferruzzi, Dennis
11:50 PM To: dev@airflow.apache.org Subject: RE: [EXTERNAL]Github Issue Triaging CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you can confirm the sender and know the content is safe. It seems that we don't need Infra: https

Re: Github Issue Triaging

2022-10-12 Thread Elad Kalif
ppreciate the support Kaxil. > > Cheers, > Niko > > > -- > *From:* Kaxil Naik > *Sent:* Wednesday, October 5, 2022 10:16 AM > *To:* dev@airflow.apache.org > *Subject:* RE: [EXTERNAL]Github Issue Triaging > > > *CAUTION*: This email

Re: Github Issue Triaging

2022-10-05 Thread Oliveira, Niko
. Cheers, Niko From: Kaxil Naik Sent: Wednesday, October 5, 2022 10:16 AM To: dev@airflow.apache.org Subject: RE: [EXTERNAL]Github Issue Triaging CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you ca

Re: Github Issue Triaging

2022-10-05 Thread Jarek Potiuk
>> Niko >> -- >> *From:* Elad Kalif >> *Sent:* Wednesday, October 5, 2022 9:01:22 AM >> *To:* dev@airflow.apache.org >> *Subject:* RE: [EXTERNAL]Github Issue Triaging >> >> >> *CAUTION*: This email originated from outside of the org

Re: Github Issue Triaging

2022-10-05 Thread Kaxil Naik
is my request to be added to the airflow-triage Team! > > Cheers, > Niko > -- > *From:* Elad Kalif > *Sent:* Wednesday, October 5, 2022 9:01:22 AM > *To:* dev@airflow.apache.org > *Subject:* RE: [EXTERNAL]Github Issue Triaging > > &

Re: Github Issue Triaging

2022-10-05 Thread Oliveira, Niko
From: Elad Kalif Sent: Wednesday, October 5, 2022 9:01:22 AM To: dev@airflow.apache.org Subject: RE: [EXTERNAL]Github Issue Triaging CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you can confirm the sender

Re: Github Issue Triaging

2022-10-05 Thread Elad Kalif
The backlog is actually in good shape. Most of the open issues just need attention from a knowledgeable contributor in the specific area to add some pointers if the issue is valid or not. The protocol for triage can be found in: https://github.com/apache/airflow/blob/main/ISSUE_TRIAGE_PROCESS.rst

Github Issue Triaging

2022-10-05 Thread Oliveira, Niko
Hello folks, Yesterday I attended a session at ApacheCon about best practices for managing bug/issue backlogs for a project and it got me reflecting on the Airflow issue backlog. I'd like to get more involved in initial (and continuous) triage of Airflow issues on Github. I chatted with Jarek