Re: Moving automated nightly build e-mails to a separate mailing list

2021-06-09 Thread Antoine Pitrou
Hello, bui...@arrow.apache.org now also has a GMane mirror at gmane.comp.apache.arrow.builds. Regards Antoine. On Sun, 23 May 2021 08:13:37 -0700 Wes McKinney wrote: > hi folks, > > In an effort to increase the signal-to-noise ratio on dev@, I suggest > that we move the [NIGHTLY] e-mails

Re: Moving automated nightly build e-mails to a separate mailing list

2021-05-25 Thread Sutou Kouhei
Hi, I've added cross...@ursalabs.org to allow list. cross...@ursalabs.org doesn't need to subscribe to builds@ to send nightly e-mails. Thanks, -- kou In "Re: Moving automated nightly build e-mails to a separate mailing list" on Tue, 25 May 2021 09:40:18 +0200, Kr

Re: Moving automated nightly build e-mails to a separate mailing list

2021-05-25 Thread Krisztián Szűcs
ts.apache.org/list.html?bui...@arrow.apache.org:2021-05 Thanks Kou! > > > Thanks, > -- > kou > > In > "Re: Moving automated nightly build e-mails to a separate mailing list" on > Tue, 25 May 2021 09:34:51 +0200, > Krisztián Szűcs wrote: > > >

Re: Moving automated nightly build e-mails to a separate mailing list

2021-05-25 Thread Sutou Kouhei
Hi, It seems that cross...@ursalabs.org isn't subscribed to bui...@arrow.apache.org. I accepted the nightly e-mail in moderated queue now. Could you confirm it? Thanks, -- kou In "Re: Moving automated nightly build e-mails to a separate mailing list" on Tue, 25 May 2021

Re: Moving automated nightly build e-mails to a separate mailing list

2021-05-25 Thread Krisztián Szűcs
On Mon, May 24, 2021 at 8:23 PM Wes McKinney wrote: > > OK. bui...@arrow.apache.org is now ready to use, so can someone please > take care of moving the nightly e-mails there and confirm here when > that's completed? Updated with commit [1] though I'm getting "list not found" error when I'm lookin

Re: Moving automated nightly build e-mails to a separate mailing list

2021-05-24 Thread Jonathan Keane
a new release. Can we work on keeping green nightly build? I > > think that we need to fix failing jobs and remove > > unmaintained failing jobs for it. > > > > > > Thanks, > > -- > > kou > > > > In > > "Re: Moving automated nightly bui

Re: Moving automated nightly build e-mails to a separate mailing list

2021-05-24 Thread Wes McKinney
fix failing jobs and remove > unmaintained failing jobs for it. > > > Thanks, > -- > kou > > In > "Re: Moving automated nightly build e-mails to a separate mailing list" on > Mon, 24 May 2021 11:22:46 -0700, > Wes McKinney wrote: > > > OK. bui

Re: Moving automated nightly build e-mails to a separate mailing list

2021-05-24 Thread Sutou Kouhei
and remove unmaintained failing jobs for it. Thanks, -- kou In "Re: Moving automated nightly build e-mails to a separate mailing list" on Mon, 24 May 2021 11:22:46 -0700, Wes McKinney wrote: > OK. bui...@arrow.apache.org is now ready to use, so can someone please > take ca

Re: Moving automated nightly build e-mails to a separate mailing list

2021-05-24 Thread Wes McKinney
OK. bui...@arrow.apache.org is now ready to use, so can someone please take care of moving the nightly e-mails there and confirm here when that's completed? https://lists.apache.org/list.html?bui...@arrow.apache.org On Mon, May 24, 2021 at 10:40 AM Mauricio Vargas wrote: > > yes, i strongly agre

Re: Moving automated nightly build e-mails to a separate mailing list

2021-05-24 Thread Mauricio Vargas
yes, i strongly agree with this idea i was preparing a static site last week taht I plan to show on wednesday On Mon, May 24, 2021 at 11:13 AM Krisztián Szűcs wrote: > We could generate a static website on the crossbow github page > including more details about the failures - this would keep cro

Re: Moving automated nightly build e-mails to a separate mailing list

2021-05-24 Thread Krisztián Szűcs
We could generate a static website on the crossbow github page including more details about the failures - this would keep crossbow self-contained. I'd suggest still sending the failing builds on the new mailing list (including the static page's link), so we get notified by the failures. On Mon, M

Re: Moving automated nightly build e-mails to a separate mailing list

2021-05-24 Thread Wes McKinney
Frankly I think we should move these reports to a real website rather than sending these emails. The emails to me were always a stopgap to add some visibility where there previously was little (you had to go digging on crossbow). On Mon, May 24, 2021 at 2:01 AM Krisztián Szűcs wrote: > On Sun, M

Re: Moving automated nightly build e-mails to a separate mailing list

2021-05-24 Thread Krisztián Szűcs
On Sun, May 23, 2021 at 7:30 PM Wes McKinney wrote: > > I just requested builds@ to be created on the self-service platform. Hi, Having a separate list sounds like a good idea to me. Could we enable HTML emails on that list? See jira https://issues.apache.org/jira/browse/ARROW-12822 > > > On Sun,

Re: Moving automated nightly build e-mails to a separate mailing list

2021-05-23 Thread Wes McKinney
I just requested builds@ to be created on the self-service platform. On Sun, May 23, 2021 at 10:12 AM Mauricio Vargas wrote: > > hi > > I agree with this, and being the person who has been digging into nightly > errors, I can move this to a weekly email to builds@ > > > On Sun, May 23, 2021 at 1

Re: Moving automated nightly build e-mails to a separate mailing list

2021-05-23 Thread Mauricio Vargas
hi I agree with this, and being the person who has been digging into nightly errors, I can move this to a weekly email to builds@ On Sun, May 23, 2021 at 11:14 AM Wes McKinney wrote: > hi folks, > > In an effort to increase the signal-to-noise ratio on dev@, I suggest > that we move the [NIGHT

Moving automated nightly build e-mails to a separate mailing list

2021-05-23 Thread Wes McKinney
hi folks, In an effort to increase the signal-to-noise ratio on dev@, I suggest that we move the [NIGHTLY] e-mails to a separate bui...@arrow.apache.org e-mail address (or similarly named). Having them on a mailing list makes it easy for us to see them when we want to see them, but otherwise for m