You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@airflow.apache.org by Ash Berlin-Taylor <as...@apache.org> on 2020/03/16 14:36:25 UTC
[VOTE] Switch from using Jira to Github Issues
The original discuss thread is here. https://lists.apache.org/thread.html/r19014fac5aa2aa15a86890aa438940da263e430cb535ca451ef451a4%40%3Cdev.airflow.apache.org%3E
Proposal is:
- We create a few appropriate issue templates in ./github -- specifically also one for "Ask for help" that basically says "Don't ask here, this will be closed".
- We ask Infra to enable Github Issues on our apache/airflow repo
- We remove the requirement on code changes to need an accompanying Jira ticket (and we don't replace it with needing a Github Issue either)
- We use Github Milestones to target which PRs should be backported to release branches.
- We update/port the dev/airflow_jira script from looking at FixVersion in Jira to look instead at the Milestone.
- We (committers/interested parties) start reviewing the open Jira issues, manually migrate the ones we think are still relevant to Github Issues, leave a link (Add Link, not just a comment) on the Jira Issue, and close it with status "Auto Closed"(?). We could also add a "migrated-to-github" label to migrated issues.
- After the review is done we bulk-comment on any remaining open issue saying "We are migrating to Github, and believe this issue is no longer relevant. If you think otherwise please create an issue at <url>".
- Ask Infra to disable creating new Jira issues for the AIRFLOW project.
There is a bit of a "contention/locking" issue about the migration -- how to avoid creating duplicate issues. Not the end of the world if we do I guess.
This vote will last for 72 hours, ending 2020-03-19T14:35:00Z, and until 3 +1 votes are cast.
This is my binding +1 vote.
Thanks,
ash
Re: [VOTE] Switch from using Jira to Github Issues
Posted by Robin Edwards <ro...@bidnamic.com>.
woohoo!
+1 none binding
On Wed, 18 Mar 2020, 08:36 Michał Słowikowski, <
michal.slowikowski@polidea.com> wrote:
> +1 (non-binding)
>
> On Tue, Mar 17, 2020 at 10:13 PM Sid Anand <sa...@apache.org> wrote:
>
> > (resending from my apache account .. sorry)
> >
> > +1 Binding
> >
> > Airflow's returning full-circle to Github issues after 4 years :-)
> > -s
> >
> > On Tue, Mar 17, 2020 at 2:12 PM Sid Anand <r3...@gmail.com> wrote:
> >
> > > +1 Binding
> > >
> > > Airflow's returning full-circle to Github issues after 4 years :-)
> > >
> > > -s
> > >
> > > On Tue, Mar 17, 2020 at 6:48 AM Daniel Imberman <
> > daniel.imberman@gmail.com>
> > > wrote:
> > >
> > >> +1 Binding
> > >>
> > >> No point in having a whole extra site if we’re not using any of the
> JIRA
> > >> specific features
> > >>
> > >> Daniel
> > >> On Mar 16, 2020, 9:58 PM -0700, Sumit Maheshwari <
> > sumeet.manit@gmail.com>,
> > >> wrote:
> > >> > +1 binding
> > >> >
> > >> > On Mon, Mar 16, 2020 at 11:44 PM Kevin Yang <yr...@gmail.com>
> > wrote:
> > >> >
> > >> > > +1 binding
> > >> > >
> > >> > > On Mon, Mar 16, 2020 at 9:34 AM Tao Feng <fe...@gmail.com>
> > wrote:
> > >> > >
> > >> > > > +1
> > >> > > >
> > >> > > > On Mon, Mar 16, 2020 at 7:36 AM Ash Berlin-Taylor <
> ash@apache.org
> > >
> > >> > > wrote:
> > >> > > >
> > >> > > > > The original discuss thread is here.
> > >> > > > >
> > >> > > >
> > >> > >
> > >>
> >
> https://lists.apache.org/thread.html/r19014fac5aa2aa15a86890aa438940da263e430cb535ca451ef451a4%40%3Cdev.airflow.apache.org%3E
> > >> > > > >
> > >> > > > > Proposal is:
> > >> > > > >
> > >> > > > > - We create a few appropriate issue templates in ./github --
> > >> > > > specifically
> > >> > > > > also one for "Ask for help" that basically says "Don't ask
> here,
> > >> this
> > >> > > > will
> > >> > > > > be closed".
> > >> > > > > - We ask Infra to enable Github Issues on our apache/airflow
> > repo
> > >> > > > > - We remove the requirement on code changes to need an
> > >> accompanying
> > >> > > Jira
> > >> > > > > ticket (and we don't replace it with needing a Github Issue
> > >> either)
> > >> > > > > - We use Github Milestones to target which PRs should be
> > >> backported to
> > >> > > > > release branches.
> > >> > > > > - We update/port the dev/airflow_jira script from looking at
> > >> FixVersion
> > >> > > > in
> > >> > > > > Jira to look instead at the Milestone.
> > >> > > > > - We (committers/interested parties) start reviewing the open
> > Jira
> > >> > > > issues,
> > >> > > > > manually migrate the ones we think are still relevant to
> Github
> > >> Issues,
> > >> > > > > leave a link (Add Link, not just a comment) on the Jira Issue,
> > and
> > >> > > close
> > >> > > > it
> > >> > > > > with status "Auto Closed"(?). We could also add a
> > >> "migrated-to-github"
> > >> > > > > label to migrated issues.
> > >> > > > > - After the review is done we bulk-comment on any remaining
> open
> > >> issue
> > >> > > > > saying "We are migrating to Github, and believe this issue is
> no
> > >> longer
> > >> > > > > relevant. If you think otherwise please create an issue at
> > <url>".
> > >> > > > > - Ask Infra to disable creating new Jira issues for the
> AIRFLOW
> > >> > > project.
> > >> > > > >
> > >> > > > > There is a bit of a "contention/locking" issue about the
> > >> migration --
> > >> > > how
> > >> > > > > to avoid creating duplicate issues. Not the end of the world
> if
> > >> we do I
> > >> > > > > guess.
> > >> > > > >
> > >> > > > > This vote will last for 72 hours, ending 2020-03-19T14:35:00Z,
> > and
> > >> > > until
> > >> > > > 3
> > >> > > > > +1 votes are cast.
> > >> > > > >
> > >> > > > > This is my binding +1 vote.
> > >> > > > >
> > >> > > > > Thanks,
> > >> > > > > ash
> > >> > > > >
> > >> > > > >
> > >> > > >
> > >> > >
> > >>
> > >
> >
>
>
> --
>
> Michał Słowikowski
> Polidea <https://www.polidea.com/> | Junior Software Engineer
>
> E: michal.slowikowski@polidea.com
>
> Unique Tech
> Check out our projects! <https://www.polidea.com/our-work>
>
Re: [VOTE] Switch from using Jira to Github Issues
Posted by Michał Słowikowski <mi...@polidea.com>.
+1 (non-binding)
On Tue, Mar 17, 2020 at 10:13 PM Sid Anand <sa...@apache.org> wrote:
> (resending from my apache account .. sorry)
>
> +1 Binding
>
> Airflow's returning full-circle to Github issues after 4 years :-)
> -s
>
> On Tue, Mar 17, 2020 at 2:12 PM Sid Anand <r3...@gmail.com> wrote:
>
> > +1 Binding
> >
> > Airflow's returning full-circle to Github issues after 4 years :-)
> >
> > -s
> >
> > On Tue, Mar 17, 2020 at 6:48 AM Daniel Imberman <
> daniel.imberman@gmail.com>
> > wrote:
> >
> >> +1 Binding
> >>
> >> No point in having a whole extra site if we’re not using any of the JIRA
> >> specific features
> >>
> >> Daniel
> >> On Mar 16, 2020, 9:58 PM -0700, Sumit Maheshwari <
> sumeet.manit@gmail.com>,
> >> wrote:
> >> > +1 binding
> >> >
> >> > On Mon, Mar 16, 2020 at 11:44 PM Kevin Yang <yr...@gmail.com>
> wrote:
> >> >
> >> > > +1 binding
> >> > >
> >> > > On Mon, Mar 16, 2020 at 9:34 AM Tao Feng <fe...@gmail.com>
> wrote:
> >> > >
> >> > > > +1
> >> > > >
> >> > > > On Mon, Mar 16, 2020 at 7:36 AM Ash Berlin-Taylor <ash@apache.org
> >
> >> > > wrote:
> >> > > >
> >> > > > > The original discuss thread is here.
> >> > > > >
> >> > > >
> >> > >
> >>
> https://lists.apache.org/thread.html/r19014fac5aa2aa15a86890aa438940da263e430cb535ca451ef451a4%40%3Cdev.airflow.apache.org%3E
> >> > > > >
> >> > > > > Proposal is:
> >> > > > >
> >> > > > > - We create a few appropriate issue templates in ./github --
> >> > > > specifically
> >> > > > > also one for "Ask for help" that basically says "Don't ask here,
> >> this
> >> > > > will
> >> > > > > be closed".
> >> > > > > - We ask Infra to enable Github Issues on our apache/airflow
> repo
> >> > > > > - We remove the requirement on code changes to need an
> >> accompanying
> >> > > Jira
> >> > > > > ticket (and we don't replace it with needing a Github Issue
> >> either)
> >> > > > > - We use Github Milestones to target which PRs should be
> >> backported to
> >> > > > > release branches.
> >> > > > > - We update/port the dev/airflow_jira script from looking at
> >> FixVersion
> >> > > > in
> >> > > > > Jira to look instead at the Milestone.
> >> > > > > - We (committers/interested parties) start reviewing the open
> Jira
> >> > > > issues,
> >> > > > > manually migrate the ones we think are still relevant to Github
> >> Issues,
> >> > > > > leave a link (Add Link, not just a comment) on the Jira Issue,
> and
> >> > > close
> >> > > > it
> >> > > > > with status "Auto Closed"(?). We could also add a
> >> "migrated-to-github"
> >> > > > > label to migrated issues.
> >> > > > > - After the review is done we bulk-comment on any remaining open
> >> issue
> >> > > > > saying "We are migrating to Github, and believe this issue is no
> >> longer
> >> > > > > relevant. If you think otherwise please create an issue at
> <url>".
> >> > > > > - Ask Infra to disable creating new Jira issues for the AIRFLOW
> >> > > project.
> >> > > > >
> >> > > > > There is a bit of a "contention/locking" issue about the
> >> migration --
> >> > > how
> >> > > > > to avoid creating duplicate issues. Not the end of the world if
> >> we do I
> >> > > > > guess.
> >> > > > >
> >> > > > > This vote will last for 72 hours, ending 2020-03-19T14:35:00Z,
> and
> >> > > until
> >> > > > 3
> >> > > > > +1 votes are cast.
> >> > > > >
> >> > > > > This is my binding +1 vote.
> >> > > > >
> >> > > > > Thanks,
> >> > > > > ash
> >> > > > >
> >> > > > >
> >> > > >
> >> > >
> >>
> >
>
--
Michał Słowikowski
Polidea <https://www.polidea.com/> | Junior Software Engineer
E: michal.slowikowski@polidea.com
Unique Tech
Check out our projects! <https://www.polidea.com/our-work>
[RESULT] [VOTE] Switch from using Jira to Github Issues
Posted by Ash Berlin-Taylor <as...@apache.org>.
This vote has passed with 12 +1 votes and 0 -1 votes.
Yay!
Daniel has already started updating the PR template and checks :)
https://github.com/apache/airflow/pull/7771/files
-ash
On Tue Mar 17, 2020 at 2:13 PM, Sid Anand wrote:
> (resending from my apache account .. sorry)
>
>
> +1 Binding
>
>
> Airflow's returning full-circle to Github issues after 4 years :-)
> -s
>
>
> On Tue, Mar 17, 2020 at 2:12 PM Sid Anand <r3...@gmail.com> wrote:
>
>
> > +1 Binding
> >
> > Airflow's returning full-circle to Github issues after 4 years :-)
> >
> > -s
> >
> > On Tue, Mar 17, 2020 at 6:48 AM Daniel Imberman <daniel.imberman@gmail.co=
> m>
> > wrote:
> >
> >> +1 Binding
> >>
> >> No point in having a whole extra site if we=E2=80=99re not using any of =
> the JIRA
> >> specific features
> >>
> >> Daniel
> >> On Mar 16, 2020, 9:58 PM -0700, Sumit Maheshwari <sumeet.manit@gmail.com=
> >,
> >> wrote:
> >> > +1 binding
> >> >
> >> > On Mon, Mar 16, 2020 at 11:44 PM Kevin Yang <yr...@gmail.com> wrote:
> >> >
> >> > > +1 binding
> >> > >
> >> > > On Mon, Mar 16, 2020 at 9:34 AM Tao Feng <fe...@gmail.com> wrote=
> :
> >> > >
> >> > > > +1
> >> > > >
> >> > > > On Mon, Mar 16, 2020 at 7:36 AM Ash Berlin-Taylor <as...@apache.org>
> >> > > wrote:
> >> > > >
> >> > > > > The original discuss thread is here.
> >> > > > >
> >> > > >
> >> > >
> >> https://lists.apache.org/thread.html/r19014fac5aa2aa15a86890aa438940da26=
> 3e430cb535ca451ef451a4%40%3Cdev.airflow.apache.org%3E
> >> > > > >
> >> > > > > Proposal is:
> >> > > > >
> >> > > > > - We create a few appropriate issue templates in ./github --
> >> > > > specifically
> >> > > > > also one for "Ask for help" that basically says "Don't ask here,
> >> this
> >> > > > will
> >> > > > > be closed".
> >> > > > > - We ask Infra to enable Github Issues on our apache/airflow rep=
> o
> >> > > > > - We remove the requirement on code changes to need an
> >> accompanying
> >> > > Jira
> >> > > > > ticket (and we don't replace it with needing a Github Issue
> >> either)
> >> > > > > - We use Github Milestones to target which PRs should be
> >> backported to
> >> > > > > release branches.
> >> > > > > - We update/port the dev/airflow_jira script from looking at
> >> FixVersion
> >> > > > in
> >> > > > > Jira to look instead at the Milestone.
> >> > > > > - We (committers/interested parties) start reviewing the open Ji=
> ra
> >> > > > issues,
> >> > > > > manually migrate the ones we think are still relevant to Github
> >> Issues,
> >> > > > > leave a link (Add Link, not just a comment) on the Jira Issue, a=
> nd
> >> > > close
> >> > > > it
> >> > > > > with status "Auto Closed"(?). We could also add a
> >> "migrated-to-github"
> >> > > > > label to migrated issues.
> >> > > > > - After the review is done we bulk-comment on any remaining open
> >> issue
> >> > > > > saying "We are migrating to Github, and believe this issue is no
> >> longer
> >> > > > > relevant. If you think otherwise please create an issue at <url>=
> ".
> >> > > > > - Ask Infra to disable creating new Jira issues for the AIRFLOW
> >> > > project.
> >> > > > >
> >> > > > > There is a bit of a "contention/locking" issue about the
> >> migration --
> >> > > how
> >> > > > > to avoid creating duplicate issues. Not the end of the world if
> >> we do I
> >> > > > > guess.
> >> > > > >
> >> > > > > This vote will last for 72 hours, ending 2020-03-19T14:35:00Z, a=
> nd
> >> > > until
> >> > > > 3
> >> > > > > +1 votes are cast.
> >> > > > >
> >> > > > > This is my binding +1 vote.
> >> > > > >
> >> > > > > Thanks,
> >> > > > > ash
> >> > > > >
> >> > > > >
> >> > > >
> >> > >
> >>
> >
>
>
>
>
Re: [VOTE] Switch from using Jira to Github Issues
Posted by Sid Anand <sa...@apache.org>.
(resending from my apache account .. sorry)
+1 Binding
Airflow's returning full-circle to Github issues after 4 years :-)
-s
On Tue, Mar 17, 2020 at 2:12 PM Sid Anand <r3...@gmail.com> wrote:
> +1 Binding
>
> Airflow's returning full-circle to Github issues after 4 years :-)
>
> -s
>
> On Tue, Mar 17, 2020 at 6:48 AM Daniel Imberman <da...@gmail.com>
> wrote:
>
>> +1 Binding
>>
>> No point in having a whole extra site if we’re not using any of the JIRA
>> specific features
>>
>> Daniel
>> On Mar 16, 2020, 9:58 PM -0700, Sumit Maheshwari <su...@gmail.com>,
>> wrote:
>> > +1 binding
>> >
>> > On Mon, Mar 16, 2020 at 11:44 PM Kevin Yang <yr...@gmail.com> wrote:
>> >
>> > > +1 binding
>> > >
>> > > On Mon, Mar 16, 2020 at 9:34 AM Tao Feng <fe...@gmail.com> wrote:
>> > >
>> > > > +1
>> > > >
>> > > > On Mon, Mar 16, 2020 at 7:36 AM Ash Berlin-Taylor <as...@apache.org>
>> > > wrote:
>> > > >
>> > > > > The original discuss thread is here.
>> > > > >
>> > > >
>> > >
>> https://lists.apache.org/thread.html/r19014fac5aa2aa15a86890aa438940da263e430cb535ca451ef451a4%40%3Cdev.airflow.apache.org%3E
>> > > > >
>> > > > > Proposal is:
>> > > > >
>> > > > > - We create a few appropriate issue templates in ./github --
>> > > > specifically
>> > > > > also one for "Ask for help" that basically says "Don't ask here,
>> this
>> > > > will
>> > > > > be closed".
>> > > > > - We ask Infra to enable Github Issues on our apache/airflow repo
>> > > > > - We remove the requirement on code changes to need an
>> accompanying
>> > > Jira
>> > > > > ticket (and we don't replace it with needing a Github Issue
>> either)
>> > > > > - We use Github Milestones to target which PRs should be
>> backported to
>> > > > > release branches.
>> > > > > - We update/port the dev/airflow_jira script from looking at
>> FixVersion
>> > > > in
>> > > > > Jira to look instead at the Milestone.
>> > > > > - We (committers/interested parties) start reviewing the open Jira
>> > > > issues,
>> > > > > manually migrate the ones we think are still relevant to Github
>> Issues,
>> > > > > leave a link (Add Link, not just a comment) on the Jira Issue, and
>> > > close
>> > > > it
>> > > > > with status "Auto Closed"(?). We could also add a
>> "migrated-to-github"
>> > > > > label to migrated issues.
>> > > > > - After the review is done we bulk-comment on any remaining open
>> issue
>> > > > > saying "We are migrating to Github, and believe this issue is no
>> longer
>> > > > > relevant. If you think otherwise please create an issue at <url>".
>> > > > > - Ask Infra to disable creating new Jira issues for the AIRFLOW
>> > > project.
>> > > > >
>> > > > > There is a bit of a "contention/locking" issue about the
>> migration --
>> > > how
>> > > > > to avoid creating duplicate issues. Not the end of the world if
>> we do I
>> > > > > guess.
>> > > > >
>> > > > > This vote will last for 72 hours, ending 2020-03-19T14:35:00Z, and
>> > > until
>> > > > 3
>> > > > > +1 votes are cast.
>> > > > >
>> > > > > This is my binding +1 vote.
>> > > > >
>> > > > > Thanks,
>> > > > > ash
>> > > > >
>> > > > >
>> > > >
>> > >
>>
>
Re: [VOTE] Switch from using Jira to Github Issues
Posted by Sid Anand <r3...@gmail.com>.
+1 Binding
Airflow's returning full-circle to Github issues after 4 years :-)
-s
On Tue, Mar 17, 2020 at 6:48 AM Daniel Imberman <da...@gmail.com>
wrote:
> +1 Binding
>
> No point in having a whole extra site if we’re not using any of the JIRA
> specific features
>
> Daniel
> On Mar 16, 2020, 9:58 PM -0700, Sumit Maheshwari <su...@gmail.com>,
> wrote:
> > +1 binding
> >
> > On Mon, Mar 16, 2020 at 11:44 PM Kevin Yang <yr...@gmail.com> wrote:
> >
> > > +1 binding
> > >
> > > On Mon, Mar 16, 2020 at 9:34 AM Tao Feng <fe...@gmail.com> wrote:
> > >
> > > > +1
> > > >
> > > > On Mon, Mar 16, 2020 at 7:36 AM Ash Berlin-Taylor <as...@apache.org>
> > > wrote:
> > > >
> > > > > The original discuss thread is here.
> > > > >
> > > >
> > >
> https://lists.apache.org/thread.html/r19014fac5aa2aa15a86890aa438940da263e430cb535ca451ef451a4%40%3Cdev.airflow.apache.org%3E
> > > > >
> > > > > Proposal is:
> > > > >
> > > > > - We create a few appropriate issue templates in ./github --
> > > > specifically
> > > > > also one for "Ask for help" that basically says "Don't ask here,
> this
> > > > will
> > > > > be closed".
> > > > > - We ask Infra to enable Github Issues on our apache/airflow repo
> > > > > - We remove the requirement on code changes to need an accompanying
> > > Jira
> > > > > ticket (and we don't replace it with needing a Github Issue either)
> > > > > - We use Github Milestones to target which PRs should be
> backported to
> > > > > release branches.
> > > > > - We update/port the dev/airflow_jira script from looking at
> FixVersion
> > > > in
> > > > > Jira to look instead at the Milestone.
> > > > > - We (committers/interested parties) start reviewing the open Jira
> > > > issues,
> > > > > manually migrate the ones we think are still relevant to Github
> Issues,
> > > > > leave a link (Add Link, not just a comment) on the Jira Issue, and
> > > close
> > > > it
> > > > > with status "Auto Closed"(?). We could also add a
> "migrated-to-github"
> > > > > label to migrated issues.
> > > > > - After the review is done we bulk-comment on any remaining open
> issue
> > > > > saying "We are migrating to Github, and believe this issue is no
> longer
> > > > > relevant. If you think otherwise please create an issue at <url>".
> > > > > - Ask Infra to disable creating new Jira issues for the AIRFLOW
> > > project.
> > > > >
> > > > > There is a bit of a "contention/locking" issue about the migration
> --
> > > how
> > > > > to avoid creating duplicate issues. Not the end of the world if we
> do I
> > > > > guess.
> > > > >
> > > > > This vote will last for 72 hours, ending 2020-03-19T14:35:00Z, and
> > > until
> > > > 3
> > > > > +1 votes are cast.
> > > > >
> > > > > This is my binding +1 vote.
> > > > >
> > > > > Thanks,
> > > > > ash
> > > > >
> > > > >
> > > >
> > >
>
Re: [VOTE] Switch from using Jira to Github Issues
Posted by Daniel Imberman <da...@gmail.com>.
+1 Binding
No point in having a whole extra site if we’re not using any of the JIRA specific features
Daniel
On Mar 16, 2020, 9:58 PM -0700, Sumit Maheshwari <su...@gmail.com>, wrote:
> +1 binding
>
> On Mon, Mar 16, 2020 at 11:44 PM Kevin Yang <yr...@gmail.com> wrote:
>
> > +1 binding
> >
> > On Mon, Mar 16, 2020 at 9:34 AM Tao Feng <fe...@gmail.com> wrote:
> >
> > > +1
> > >
> > > On Mon, Mar 16, 2020 at 7:36 AM Ash Berlin-Taylor <as...@apache.org>
> > wrote:
> > >
> > > > The original discuss thread is here.
> > > >
> > >
> > https://lists.apache.org/thread.html/r19014fac5aa2aa15a86890aa438940da263e430cb535ca451ef451a4%40%3Cdev.airflow.apache.org%3E
> > > >
> > > > Proposal is:
> > > >
> > > > - We create a few appropriate issue templates in ./github --
> > > specifically
> > > > also one for "Ask for help" that basically says "Don't ask here, this
> > > will
> > > > be closed".
> > > > - We ask Infra to enable Github Issues on our apache/airflow repo
> > > > - We remove the requirement on code changes to need an accompanying
> > Jira
> > > > ticket (and we don't replace it with needing a Github Issue either)
> > > > - We use Github Milestones to target which PRs should be backported to
> > > > release branches.
> > > > - We update/port the dev/airflow_jira script from looking at FixVersion
> > > in
> > > > Jira to look instead at the Milestone.
> > > > - We (committers/interested parties) start reviewing the open Jira
> > > issues,
> > > > manually migrate the ones we think are still relevant to Github Issues,
> > > > leave a link (Add Link, not just a comment) on the Jira Issue, and
> > close
> > > it
> > > > with status "Auto Closed"(?). We could also add a "migrated-to-github"
> > > > label to migrated issues.
> > > > - After the review is done we bulk-comment on any remaining open issue
> > > > saying "We are migrating to Github, and believe this issue is no longer
> > > > relevant. If you think otherwise please create an issue at <url>".
> > > > - Ask Infra to disable creating new Jira issues for the AIRFLOW
> > project.
> > > >
> > > > There is a bit of a "contention/locking" issue about the migration --
> > how
> > > > to avoid creating duplicate issues. Not the end of the world if we do I
> > > > guess.
> > > >
> > > > This vote will last for 72 hours, ending 2020-03-19T14:35:00Z, and
> > until
> > > 3
> > > > +1 votes are cast.
> > > >
> > > > This is my binding +1 vote.
> > > >
> > > > Thanks,
> > > > ash
> > > >
> > > >
> > >
> >
Re: [VOTE] Switch from using Jira to Github Issues
Posted by Sumit Maheshwari <su...@gmail.com>.
+1 binding
On Mon, Mar 16, 2020 at 11:44 PM Kevin Yang <yr...@gmail.com> wrote:
> +1 binding
>
> On Mon, Mar 16, 2020 at 9:34 AM Tao Feng <fe...@gmail.com> wrote:
>
> > +1
> >
> > On Mon, Mar 16, 2020 at 7:36 AM Ash Berlin-Taylor <as...@apache.org>
> wrote:
> >
> > > The original discuss thread is here.
> > >
> >
> https://lists.apache.org/thread.html/r19014fac5aa2aa15a86890aa438940da263e430cb535ca451ef451a4%40%3Cdev.airflow.apache.org%3E
> > >
> > > Proposal is:
> > >
> > > - We create a few appropriate issue templates in ./github --
> > specifically
> > > also one for "Ask for help" that basically says "Don't ask here, this
> > will
> > > be closed".
> > > - We ask Infra to enable Github Issues on our apache/airflow repo
> > > - We remove the requirement on code changes to need an accompanying
> Jira
> > > ticket (and we don't replace it with needing a Github Issue either)
> > > - We use Github Milestones to target which PRs should be backported to
> > > release branches.
> > > - We update/port the dev/airflow_jira script from looking at FixVersion
> > in
> > > Jira to look instead at the Milestone.
> > > - We (committers/interested parties) start reviewing the open Jira
> > issues,
> > > manually migrate the ones we think are still relevant to Github Issues,
> > > leave a link (Add Link, not just a comment) on the Jira Issue, and
> close
> > it
> > > with status "Auto Closed"(?). We could also add a "migrated-to-github"
> > > label to migrated issues.
> > > - After the review is done we bulk-comment on any remaining open issue
> > > saying "We are migrating to Github, and believe this issue is no longer
> > > relevant. If you think otherwise please create an issue at <url>".
> > > - Ask Infra to disable creating new Jira issues for the AIRFLOW
> project.
> > >
> > > There is a bit of a "contention/locking" issue about the migration --
> how
> > > to avoid creating duplicate issues. Not the end of the world if we do I
> > > guess.
> > >
> > > This vote will last for 72 hours, ending 2020-03-19T14:35:00Z, and
> until
> > 3
> > > +1 votes are cast.
> > >
> > > This is my binding +1 vote.
> > >
> > > Thanks,
> > > ash
> > >
> > >
> >
>
Re: [VOTE] Switch from using Jira to Github Issues
Posted by Kevin Yang <yr...@gmail.com>.
+1 binding
On Mon, Mar 16, 2020 at 9:34 AM Tao Feng <fe...@gmail.com> wrote:
> +1
>
> On Mon, Mar 16, 2020 at 7:36 AM Ash Berlin-Taylor <as...@apache.org> wrote:
>
> > The original discuss thread is here.
> >
> https://lists.apache.org/thread.html/r19014fac5aa2aa15a86890aa438940da263e430cb535ca451ef451a4%40%3Cdev.airflow.apache.org%3E
> >
> > Proposal is:
> >
> > - We create a few appropriate issue templates in ./github --
> specifically
> > also one for "Ask for help" that basically says "Don't ask here, this
> will
> > be closed".
> > - We ask Infra to enable Github Issues on our apache/airflow repo
> > - We remove the requirement on code changes to need an accompanying Jira
> > ticket (and we don't replace it with needing a Github Issue either)
> > - We use Github Milestones to target which PRs should be backported to
> > release branches.
> > - We update/port the dev/airflow_jira script from looking at FixVersion
> in
> > Jira to look instead at the Milestone.
> > - We (committers/interested parties) start reviewing the open Jira
> issues,
> > manually migrate the ones we think are still relevant to Github Issues,
> > leave a link (Add Link, not just a comment) on the Jira Issue, and close
> it
> > with status "Auto Closed"(?). We could also add a "migrated-to-github"
> > label to migrated issues.
> > - After the review is done we bulk-comment on any remaining open issue
> > saying "We are migrating to Github, and believe this issue is no longer
> > relevant. If you think otherwise please create an issue at <url>".
> > - Ask Infra to disable creating new Jira issues for the AIRFLOW project.
> >
> > There is a bit of a "contention/locking" issue about the migration -- how
> > to avoid creating duplicate issues. Not the end of the world if we do I
> > guess.
> >
> > This vote will last for 72 hours, ending 2020-03-19T14:35:00Z, and until
> 3
> > +1 votes are cast.
> >
> > This is my binding +1 vote.
> >
> > Thanks,
> > ash
> >
> >
>
Re: [VOTE] Switch from using Jira to Github Issues
Posted by Tao Feng <fe...@gmail.com>.
+1
On Mon, Mar 16, 2020 at 7:36 AM Ash Berlin-Taylor <as...@apache.org> wrote:
> The original discuss thread is here.
> https://lists.apache.org/thread.html/r19014fac5aa2aa15a86890aa438940da263e430cb535ca451ef451a4%40%3Cdev.airflow.apache.org%3E
>
> Proposal is:
>
> - We create a few appropriate issue templates in ./github -- specifically
> also one for "Ask for help" that basically says "Don't ask here, this will
> be closed".
> - We ask Infra to enable Github Issues on our apache/airflow repo
> - We remove the requirement on code changes to need an accompanying Jira
> ticket (and we don't replace it with needing a Github Issue either)
> - We use Github Milestones to target which PRs should be backported to
> release branches.
> - We update/port the dev/airflow_jira script from looking at FixVersion in
> Jira to look instead at the Milestone.
> - We (committers/interested parties) start reviewing the open Jira issues,
> manually migrate the ones we think are still relevant to Github Issues,
> leave a link (Add Link, not just a comment) on the Jira Issue, and close it
> with status "Auto Closed"(?). We could also add a "migrated-to-github"
> label to migrated issues.
> - After the review is done we bulk-comment on any remaining open issue
> saying "We are migrating to Github, and believe this issue is no longer
> relevant. If you think otherwise please create an issue at <url>".
> - Ask Infra to disable creating new Jira issues for the AIRFLOW project.
>
> There is a bit of a "contention/locking" issue about the migration -- how
> to avoid creating duplicate issues. Not the end of the world if we do I
> guess.
>
> This vote will last for 72 hours, ending 2020-03-19T14:35:00Z, and until 3
> +1 votes are cast.
>
> This is my binding +1 vote.
>
> Thanks,
> ash
>
>
Re: [VOTE] Switch from using Jira to Github Issues
Posted by Ash Berlin-Taylor <as...@apache.org>.
I wasn't think so, not for now. The Confluence based-flow isn't causing (me) any pain points.
-ash
On 2020/03/16 15:11:33, Darren Weber <dw...@gmail.com> wrote:
> +1
>
> What about AIPs - will they migrate also?
>
> On Mon, Mar 16, 2020 at 8:01 AM Maxime Beauchemin <
> maximebeauchemin@gmail.com> wrote:
>
> > +1 binding
> >
> > On Mon, Mar 16, 2020, 7:45 AM Jarek Potiuk <Ja...@polidea.com>
> > wrote:
> >
> > > +1 binding.
> > >
> > > Re: contention: I think we can split reviewers by components. I think the
> > > assignment to components was done recently so duplicates will be rare. I
> > am
> > > happy to be one of the reviewers.
> > >
> > > On Mon, Mar 16, 2020 at 3:42 PM Kaxil Naik <ka...@gmail.com> wrote:
> > >
> > > > +1 binding
> > > >
> > > > BTW, we can enable Github Issues by just adding the following block in
> > > > *airflow/.asf.yaml*
> > > >
> > > > github:
> > > > features:
> > > > # Enable issues management
> > > > issues: true
> > > > # Enable projects for project management boards
> > > > projects: true
> > > >
> > > > On Mon, Mar 16, 2020 at 2:36 PM Ash Berlin-Taylor <as...@apache.org>
> > > wrote:
> > > >
> > > > > The original discuss thread is here.
> > > > >
> > > >
> > >
> > https://lists.apache.org/thread.html/r19014fac5aa2aa15a86890aa438940da263e430cb535ca451ef451a4%40%3Cdev.airflow.apache.org%3E
> > > > >
> > > > > Proposal is:
> > > > >
> > > > > - We create a few appropriate issue templates in ./github --
> > > > specifically
> > > > > also one for "Ask for help" that basically says "Don't ask here, this
> > > > will
> > > > > be closed".
> > > > > - We ask Infra to enable Github Issues on our apache/airflow repo
> > > > > - We remove the requirement on code changes to need an accompanying
> > > Jira
> > > > > ticket (and we don't replace it with needing a Github Issue either)
> > > > > - We use Github Milestones to target which PRs should be backported
> > to
> > > > > release branches.
> > > > > - We update/port the dev/airflow_jira script from looking at
> > FixVersion
> > > > in
> > > > > Jira to look instead at the Milestone.
> > > > > - We (committers/interested parties) start reviewing the open Jira
> > > > issues,
> > > > > manually migrate the ones we think are still relevant to Github
> > Issues,
> > > > > leave a link (Add Link, not just a comment) on the Jira Issue, and
> > > close
> > > > it
> > > > > with status "Auto Closed"(?). We could also add a
> > "migrated-to-github"
> > > > > label to migrated issues.
> > > > > - After the review is done we bulk-comment on any remaining open
> > issue
> > > > > saying "We are migrating to Github, and believe this issue is no
> > longer
> > > > > relevant. If you think otherwise please create an issue at <url>".
> > > > > - Ask Infra to disable creating new Jira issues for the AIRFLOW
> > > project.
> > > > >
> > > > > There is a bit of a "contention/locking" issue about the migration --
> > > how
> > > > > to avoid creating duplicate issues. Not the end of the world if we
> > do I
> > > > > guess.
> > > > >
> > > > > This vote will last for 72 hours, ending 2020-03-19T14:35:00Z, and
> > > until
> > > > 3
> > > > > +1 votes are cast.
> > > > >
> > > > > This is my binding +1 vote.
> > > > >
> > > > > Thanks,
> > > > > ash
> > > > >
> > > > >
> > > >
> > >
> > >
> > > --
> > >
> > > Jarek Potiuk
> > > Polidea <https://www.polidea.com/> | Principal Software Engineer
> > >
> > > M: +48 660 796 129 <+48660796129>
> > > [image: Polidea] <https://www.polidea.com/>
> > >
> >
>
Re: [VOTE] Switch from using Jira to Github Issues
Posted by Darren Weber <dw...@gmail.com>.
+1
What about AIPs - will they migrate also?
On Mon, Mar 16, 2020 at 8:01 AM Maxime Beauchemin <
maximebeauchemin@gmail.com> wrote:
> +1 binding
>
> On Mon, Mar 16, 2020, 7:45 AM Jarek Potiuk <Ja...@polidea.com>
> wrote:
>
> > +1 binding.
> >
> > Re: contention: I think we can split reviewers by components. I think the
> > assignment to components was done recently so duplicates will be rare. I
> am
> > happy to be one of the reviewers.
> >
> > On Mon, Mar 16, 2020 at 3:42 PM Kaxil Naik <ka...@gmail.com> wrote:
> >
> > > +1 binding
> > >
> > > BTW, we can enable Github Issues by just adding the following block in
> > > *airflow/.asf.yaml*
> > >
> > > github:
> > > features:
> > > # Enable issues management
> > > issues: true
> > > # Enable projects for project management boards
> > > projects: true
> > >
> > > On Mon, Mar 16, 2020 at 2:36 PM Ash Berlin-Taylor <as...@apache.org>
> > wrote:
> > >
> > > > The original discuss thread is here.
> > > >
> > >
> >
> https://lists.apache.org/thread.html/r19014fac5aa2aa15a86890aa438940da263e430cb535ca451ef451a4%40%3Cdev.airflow.apache.org%3E
> > > >
> > > > Proposal is:
> > > >
> > > > - We create a few appropriate issue templates in ./github --
> > > specifically
> > > > also one for "Ask for help" that basically says "Don't ask here, this
> > > will
> > > > be closed".
> > > > - We ask Infra to enable Github Issues on our apache/airflow repo
> > > > - We remove the requirement on code changes to need an accompanying
> > Jira
> > > > ticket (and we don't replace it with needing a Github Issue either)
> > > > - We use Github Milestones to target which PRs should be backported
> to
> > > > release branches.
> > > > - We update/port the dev/airflow_jira script from looking at
> FixVersion
> > > in
> > > > Jira to look instead at the Milestone.
> > > > - We (committers/interested parties) start reviewing the open Jira
> > > issues,
> > > > manually migrate the ones we think are still relevant to Github
> Issues,
> > > > leave a link (Add Link, not just a comment) on the Jira Issue, and
> > close
> > > it
> > > > with status "Auto Closed"(?). We could also add a
> "migrated-to-github"
> > > > label to migrated issues.
> > > > - After the review is done we bulk-comment on any remaining open
> issue
> > > > saying "We are migrating to Github, and believe this issue is no
> longer
> > > > relevant. If you think otherwise please create an issue at <url>".
> > > > - Ask Infra to disable creating new Jira issues for the AIRFLOW
> > project.
> > > >
> > > > There is a bit of a "contention/locking" issue about the migration --
> > how
> > > > to avoid creating duplicate issues. Not the end of the world if we
> do I
> > > > guess.
> > > >
> > > > This vote will last for 72 hours, ending 2020-03-19T14:35:00Z, and
> > until
> > > 3
> > > > +1 votes are cast.
> > > >
> > > > This is my binding +1 vote.
> > > >
> > > > Thanks,
> > > > ash
> > > >
> > > >
> > >
> >
> >
> > --
> >
> > Jarek Potiuk
> > Polidea <https://www.polidea.com/> | Principal Software Engineer
> >
> > M: +48 660 796 129 <+48660796129>
> > [image: Polidea] <https://www.polidea.com/>
> >
>
Re: [VOTE] Switch from using Jira to Github Issues
Posted by Maxime Beauchemin <ma...@gmail.com>.
+1 binding
On Mon, Mar 16, 2020, 7:45 AM Jarek Potiuk <Ja...@polidea.com> wrote:
> +1 binding.
>
> Re: contention: I think we can split reviewers by components. I think the
> assignment to components was done recently so duplicates will be rare. I am
> happy to be one of the reviewers.
>
> On Mon, Mar 16, 2020 at 3:42 PM Kaxil Naik <ka...@gmail.com> wrote:
>
> > +1 binding
> >
> > BTW, we can enable Github Issues by just adding the following block in
> > *airflow/.asf.yaml*
> >
> > github:
> > features:
> > # Enable issues management
> > issues: true
> > # Enable projects for project management boards
> > projects: true
> >
> > On Mon, Mar 16, 2020 at 2:36 PM Ash Berlin-Taylor <as...@apache.org>
> wrote:
> >
> > > The original discuss thread is here.
> > >
> >
> https://lists.apache.org/thread.html/r19014fac5aa2aa15a86890aa438940da263e430cb535ca451ef451a4%40%3Cdev.airflow.apache.org%3E
> > >
> > > Proposal is:
> > >
> > > - We create a few appropriate issue templates in ./github --
> > specifically
> > > also one for "Ask for help" that basically says "Don't ask here, this
> > will
> > > be closed".
> > > - We ask Infra to enable Github Issues on our apache/airflow repo
> > > - We remove the requirement on code changes to need an accompanying
> Jira
> > > ticket (and we don't replace it with needing a Github Issue either)
> > > - We use Github Milestones to target which PRs should be backported to
> > > release branches.
> > > - We update/port the dev/airflow_jira script from looking at FixVersion
> > in
> > > Jira to look instead at the Milestone.
> > > - We (committers/interested parties) start reviewing the open Jira
> > issues,
> > > manually migrate the ones we think are still relevant to Github Issues,
> > > leave a link (Add Link, not just a comment) on the Jira Issue, and
> close
> > it
> > > with status "Auto Closed"(?). We could also add a "migrated-to-github"
> > > label to migrated issues.
> > > - After the review is done we bulk-comment on any remaining open issue
> > > saying "We are migrating to Github, and believe this issue is no longer
> > > relevant. If you think otherwise please create an issue at <url>".
> > > - Ask Infra to disable creating new Jira issues for the AIRFLOW
> project.
> > >
> > > There is a bit of a "contention/locking" issue about the migration --
> how
> > > to avoid creating duplicate issues. Not the end of the world if we do I
> > > guess.
> > >
> > > This vote will last for 72 hours, ending 2020-03-19T14:35:00Z, and
> until
> > 3
> > > +1 votes are cast.
> > >
> > > This is my binding +1 vote.
> > >
> > > Thanks,
> > > ash
> > >
> > >
> >
>
>
> --
>
> Jarek Potiuk
> Polidea <https://www.polidea.com/> | Principal Software Engineer
>
> M: +48 660 796 129 <+48660796129>
> [image: Polidea] <https://www.polidea.com/>
>
Re: [VOTE] Switch from using Jira to Github Issues
Posted by Jarek Potiuk <Ja...@polidea.com>.
+1 binding.
Re: contention: I think we can split reviewers by components. I think the
assignment to components was done recently so duplicates will be rare. I am
happy to be one of the reviewers.
On Mon, Mar 16, 2020 at 3:42 PM Kaxil Naik <ka...@gmail.com> wrote:
> +1 binding
>
> BTW, we can enable Github Issues by just adding the following block in
> *airflow/.asf.yaml*
>
> github:
> features:
> # Enable issues management
> issues: true
> # Enable projects for project management boards
> projects: true
>
> On Mon, Mar 16, 2020 at 2:36 PM Ash Berlin-Taylor <as...@apache.org> wrote:
>
> > The original discuss thread is here.
> >
> https://lists.apache.org/thread.html/r19014fac5aa2aa15a86890aa438940da263e430cb535ca451ef451a4%40%3Cdev.airflow.apache.org%3E
> >
> > Proposal is:
> >
> > - We create a few appropriate issue templates in ./github --
> specifically
> > also one for "Ask for help" that basically says "Don't ask here, this
> will
> > be closed".
> > - We ask Infra to enable Github Issues on our apache/airflow repo
> > - We remove the requirement on code changes to need an accompanying Jira
> > ticket (and we don't replace it with needing a Github Issue either)
> > - We use Github Milestones to target which PRs should be backported to
> > release branches.
> > - We update/port the dev/airflow_jira script from looking at FixVersion
> in
> > Jira to look instead at the Milestone.
> > - We (committers/interested parties) start reviewing the open Jira
> issues,
> > manually migrate the ones we think are still relevant to Github Issues,
> > leave a link (Add Link, not just a comment) on the Jira Issue, and close
> it
> > with status "Auto Closed"(?). We could also add a "migrated-to-github"
> > label to migrated issues.
> > - After the review is done we bulk-comment on any remaining open issue
> > saying "We are migrating to Github, and believe this issue is no longer
> > relevant. If you think otherwise please create an issue at <url>".
> > - Ask Infra to disable creating new Jira issues for the AIRFLOW project.
> >
> > There is a bit of a "contention/locking" issue about the migration -- how
> > to avoid creating duplicate issues. Not the end of the world if we do I
> > guess.
> >
> > This vote will last for 72 hours, ending 2020-03-19T14:35:00Z, and until
> 3
> > +1 votes are cast.
> >
> > This is my binding +1 vote.
> >
> > Thanks,
> > ash
> >
> >
>
--
Jarek Potiuk
Polidea <https://www.polidea.com/> | Principal Software Engineer
M: +48 660 796 129 <+48660796129>
[image: Polidea] <https://www.polidea.com/>
Re: [VOTE] Switch from using Jira to Github Issues
Posted by Tomasz Urbaszek <tu...@apache.org>.
+1 binding
T.
On Mon, Mar 16, 2020 at 3:42 PM Kaxil Naik <ka...@gmail.com> wrote:
>
> +1 binding
>
> BTW, we can enable Github Issues by just adding the following block in
> *airflow/.asf.yaml*
>
> github:
> features:
> # Enable issues management
> issues: true
> # Enable projects for project management boards
> projects: true
>
> On Mon, Mar 16, 2020 at 2:36 PM Ash Berlin-Taylor <as...@apache.org> wrote:
>
> > The original discuss thread is here.
> > https://lists.apache.org/thread.html/r19014fac5aa2aa15a86890aa438940da263e430cb535ca451ef451a4%40%3Cdev.airflow.apache.org%3E
> >
> > Proposal is:
> >
> > - We create a few appropriate issue templates in ./github -- specifically
> > also one for "Ask for help" that basically says "Don't ask here, this will
> > be closed".
> > - We ask Infra to enable Github Issues on our apache/airflow repo
> > - We remove the requirement on code changes to need an accompanying Jira
> > ticket (and we don't replace it with needing a Github Issue either)
> > - We use Github Milestones to target which PRs should be backported to
> > release branches.
> > - We update/port the dev/airflow_jira script from looking at FixVersion in
> > Jira to look instead at the Milestone.
> > - We (committers/interested parties) start reviewing the open Jira issues,
> > manually migrate the ones we think are still relevant to Github Issues,
> > leave a link (Add Link, not just a comment) on the Jira Issue, and close it
> > with status "Auto Closed"(?). We could also add a "migrated-to-github"
> > label to migrated issues.
> > - After the review is done we bulk-comment on any remaining open issue
> > saying "We are migrating to Github, and believe this issue is no longer
> > relevant. If you think otherwise please create an issue at <url>".
> > - Ask Infra to disable creating new Jira issues for the AIRFLOW project.
> >
> > There is a bit of a "contention/locking" issue about the migration -- how
> > to avoid creating duplicate issues. Not the end of the world if we do I
> > guess.
> >
> > This vote will last for 72 hours, ending 2020-03-19T14:35:00Z, and until 3
> > +1 votes are cast.
> >
> > This is my binding +1 vote.
> >
> > Thanks,
> > ash
> >
> >
Re: [VOTE] Switch from using Jira to Github Issues
Posted by Kaxil Naik <ka...@gmail.com>.
+1 binding
BTW, we can enable Github Issues by just adding the following block in
*airflow/.asf.yaml*
github:
features:
# Enable issues management
issues: true
# Enable projects for project management boards
projects: true
On Mon, Mar 16, 2020 at 2:36 PM Ash Berlin-Taylor <as...@apache.org> wrote:
> The original discuss thread is here.
> https://lists.apache.org/thread.html/r19014fac5aa2aa15a86890aa438940da263e430cb535ca451ef451a4%40%3Cdev.airflow.apache.org%3E
>
> Proposal is:
>
> - We create a few appropriate issue templates in ./github -- specifically
> also one for "Ask for help" that basically says "Don't ask here, this will
> be closed".
> - We ask Infra to enable Github Issues on our apache/airflow repo
> - We remove the requirement on code changes to need an accompanying Jira
> ticket (and we don't replace it with needing a Github Issue either)
> - We use Github Milestones to target which PRs should be backported to
> release branches.
> - We update/port the dev/airflow_jira script from looking at FixVersion in
> Jira to look instead at the Milestone.
> - We (committers/interested parties) start reviewing the open Jira issues,
> manually migrate the ones we think are still relevant to Github Issues,
> leave a link (Add Link, not just a comment) on the Jira Issue, and close it
> with status "Auto Closed"(?). We could also add a "migrated-to-github"
> label to migrated issues.
> - After the review is done we bulk-comment on any remaining open issue
> saying "We are migrating to Github, and believe this issue is no longer
> relevant. If you think otherwise please create an issue at <url>".
> - Ask Infra to disable creating new Jira issues for the AIRFLOW project.
>
> There is a bit of a "contention/locking" issue about the migration -- how
> to avoid creating duplicate issues. Not the end of the world if we do I
> guess.
>
> This vote will last for 72 hours, ending 2020-03-19T14:35:00Z, and until 3
> +1 votes are cast.
>
> This is my binding +1 vote.
>
> Thanks,
> ash
>
>