Re: [VOTE] Move issue tracking to GitHub Issues
Le 31/10/2022 à 14:17, Neal Richardson a écrit : The vote passes with 10 binding +1 votes and 9 other +1s. Thanks all. The Infra policy change takes effect on November 6, so we have this week to work through the migration and other questions. It doesn't have to be done by November 6. Let's ensure we have a high-quality migration rather than a rushed one. Regards Antoine. Let's discuss further on https://github.com/apache/arrow/issues/14542 and its subtasks. Neal On Thu, Oct 27, 2022 at 4:25 PM Matt Topol wrote: +1 (Non-binding) On Thu, Oct 27, 2022, 4:19 PM Joris Van den Bossche < jorisvandenboss...@gmail.com> wrote: +1 On Thu, 27 Oct 2022 at 07:27, Jacob Quinn wrote: +1 On Wed, Oct 26, 2022 at 5:04 PM Neal Richardson < neal.p.richard...@gmail.com> wrote: I propose that we move issue tracking from the ASF's Jira to GitHub Issues. This has been discussed on [1] and [2] and there seems to be consensus. A number of Arrow subprojects already use GitHub Issues; this moves the issue tracking for `apache/arrow` into GitHub along with the source code. The vote will be open for at least 72 hours. [ ] +1 Leave ASF Jira and move to GitHub Issues [ ] +0 [ ] -1 Remain in Jira because... My vote: +1 Neal [1]: https://lists.apache.org/thread/l545m95xmf3w47oxwqxvg811or7b93tb [2]: https://lists.apache.org/thread/0vwj8gdo55jly5zn16wksrotyqqm0zqr
Re: [VOTE] Move issue tracking to GitHub Issues
The vote passes with 10 binding +1 votes and 9 other +1s. Thanks all. The Infra policy change takes effect on November 6, so we have this week to work through the migration and other questions. Let's discuss further on https://github.com/apache/arrow/issues/14542 and its subtasks. Neal On Thu, Oct 27, 2022 at 4:25 PM Matt Topol wrote: > +1 (Non-binding) > > On Thu, Oct 27, 2022, 4:19 PM Joris Van den Bossche < > jorisvandenboss...@gmail.com> wrote: > > > +1 > > > > On Thu, 27 Oct 2022 at 07:27, Jacob Quinn > wrote: > > > > > > +1 > > > > > > On Wed, Oct 26, 2022 at 5:04 PM Neal Richardson < > > neal.p.richard...@gmail.com> > > > wrote: > > > > > > > I propose that we move issue tracking from the ASF's Jira to GitHub > > Issues. > > > > This has been discussed on [1] and [2] and there seems to be > > consensus. A > > > > number of Arrow subprojects already use GitHub Issues; this moves the > > issue > > > > tracking for `apache/arrow` into GitHub along with the source code. > > > > > > > > The vote will be open for at least 72 hours. > > > > > > > > [ ] +1 Leave ASF Jira and move to GitHub Issues > > > > [ ] +0 > > > > [ ] -1 Remain in Jira because... > > > > > > > > My vote: +1 > > > > > > > > Neal > > > > > > > > > > > > [1]: > https://lists.apache.org/thread/l545m95xmf3w47oxwqxvg811or7b93tb > > > > [2]: > https://lists.apache.org/thread/0vwj8gdo55jly5zn16wksrotyqqm0zqr > > > > > > >
Re: [VOTE] Move issue tracking to GitHub Issues
+1 (Non-binding) On Thu, Oct 27, 2022, 4:19 PM Joris Van den Bossche < jorisvandenboss...@gmail.com> wrote: > +1 > > On Thu, 27 Oct 2022 at 07:27, Jacob Quinn wrote: > > > > +1 > > > > On Wed, Oct 26, 2022 at 5:04 PM Neal Richardson < > neal.p.richard...@gmail.com> > > wrote: > > > > > I propose that we move issue tracking from the ASF's Jira to GitHub > Issues. > > > This has been discussed on [1] and [2] and there seems to be > consensus. A > > > number of Arrow subprojects already use GitHub Issues; this moves the > issue > > > tracking for `apache/arrow` into GitHub along with the source code. > > > > > > The vote will be open for at least 72 hours. > > > > > > [ ] +1 Leave ASF Jira and move to GitHub Issues > > > [ ] +0 > > > [ ] -1 Remain in Jira because... > > > > > > My vote: +1 > > > > > > Neal > > > > > > > > > [1]: https://lists.apache.org/thread/l545m95xmf3w47oxwqxvg811or7b93tb > > > [2]: https://lists.apache.org/thread/0vwj8gdo55jly5zn16wksrotyqqm0zqr > > > >
Re: [VOTE] Move issue tracking to GitHub Issues
+1 On Thu, 27 Oct 2022 at 07:27, Jacob Quinn wrote: > > +1 > > On Wed, Oct 26, 2022 at 5:04 PM Neal Richardson > wrote: > > > I propose that we move issue tracking from the ASF's Jira to GitHub Issues. > > This has been discussed on [1] and [2] and there seems to be consensus. A > > number of Arrow subprojects already use GitHub Issues; this moves the issue > > tracking for `apache/arrow` into GitHub along with the source code. > > > > The vote will be open for at least 72 hours. > > > > [ ] +1 Leave ASF Jira and move to GitHub Issues > > [ ] +0 > > [ ] -1 Remain in Jira because... > > > > My vote: +1 > > > > Neal > > > > > > [1]: https://lists.apache.org/thread/l545m95xmf3w47oxwqxvg811or7b93tb > > [2]: https://lists.apache.org/thread/0vwj8gdo55jly5zn16wksrotyqqm0zqr > >
Re: [VOTE] Move issue tracking to GitHub Issues
+1 On Thu, 27 Oct 2022 at 08:34, Matt Phelps wrote: > +1 > > From: Uwe L. Korn > Date: Thursday, October 27, 2022 at 10:22 AM > To: dev@arrow.apache.org > Subject: Re: [VOTE] Move issue tracking to GitHub Issues > CAUTION: This email originated from outside of the organization. Do not > click links or open attachments unless you recognize the sender and know > the content is safe. > > +1 > > On Thu, Oct 27, 2022, at 5:13 PM, Nic wrote: > > +1 > > > > On Thu, 27 Oct 2022 at 14:00, Alenka Frim .invalid> > > wrote: > > > >> +1 > >> > >> On Thu, Oct 27, 2022 at 2:36 PM prem sagar gali > >> wrote: > >> > >> > +1 > >> > > >> > On Thu, Oct 27, 2022 at 7:13 AM Dewey Dunnington > >> > wrote: > >> > > >> > > +1 (non-binding)! > >> > > > >> > > On Thu, Oct 27, 2022 at 8:54 AM Eric Hanson > > >> > > wrote: > >> > > > >> > > > +1 > >> > > > > >> > > > On 2022/10/26 23:02:33 Neal Richardson wrote: > >> > > > > I propose that we move issue tracking from the ASF's Jira to > GitHub > >> > > > Issues. > >> > > > > This has been discussed on [1] and [2] and there seems to be > >> > > consensus. A > >> > > > > number of Arrow subprojects already use GitHub Issues; this > moves > >> the > >> > > > issue > >> > > > > tracking for `apache/arrow` into GitHub along with the source > code. > >> > > > > > >> > > > > The vote will be open for at least 72 hours. > >> > > > > > >> > > > > [ ] +1 Leave ASF Jira and move to GitHub Issues > >> > > > > [ ] +0 > >> > > > > [ ] -1 Remain in Jira because... > >> > > > > > >> > > > > My vote: +1 > >> > > > > > >> > > > > Neal > >> > > > > > >> > > > > > >> > > > > [1]: > >> > > https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.apache.org%2Fthread%2Fl545m95xmf3w47oxwqxvg811or7b93tb&data=05%7C01%7Cmatt.phelps%408451.com%7C17169903a26945db335608dab82f1a2f%7C5f9dc6bdf38a454a864cc803691193c5%7C0%7C0%7C638024809699659114%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=cbc4pEWsIlRSH2bLOcMVgDAMT2NM%2FeqG86FYv%2FPmaME%3D&reserved=0 > >> > > > > [2]: > >> > > https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.apache.org%2Fthread%2F0vwj8gdo55jly5zn16wksrotyqqm0zqr&data=05%7C01%7Cmatt.phelps%408451.com%7C17169903a26945db335608dab82f1a2f%7C5f9dc6bdf38a454a864cc803691193c5%7C0%7C0%7C638024809699659114%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=lkTheFeoBmRNQ0IeG5OA2f9TfW%2FZ52L4QEX3aTNexKs%3D&reserved=0 > >> > > > > > >> > > > > >> > > > >> > > >> >
Re: [VOTE] Move issue tracking to GitHub Issues
+1 From: Uwe L. Korn Date: Thursday, October 27, 2022 at 10:22 AM To: dev@arrow.apache.org Subject: Re: [VOTE] Move issue tracking to GitHub Issues CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe. +1 On Thu, Oct 27, 2022, at 5:13 PM, Nic wrote: > +1 > > On Thu, 27 Oct 2022 at 14:00, Alenka Frim > wrote: > >> +1 >> >> On Thu, Oct 27, 2022 at 2:36 PM prem sagar gali >> wrote: >> >> > +1 >> > >> > On Thu, Oct 27, 2022 at 7:13 AM Dewey Dunnington >> > wrote: >> > >> > > +1 (non-binding)! >> > > >> > > On Thu, Oct 27, 2022 at 8:54 AM Eric Hanson >> > > wrote: >> > > >> > > > +1 >> > > > >> > > > On 2022/10/26 23:02:33 Neal Richardson wrote: >> > > > > I propose that we move issue tracking from the ASF's Jira to GitHub >> > > > Issues. >> > > > > This has been discussed on [1] and [2] and there seems to be >> > > consensus. A >> > > > > number of Arrow subprojects already use GitHub Issues; this moves >> the >> > > > issue >> > > > > tracking for `apache/arrow` into GitHub along with the source code. >> > > > > >> > > > > The vote will be open for at least 72 hours. >> > > > > >> > > > > [ ] +1 Leave ASF Jira and move to GitHub Issues >> > > > > [ ] +0 >> > > > > [ ] -1 Remain in Jira because... >> > > > > >> > > > > My vote: +1 >> > > > > >> > > > > Neal >> > > > > >> > > > > >> > > > > [1]: >> > https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.apache.org%2Fthread%2Fl545m95xmf3w47oxwqxvg811or7b93tb&data=05%7C01%7Cmatt.phelps%408451.com%7C17169903a26945db335608dab82f1a2f%7C5f9dc6bdf38a454a864cc803691193c5%7C0%7C0%7C638024809699659114%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=cbc4pEWsIlRSH2bLOcMVgDAMT2NM%2FeqG86FYv%2FPmaME%3D&reserved=0 >> > > > > [2]: >> > https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.apache.org%2Fthread%2F0vwj8gdo55jly5zn16wksrotyqqm0zqr&data=05%7C01%7Cmatt.phelps%408451.com%7C17169903a26945db335608dab82f1a2f%7C5f9dc6bdf38a454a864cc803691193c5%7C0%7C0%7C638024809699659114%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=lkTheFeoBmRNQ0IeG5OA2f9TfW%2FZ52L4QEX3aTNexKs%3D&reserved=0 >> > > > > >> > > > >> > > >> > >>
Re: [VOTE] Move issue tracking to GitHub Issues
+1 On Thu, Oct 27, 2022, at 5:13 PM, Nic wrote: > +1 > > On Thu, 27 Oct 2022 at 14:00, Alenka Frim > wrote: > >> +1 >> >> On Thu, Oct 27, 2022 at 2:36 PM prem sagar gali >> wrote: >> >> > +1 >> > >> > On Thu, Oct 27, 2022 at 7:13 AM Dewey Dunnington >> > wrote: >> > >> > > +1 (non-binding)! >> > > >> > > On Thu, Oct 27, 2022 at 8:54 AM Eric Hanson >> > > wrote: >> > > >> > > > +1 >> > > > >> > > > On 2022/10/26 23:02:33 Neal Richardson wrote: >> > > > > I propose that we move issue tracking from the ASF's Jira to GitHub >> > > > Issues. >> > > > > This has been discussed on [1] and [2] and there seems to be >> > > consensus. A >> > > > > number of Arrow subprojects already use GitHub Issues; this moves >> the >> > > > issue >> > > > > tracking for `apache/arrow` into GitHub along with the source code. >> > > > > >> > > > > The vote will be open for at least 72 hours. >> > > > > >> > > > > [ ] +1 Leave ASF Jira and move to GitHub Issues >> > > > > [ ] +0 >> > > > > [ ] -1 Remain in Jira because... >> > > > > >> > > > > My vote: +1 >> > > > > >> > > > > Neal >> > > > > >> > > > > >> > > > > [1]: >> > https://lists.apache.org/thread/l545m95xmf3w47oxwqxvg811or7b93tb >> > > > > [2]: >> > https://lists.apache.org/thread/0vwj8gdo55jly5zn16wksrotyqqm0zqr >> > > > > >> > > > >> > > >> > >>
Re: [VOTE] Move issue tracking to GitHub Issues
+1 On Thu, 27 Oct 2022 at 14:00, Alenka Frim wrote: > +1 > > On Thu, Oct 27, 2022 at 2:36 PM prem sagar gali > wrote: > > > +1 > > > > On Thu, Oct 27, 2022 at 7:13 AM Dewey Dunnington > > wrote: > > > > > +1 (non-binding)! > > > > > > On Thu, Oct 27, 2022 at 8:54 AM Eric Hanson > > > wrote: > > > > > > > +1 > > > > > > > > On 2022/10/26 23:02:33 Neal Richardson wrote: > > > > > I propose that we move issue tracking from the ASF's Jira to GitHub > > > > Issues. > > > > > This has been discussed on [1] and [2] and there seems to be > > > consensus. A > > > > > number of Arrow subprojects already use GitHub Issues; this moves > the > > > > issue > > > > > tracking for `apache/arrow` into GitHub along with the source code. > > > > > > > > > > The vote will be open for at least 72 hours. > > > > > > > > > > [ ] +1 Leave ASF Jira and move to GitHub Issues > > > > > [ ] +0 > > > > > [ ] -1 Remain in Jira because... > > > > > > > > > > My vote: +1 > > > > > > > > > > Neal > > > > > > > > > > > > > > > [1]: > > https://lists.apache.org/thread/l545m95xmf3w47oxwqxvg811or7b93tb > > > > > [2]: > > https://lists.apache.org/thread/0vwj8gdo55jly5zn16wksrotyqqm0zqr > > > > > > > > > > > > > > >
Re: [VOTE] Move issue tracking to GitHub Issues
+1 On Thu, Oct 27, 2022 at 2:36 PM prem sagar gali wrote: > +1 > > On Thu, Oct 27, 2022 at 7:13 AM Dewey Dunnington > wrote: > > > +1 (non-binding)! > > > > On Thu, Oct 27, 2022 at 8:54 AM Eric Hanson > > wrote: > > > > > +1 > > > > > > On 2022/10/26 23:02:33 Neal Richardson wrote: > > > > I propose that we move issue tracking from the ASF's Jira to GitHub > > > Issues. > > > > This has been discussed on [1] and [2] and there seems to be > > consensus. A > > > > number of Arrow subprojects already use GitHub Issues; this moves the > > > issue > > > > tracking for `apache/arrow` into GitHub along with the source code. > > > > > > > > The vote will be open for at least 72 hours. > > > > > > > > [ ] +1 Leave ASF Jira and move to GitHub Issues > > > > [ ] +0 > > > > [ ] -1 Remain in Jira because... > > > > > > > > My vote: +1 > > > > > > > > Neal > > > > > > > > > > > > [1]: > https://lists.apache.org/thread/l545m95xmf3w47oxwqxvg811or7b93tb > > > > [2]: > https://lists.apache.org/thread/0vwj8gdo55jly5zn16wksrotyqqm0zqr > > > > > > > > > >
Re: [VOTE] Move issue tracking to GitHub Issues
+1 On Thu, Oct 27, 2022 at 7:13 AM Dewey Dunnington wrote: > +1 (non-binding)! > > On Thu, Oct 27, 2022 at 8:54 AM Eric Hanson > wrote: > > > +1 > > > > On 2022/10/26 23:02:33 Neal Richardson wrote: > > > I propose that we move issue tracking from the ASF's Jira to GitHub > > Issues. > > > This has been discussed on [1] and [2] and there seems to be > consensus. A > > > number of Arrow subprojects already use GitHub Issues; this moves the > > issue > > > tracking for `apache/arrow` into GitHub along with the source code. > > > > > > The vote will be open for at least 72 hours. > > > > > > [ ] +1 Leave ASF Jira and move to GitHub Issues > > > [ ] +0 > > > [ ] -1 Remain in Jira because... > > > > > > My vote: +1 > > > > > > Neal > > > > > > > > > [1]: https://lists.apache.org/thread/l545m95xmf3w47oxwqxvg811or7b93tb > > > [2]: https://lists.apache.org/thread/0vwj8gdo55jly5zn16wksrotyqqm0zqr > > > > > >
Re: [VOTE] Move issue tracking to GitHub Issues
+1 (non-binding)! On Thu, Oct 27, 2022 at 8:54 AM Eric Hanson wrote: > +1 > > On 2022/10/26 23:02:33 Neal Richardson wrote: > > I propose that we move issue tracking from the ASF's Jira to GitHub > Issues. > > This has been discussed on [1] and [2] and there seems to be consensus. A > > number of Arrow subprojects already use GitHub Issues; this moves the > issue > > tracking for `apache/arrow` into GitHub along with the source code. > > > > The vote will be open for at least 72 hours. > > > > [ ] +1 Leave ASF Jira and move to GitHub Issues > > [ ] +0 > > [ ] -1 Remain in Jira because... > > > > My vote: +1 > > > > Neal > > > > > > [1]: https://lists.apache.org/thread/l545m95xmf3w47oxwqxvg811or7b93tb > > [2]: https://lists.apache.org/thread/0vwj8gdo55jly5zn16wksrotyqqm0zqr > > >
Re: [VOTE] Move issue tracking to GitHub Issues
+1 On 2022/10/26 23:02:33 Neal Richardson wrote: > I propose that we move issue tracking from the ASF's Jira to GitHub Issues. > This has been discussed on [1] and [2] and there seems to be consensus. A > number of Arrow subprojects already use GitHub Issues; this moves the issue > tracking for `apache/arrow` into GitHub along with the source code. > > The vote will be open for at least 72 hours. > > [ ] +1 Leave ASF Jira and move to GitHub Issues > [ ] +0 > [ ] -1 Remain in Jira because... > > My vote: +1 > > Neal > > > [1]: https://lists.apache.org/thread/l545m95xmf3w47oxwqxvg811or7b93tb > [2]: https://lists.apache.org/thread/0vwj8gdo55jly5zn16wksrotyqqm0zqr >
Re: [VOTE] Move issue tracking to GitHub Issues
+1 (non-binding) Rok On Thu, Oct 27, 2022 at 9:19 AM Antoine Pitrou wrote: > > +1 (binding) but let's make sure we have a quality migration to keep as > much of the JIRA metadata as possible. > > Regards > > Antoine. > > > Le 27/10/2022 à 01:02, Neal Richardson a écrit : > > I propose that we move issue tracking from the ASF's Jira to GitHub > Issues. > > This has been discussed on [1] and [2] and there seems to be consensus. A > > number of Arrow subprojects already use GitHub Issues; this moves the > issue > > tracking for `apache/arrow` into GitHub along with the source code. > > > > The vote will be open for at least 72 hours. > > > > [ ] +1 Leave ASF Jira and move to GitHub Issues > > [ ] +0 > > [ ] -1 Remain in Jira because... > > > > My vote: +1 > > > > Neal > > > > > > [1]: https://lists.apache.org/thread/l545m95xmf3w47oxwqxvg811or7b93tb > > [2]: https://lists.apache.org/thread/0vwj8gdo55jly5zn16wksrotyqqm0zqr > > >
Re: [VOTE] Move issue tracking to GitHub Issues
+1 (binding) but let's make sure we have a quality migration to keep as much of the JIRA metadata as possible. Regards Antoine. Le 27/10/2022 à 01:02, Neal Richardson a écrit : I propose that we move issue tracking from the ASF's Jira to GitHub Issues. This has been discussed on [1] and [2] and there seems to be consensus. A number of Arrow subprojects already use GitHub Issues; this moves the issue tracking for `apache/arrow` into GitHub along with the source code. The vote will be open for at least 72 hours. [ ] +1 Leave ASF Jira and move to GitHub Issues [ ] +0 [ ] -1 Remain in Jira because... My vote: +1 Neal [1]: https://lists.apache.org/thread/l545m95xmf3w47oxwqxvg811or7b93tb [2]: https://lists.apache.org/thread/0vwj8gdo55jly5zn16wksrotyqqm0zqr
Re: [VOTE] Move issue tracking to GitHub Issues
+1 On Wed, Oct 26, 2022 at 5:04 PM Neal Richardson wrote: > I propose that we move issue tracking from the ASF's Jira to GitHub Issues. > This has been discussed on [1] and [2] and there seems to be consensus. A > number of Arrow subprojects already use GitHub Issues; this moves the issue > tracking for `apache/arrow` into GitHub along with the source code. > > The vote will be open for at least 72 hours. > > [ ] +1 Leave ASF Jira and move to GitHub Issues > [ ] +0 > [ ] -1 Remain in Jira because... > > My vote: +1 > > Neal > > > [1]: https://lists.apache.org/thread/l545m95xmf3w47oxwqxvg811or7b93tb > [2]: https://lists.apache.org/thread/0vwj8gdo55jly5zn16wksrotyqqm0zqr >
Re: [VOTE] Move issue tracking to GitHub Issues
+1, I'm very glad to see what will hopefully be a _slightly smoother_ experience for new contributors + issue reporters -Jon On Wed, Oct 26, 2022 at 7:05 PM David Li wrote: > +1 > > On Wed, Oct 26, 2022, at 20:01, Andy Grove wrote: > > +1 > > > > On Wed, Oct 26, 2022 at 5:50 PM L. C. Hsieh wrote: > > > >> +1 > >> > >> > >> > >> On Wed, Oct 26, 2022 at 4:08 PM Raphael Taylor-Davies > >> wrote: > >> > > >> > +1 > >> > > >> > On 27/10/2022 12:02, Neal Richardson wrote: > >> > > I propose that we move issue tracking from the ASF's Jira to GitHub > >> Issues. > >> > > This has been discussed on [1] and [2] and there seems to be > >> consensus. A > >> > > number of Arrow subprojects already use GitHub Issues; this moves > the > >> issue > >> > > tracking for `apache/arrow` into GitHub along with the source code. > >> > > > >> > > The vote will be open for at least 72 hours. > >> > > > >> > > [ ] +1 Leave ASF Jira and move to GitHub Issues > >> > > [ ] +0 > >> > > [ ] -1 Remain in Jira because... > >> > > > >> > > My vote: +1 > >> > > > >> > > Neal > >> > > > >> > > > >> > > [1]: > https://lists.apache.org/thread/l545m95xmf3w47oxwqxvg811or7b93tb > >> > > [2]: > https://lists.apache.org/thread/0vwj8gdo55jly5zn16wksrotyqqm0zqr > >> > > > >> >
Re: [VOTE] Move issue tracking to GitHub Issues
+1 On Wed, Oct 26, 2022, at 20:01, Andy Grove wrote: > +1 > > On Wed, Oct 26, 2022 at 5:50 PM L. C. Hsieh wrote: > >> +1 >> >> >> >> On Wed, Oct 26, 2022 at 4:08 PM Raphael Taylor-Davies >> wrote: >> > >> > +1 >> > >> > On 27/10/2022 12:02, Neal Richardson wrote: >> > > I propose that we move issue tracking from the ASF's Jira to GitHub >> Issues. >> > > This has been discussed on [1] and [2] and there seems to be >> consensus. A >> > > number of Arrow subprojects already use GitHub Issues; this moves the >> issue >> > > tracking for `apache/arrow` into GitHub along with the source code. >> > > >> > > The vote will be open for at least 72 hours. >> > > >> > > [ ] +1 Leave ASF Jira and move to GitHub Issues >> > > [ ] +0 >> > > [ ] -1 Remain in Jira because... >> > > >> > > My vote: +1 >> > > >> > > Neal >> > > >> > > >> > > [1]: https://lists.apache.org/thread/l545m95xmf3w47oxwqxvg811or7b93tb >> > > [2]: https://lists.apache.org/thread/0vwj8gdo55jly5zn16wksrotyqqm0zqr >> > > >>
Re: [VOTE] Move issue tracking to GitHub Issues
+1 On Wed, Oct 26, 2022 at 5:50 PM L. C. Hsieh wrote: > +1 > > > > On Wed, Oct 26, 2022 at 4:08 PM Raphael Taylor-Davies > wrote: > > > > +1 > > > > On 27/10/2022 12:02, Neal Richardson wrote: > > > I propose that we move issue tracking from the ASF's Jira to GitHub > Issues. > > > This has been discussed on [1] and [2] and there seems to be > consensus. A > > > number of Arrow subprojects already use GitHub Issues; this moves the > issue > > > tracking for `apache/arrow` into GitHub along with the source code. > > > > > > The vote will be open for at least 72 hours. > > > > > > [ ] +1 Leave ASF Jira and move to GitHub Issues > > > [ ] +0 > > > [ ] -1 Remain in Jira because... > > > > > > My vote: +1 > > > > > > Neal > > > > > > > > > [1]: https://lists.apache.org/thread/l545m95xmf3w47oxwqxvg811or7b93tb > > > [2]: https://lists.apache.org/thread/0vwj8gdo55jly5zn16wksrotyqqm0zqr > > > >
Re: [VOTE] Move issue tracking to GitHub Issues
+1 On Wed, Oct 26, 2022 at 4:08 PM Raphael Taylor-Davies wrote: > > +1 > > On 27/10/2022 12:02, Neal Richardson wrote: > > I propose that we move issue tracking from the ASF's Jira to GitHub Issues. > > This has been discussed on [1] and [2] and there seems to be consensus. A > > number of Arrow subprojects already use GitHub Issues; this moves the issue > > tracking for `apache/arrow` into GitHub along with the source code. > > > > The vote will be open for at least 72 hours. > > > > [ ] +1 Leave ASF Jira and move to GitHub Issues > > [ ] +0 > > [ ] -1 Remain in Jira because... > > > > My vote: +1 > > > > Neal > > > > > > [1]: https://lists.apache.org/thread/l545m95xmf3w47oxwqxvg811or7b93tb > > [2]: https://lists.apache.org/thread/0vwj8gdo55jly5zn16wksrotyqqm0zqr > >
Re: [VOTE] Move issue tracking to GitHub Issues
+1 On 27/10/2022 12:02, Neal Richardson wrote: I propose that we move issue tracking from the ASF's Jira to GitHub Issues. This has been discussed on [1] and [2] and there seems to be consensus. A number of Arrow subprojects already use GitHub Issues; this moves the issue tracking for `apache/arrow` into GitHub along with the source code. The vote will be open for at least 72 hours. [ ] +1 Leave ASF Jira and move to GitHub Issues [ ] +0 [ ] -1 Remain in Jira because... My vote: +1 Neal [1]: https://lists.apache.org/thread/l545m95xmf3w47oxwqxvg811or7b93tb [2]: https://lists.apache.org/thread/0vwj8gdo55jly5zn16wksrotyqqm0zqr
[VOTE] Move issue tracking to GitHub Issues
I propose that we move issue tracking from the ASF's Jira to GitHub Issues. This has been discussed on [1] and [2] and there seems to be consensus. A number of Arrow subprojects already use GitHub Issues; this moves the issue tracking for `apache/arrow` into GitHub along with the source code. The vote will be open for at least 72 hours. [ ] +1 Leave ASF Jira and move to GitHub Issues [ ] +0 [ ] -1 Remain in Jira because... My vote: +1 Neal [1]: https://lists.apache.org/thread/l545m95xmf3w47oxwqxvg811or7b93tb [2]: https://lists.apache.org/thread/0vwj8gdo55jly5zn16wksrotyqqm0zqr
