You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@kudu.apache.org by Andrew Wong <aw...@apache.org> on 2020/07/20 19:23:04 UTC
[DISCUSS] Should we have a builds@kudu.apache.org mailing list?
Hello Kudu developers!
I've been discussing with some folks about the current state of this (dev@)
mailing list, which has recently gained more traffic from the "Daily KUDU
ARM64 Cron Job." Several people have noticed the alerts becoming quite
noisy, and crowding the inbox, with very little visibility into the issue,
who is working on fixing it, etc. This doesn't seem like the best use of
dev@, which historically has been more for design and developer-related
discussions.
There are some suggestions in KUDU-3007
<https://issues.apache.org/jira/browse/KUDU-3007> with regards to less
trivial testing infra improvements that can be made to incorporate ARM
testing with the rest of Kudu's CI pipeline. Grant and I have also been
discussing the possibility getting a more widely available ARM build via
dockerx. These projects, while important, may not have as many developer
cycles as we'd like to get them through the finish line, at least for the
next few weeks.
So until these materialize, one suggestion is to create a new mailing list,
builds@k.a.o, to catch these, and other build-related issues. Today, such
build failures may be reported on Slack at #kudu-general or #kudu-macos, or
on Jira -- it might be nice to have a single, archived, searchable list to
document such issues, as well as catch these kinds of CI emails for the
time being.
Other projects have similar "builds" mailing lists
<https://mail-archives.apache.org/mod_mbox/>; it doesn't seem unreasonable
to start one for Kudu as well, so per the ASF Mailing List Moderation
guidelines <https://infra.apache.org/mailing-list-moderation.html>, I'm
surfacing this to discuss a bit here. If there's agreement on this being a
useful list to have, I'll send out a request to create it.
Thanks,
Andrew
Re: [DISCUSS] Should we have a builds@kudu.apache.org mailing list?
Posted by Sheng Liu <li...@gmail.com>.
Hi Andrew,
Thank for doing this, I have change the ARM CI configurations to use the
builds@kudu.apache.org, let's see if it works.
Regards
---
Liu sheng
Andrew Wong <aw...@apache.org> 于2020年8月3日周一 上午5:58写道：
> Circling back to this, builds@kudu.apache.org is up and running. The
> archive can be found here
> <ht...@kudu.apache.org>.
>
> On Wed, Jul 22, 2020 at 12:29 PM Grant Henke <gh...@cloudera.com.invalid>
> wrote:
>
> > +1 to a new builds@ mailing list. Thanks for driving this Andrew.
> >
> > On Tue, Jul 21, 2020 at 6:03 PM Andrew Wong <aw...@apache.org> wrote:
> >
> > > Hey!
> > >
> > > No problem, it is more indicative that there is a gap in Kudu's
> > > infrastructure and process with regards to building/testing on
> different
> > > architectures. Hopefully a separate mailing list is a step in the right
> > > direction.
> > >
> > > If there are no objections, I'll submit a ticket to create the mailing
> > list
> > > at the end of the week (will give some time for folks to continue
> chiming
> > > in, in case there's more feedback).
> > >
> > > On Mon, Jul 20, 2020 at 8:13 PM Sheng Liu <li...@gmail.com>
> > wrote:
> > >
> > > > Hi,
> > > > Thanks for bringing this up, we are the maintainers of the ARM CI,
> > sorry
> > > > for the noise of dev mailing list from "Daily KUDU ARM64 Cron Job."
> > The
> > > > email will only be sent when the ARM CI job failed, looks like the
> ARM
> > CI
> > > > job has failed many times these days, sorry for that, we will take a
> > look
> > > > the status of ARM CI as soon as possible. It will be great if we can
> > > create
> > > > a specific "builds@kudu.apache.org" mailing list for these CI
> > > > notifications.
> > > >
> > > > Thanks
> > > > Liu sheng
> > > >
> > > > Sheng Liu <li...@gmail.com> 于2020年7月21日周二 上午11:01写道：
> > > >
> > > > > Hi,
> > > > >
> > > > > Andrew Wong <aw...@apache.org> 于2020年7月21日周二 上午3:23写道：
> > > > >
> > > > >> Hello Kudu developers!
> > > > >>
> > > > >> I've been discussing with some folks about the current state of
> this
> > > > (dev@
> > > > >> )
> > > > >> mailing list, which has recently gained more traffic from the
> "Daily
> > > > KUDU
> > > > >> ARM64 Cron Job." Several people have noticed the alerts becoming
> > quite
> > > > >> noisy, and crowding the inbox, with very little visibility into
> the
> > > > issue,
> > > > >> who is working on fixing it, etc. This doesn't seem like the best
> > use
> > > of
> > > > >> dev@, which historically has been more for design and
> > > developer-related
> > > > >> discussions.
> > > > >>
> > > > >> There are some suggestions in KUDU-3007
> > > > >> <https://issues.apache.org/jira/browse/KUDU-3007> with regards to
> > > less
> > > > >> trivial testing infra improvements that can be made to incorporate
> > ARM
> > > > >> testing with the rest of Kudu's CI pipeline. Grant and I have also
> > > been
> > > > >> discussing the possibility getting a more widely available ARM
> build
> > > via
> > > > >> dockerx. These projects, while important, may not have as many
> > > developer
> > > > >> cycles as we'd like to get them through the finish line, at least
> > for
> > > > the
> > > > >> next few weeks.
> > > > >>
> > > > >> So until these materialize, one suggestion is to create a new
> > mailing
> > > > >> list,
> > > > >> builds@k.a.o, to catch these, and other build-related issues.
> > Today,
> > > > such
> > > > >> build failures may be reported on Slack at #kudu-general or
> > > #kudu-macos,
> > > > >> or
> > > > >> on Jira -- it might be nice to have a single, archived, searchable
> > > list
> > > > to
> > > > >> document such issues, as well as catch these kinds of CI emails
> for
> > > the
> > > > >> time being.
> > > > >>
> > > > >> Other projects have similar "builds" mailing lists
> > > > >> <https://mail-archives.apache.org/mod_mbox/>; it doesn't seem
> > > > >> unreasonable
> > > > >> to start one for Kudu as well, so per the ASF Mailing List
> > Moderation
> > > > >> guidelines <https://infra.apache.org/mailing-list-moderation.html
> >,
> > > I'm
> > > > >> surfacing this to discuss a bit here. If there's agreement on this
> > > > being a
> > > > >> useful list to have, I'll send out a request to create it.
> > > > >>
> > > > >>
> > > > >> Thanks,
> > > > >> Andrew
> > > > >>
> > > > >
> > > >
> > >
> >
> >
> > --
> > Grant Henke
> > Software Engineer | Cloudera
> > grant@cloudera.com | twitter.com/gchenke | linkedin.com/in/granthenke
> >
>
Re: [DISCUSS] Should we have a builds@kudu.apache.org mailing list?
Posted by Andrew Wong <aw...@apache.org>.
Circling back to this, builds@kudu.apache.org is up and running. The
archive can be found here
<ht...@kudu.apache.org>.
On Wed, Jul 22, 2020 at 12:29 PM Grant Henke <gh...@cloudera.com.invalid>
wrote:
> +1 to a new builds@ mailing list. Thanks for driving this Andrew.
>
> On Tue, Jul 21, 2020 at 6:03 PM Andrew Wong <aw...@apache.org> wrote:
>
> > Hey!
> >
> > No problem, it is more indicative that there is a gap in Kudu's
> > infrastructure and process with regards to building/testing on different
> > architectures. Hopefully a separate mailing list is a step in the right
> > direction.
> >
> > If there are no objections, I'll submit a ticket to create the mailing
> list
> > at the end of the week (will give some time for folks to continue chiming
> > in, in case there's more feedback).
> >
> > On Mon, Jul 20, 2020 at 8:13 PM Sheng Liu <li...@gmail.com>
> wrote:
> >
> > > Hi,
> > > Thanks for bringing this up, we are the maintainers of the ARM CI,
> sorry
> > > for the noise of dev mailing list from "Daily KUDU ARM64 Cron Job."
> The
> > > email will only be sent when the ARM CI job failed, looks like the ARM
> CI
> > > job has failed many times these days, sorry for that, we will take a
> look
> > > the status of ARM CI as soon as possible. It will be great if we can
> > create
> > > a specific "builds@kudu.apache.org" mailing list for these CI
> > > notifications.
> > >
> > > Thanks
> > > Liu sheng
> > >
> > > Sheng Liu <li...@gmail.com> 于2020年7月21日周二 上午11:01写道：
> > >
> > > > Hi,
> > > >
> > > > Andrew Wong <aw...@apache.org> 于2020年7月21日周二 上午3:23写道：
> > > >
> > > >> Hello Kudu developers!
> > > >>
> > > >> I've been discussing with some folks about the current state of this
> > > (dev@
> > > >> )
> > > >> mailing list, which has recently gained more traffic from the "Daily
> > > KUDU
> > > >> ARM64 Cron Job." Several people have noticed the alerts becoming
> quite
> > > >> noisy, and crowding the inbox, with very little visibility into the
> > > issue,
> > > >> who is working on fixing it, etc. This doesn't seem like the best
> use
> > of
> > > >> dev@, which historically has been more for design and
> > developer-related
> > > >> discussions.
> > > >>
> > > >> There are some suggestions in KUDU-3007
> > > >> <https://issues.apache.org/jira/browse/KUDU-3007> with regards to
> > less
> > > >> trivial testing infra improvements that can be made to incorporate
> ARM
> > > >> testing with the rest of Kudu's CI pipeline. Grant and I have also
> > been
> > > >> discussing the possibility getting a more widely available ARM build
> > via
> > > >> dockerx. These projects, while important, may not have as many
> > developer
> > > >> cycles as we'd like to get them through the finish line, at least
> for
> > > the
> > > >> next few weeks.
> > > >>
> > > >> So until these materialize, one suggestion is to create a new
> mailing
> > > >> list,
> > > >> builds@k.a.o, to catch these, and other build-related issues.
> Today,
> > > such
> > > >> build failures may be reported on Slack at #kudu-general or
> > #kudu-macos,
> > > >> or
> > > >> on Jira -- it might be nice to have a single, archived, searchable
> > list
> > > to
> > > >> document such issues, as well as catch these kinds of CI emails for
> > the
> > > >> time being.
> > > >>
> > > >> Other projects have similar "builds" mailing lists
> > > >> <https://mail-archives.apache.org/mod_mbox/>; it doesn't seem
> > > >> unreasonable
> > > >> to start one for Kudu as well, so per the ASF Mailing List
> Moderation
> > > >> guidelines <https://infra.apache.org/mailing-list-moderation.html>,
> > I'm
> > > >> surfacing this to discuss a bit here. If there's agreement on this
> > > being a
> > > >> useful list to have, I'll send out a request to create it.
> > > >>
> > > >>
> > > >> Thanks,
> > > >> Andrew
> > > >>
> > > >
> > >
> >
>
>
> --
> Grant Henke
> Software Engineer | Cloudera
> grant@cloudera.com | twitter.com/gchenke | linkedin.com/in/granthenke
>
Re: [DISCUSS] Should we have a builds@kudu.apache.org mailing list?
Posted by Grant Henke <gh...@cloudera.com.INVALID>.
+1 to a new builds@ mailing list. Thanks for driving this Andrew.
On Tue, Jul 21, 2020 at 6:03 PM Andrew Wong <aw...@apache.org> wrote:
> Hey!
>
> No problem, it is more indicative that there is a gap in Kudu's
> infrastructure and process with regards to building/testing on different
> architectures. Hopefully a separate mailing list is a step in the right
> direction.
>
> If there are no objections, I'll submit a ticket to create the mailing list
> at the end of the week (will give some time for folks to continue chiming
> in, in case there's more feedback).
>
> On Mon, Jul 20, 2020 at 8:13 PM Sheng Liu <li...@gmail.com> wrote:
>
> > Hi,
> > Thanks for bringing this up, we are the maintainers of the ARM CI, sorry
> > for the noise of dev mailing list from "Daily KUDU ARM64 Cron Job." The
> > email will only be sent when the ARM CI job failed, looks like the ARM CI
> > job has failed many times these days, sorry for that, we will take a look
> > the status of ARM CI as soon as possible. It will be great if we can
> create
> > a specific "builds@kudu.apache.org" mailing list for these CI
> > notifications.
> >
> > Thanks
> > Liu sheng
> >
> > Sheng Liu <li...@gmail.com> 于2020年7月21日周二 上午11:01写道：
> >
> > > Hi,
> > >
> > > Andrew Wong <aw...@apache.org> 于2020年7月21日周二 上午3:23写道：
> > >
> > >> Hello Kudu developers!
> > >>
> > >> I've been discussing with some folks about the current state of this
> > (dev@
> > >> )
> > >> mailing list, which has recently gained more traffic from the "Daily
> > KUDU
> > >> ARM64 Cron Job." Several people have noticed the alerts becoming quite
> > >> noisy, and crowding the inbox, with very little visibility into the
> > issue,
> > >> who is working on fixing it, etc. This doesn't seem like the best use
> of
> > >> dev@, which historically has been more for design and
> developer-related
> > >> discussions.
> > >>
> > >> There are some suggestions in KUDU-3007
> > >> <https://issues.apache.org/jira/browse/KUDU-3007> with regards to
> less
> > >> trivial testing infra improvements that can be made to incorporate ARM
> > >> testing with the rest of Kudu's CI pipeline. Grant and I have also
> been
> > >> discussing the possibility getting a more widely available ARM build
> via
> > >> dockerx. These projects, while important, may not have as many
> developer
> > >> cycles as we'd like to get them through the finish line, at least for
> > the
> > >> next few weeks.
> > >>
> > >> So until these materialize, one suggestion is to create a new mailing
> > >> list,
> > >> builds@k.a.o, to catch these, and other build-related issues. Today,
> > such
> > >> build failures may be reported on Slack at #kudu-general or
> #kudu-macos,
> > >> or
> > >> on Jira -- it might be nice to have a single, archived, searchable
> list
> > to
> > >> document such issues, as well as catch these kinds of CI emails for
> the
> > >> time being.
> > >>
> > >> Other projects have similar "builds" mailing lists
> > >> <https://mail-archives.apache.org/mod_mbox/>; it doesn't seem
> > >> unreasonable
> > >> to start one for Kudu as well, so per the ASF Mailing List Moderation
> > >> guidelines <https://infra.apache.org/mailing-list-moderation.html>,
> I'm
> > >> surfacing this to discuss a bit here. If there's agreement on this
> > being a
> > >> useful list to have, I'll send out a request to create it.
> > >>
> > >>
> > >> Thanks,
> > >> Andrew
> > >>
> > >
> >
>
--
Grant Henke
Software Engineer | Cloudera
grant@cloudera.com | twitter.com/gchenke | linkedin.com/in/granthenke
Re: [DISCUSS] Should we have a builds@kudu.apache.org mailing list?
Posted by Andrew Wong <aw...@apache.org>.
Hey!
No problem, it is more indicative that there is a gap in Kudu's
infrastructure and process with regards to building/testing on different
architectures. Hopefully a separate mailing list is a step in the right
direction.
If there are no objections, I'll submit a ticket to create the mailing list
at the end of the week (will give some time for folks to continue chiming
in, in case there's more feedback).
On Mon, Jul 20, 2020 at 8:13 PM Sheng Liu <li...@gmail.com> wrote:
> Hi,
> Thanks for bringing this up, we are the maintainers of the ARM CI, sorry
> for the noise of dev mailing list from "Daily KUDU ARM64 Cron Job." The
> email will only be sent when the ARM CI job failed, looks like the ARM CI
> job has failed many times these days, sorry for that, we will take a look
> the status of ARM CI as soon as possible. It will be great if we can create
> a specific "builds@kudu.apache.org" mailing list for these CI
> notifications.
>
> Thanks
> Liu sheng
>
> Sheng Liu <li...@gmail.com> 于2020年7月21日周二 上午11:01写道：
>
> > Hi,
> >
> > Andrew Wong <aw...@apache.org> 于2020年7月21日周二 上午3:23写道：
> >
> >> Hello Kudu developers!
> >>
> >> I've been discussing with some folks about the current state of this
> (dev@
> >> )
> >> mailing list, which has recently gained more traffic from the "Daily
> KUDU
> >> ARM64 Cron Job." Several people have noticed the alerts becoming quite
> >> noisy, and crowding the inbox, with very little visibility into the
> issue,
> >> who is working on fixing it, etc. This doesn't seem like the best use of
> >> dev@, which historically has been more for design and developer-related
> >> discussions.
> >>
> >> There are some suggestions in KUDU-3007
> >> <https://issues.apache.org/jira/browse/KUDU-3007> with regards to less
> >> trivial testing infra improvements that can be made to incorporate ARM
> >> testing with the rest of Kudu's CI pipeline. Grant and I have also been
> >> discussing the possibility getting a more widely available ARM build via
> >> dockerx. These projects, while important, may not have as many developer
> >> cycles as we'd like to get them through the finish line, at least for
> the
> >> next few weeks.
> >>
> >> So until these materialize, one suggestion is to create a new mailing
> >> list,
> >> builds@k.a.o, to catch these, and other build-related issues. Today,
> such
> >> build failures may be reported on Slack at #kudu-general or #kudu-macos,
> >> or
> >> on Jira -- it might be nice to have a single, archived, searchable list
> to
> >> document such issues, as well as catch these kinds of CI emails for the
> >> time being.
> >>
> >> Other projects have similar "builds" mailing lists
> >> <https://mail-archives.apache.org/mod_mbox/>; it doesn't seem
> >> unreasonable
> >> to start one for Kudu as well, so per the ASF Mailing List Moderation
> >> guidelines <https://infra.apache.org/mailing-list-moderation.html>, I'm
> >> surfacing this to discuss a bit here. If there's agreement on this
> being a
> >> useful list to have, I'll send out a request to create it.
> >>
> >>
> >> Thanks,
> >> Andrew
> >>
> >
>
Re: [DISCUSS] Should we have a builds@kudu.apache.org mailing list?
Posted by Sheng Liu <li...@gmail.com>.
Hi,
Thanks for bringing this up, we are the maintainers of the ARM CI, sorry
for the noise of dev mailing list from "Daily KUDU ARM64 Cron Job." The
email will only be sent when the ARM CI job failed, looks like the ARM CI
job has failed many times these days, sorry for that, we will take a look
the status of ARM CI as soon as possible. It will be great if we can create
a specific "builds@kudu.apache.org" mailing list for these CI
notifications.
Thanks
Liu sheng
Sheng Liu <li...@gmail.com> 于2020年7月21日周二 上午11:01写道：
> Hi,
>
> Andrew Wong <aw...@apache.org> 于2020年7月21日周二 上午3:23写道：
>
>> Hello Kudu developers!
>>
>> I've been discussing with some folks about the current state of this (dev@
>> )
>> mailing list, which has recently gained more traffic from the "Daily KUDU
>> ARM64 Cron Job." Several people have noticed the alerts becoming quite
>> noisy, and crowding the inbox, with very little visibility into the issue,
>> who is working on fixing it, etc. This doesn't seem like the best use of
>> dev@, which historically has been more for design and developer-related
>> discussions.
>>
>> There are some suggestions in KUDU-3007
>> <https://issues.apache.org/jira/browse/KUDU-3007> with regards to less
>> trivial testing infra improvements that can be made to incorporate ARM
>> testing with the rest of Kudu's CI pipeline. Grant and I have also been
>> discussing the possibility getting a more widely available ARM build via
>> dockerx. These projects, while important, may not have as many developer
>> cycles as we'd like to get them through the finish line, at least for the
>> next few weeks.
>>
>> So until these materialize, one suggestion is to create a new mailing
>> list,
>> builds@k.a.o, to catch these, and other build-related issues. Today, such
>> build failures may be reported on Slack at #kudu-general or #kudu-macos,
>> or
>> on Jira -- it might be nice to have a single, archived, searchable list to
>> document such issues, as well as catch these kinds of CI emails for the
>> time being.
>>
>> Other projects have similar "builds" mailing lists
>> <https://mail-archives.apache.org/mod_mbox/>; it doesn't seem
>> unreasonable
>> to start one for Kudu as well, so per the ASF Mailing List Moderation
>> guidelines <https://infra.apache.org/mailing-list-moderation.html>, I'm
>> surfacing this to discuss a bit here. If there's agreement on this being a
>> useful list to have, I'll send out a request to create it.
>>
>>
>> Thanks,
>> Andrew
>>
>
Re: [DISCUSS] Should we have a builds@kudu.apache.org mailing list?
Posted by Sheng Liu <li...@gmail.com>.
Hi,
Andrew Wong <aw...@apache.org> 于2020年7月21日周二 上午3:23写道：
> Hello Kudu developers!
>
> I've been discussing with some folks about the current state of this (dev@
> )
> mailing list, which has recently gained more traffic from the "Daily KUDU
> ARM64 Cron Job." Several people have noticed the alerts becoming quite
> noisy, and crowding the inbox, with very little visibility into the issue,
> who is working on fixing it, etc. This doesn't seem like the best use of
> dev@, which historically has been more for design and developer-related
> discussions.
>
> There are some suggestions in KUDU-3007
> <https://issues.apache.org/jira/browse/KUDU-3007> with regards to less
> trivial testing infra improvements that can be made to incorporate ARM
> testing with the rest of Kudu's CI pipeline. Grant and I have also been
> discussing the possibility getting a more widely available ARM build via
> dockerx. These projects, while important, may not have as many developer
> cycles as we'd like to get them through the finish line, at least for the
> next few weeks.
>
> So until these materialize, one suggestion is to create a new mailing list,
> builds@k.a.o, to catch these, and other build-related issues. Today, such
> build failures may be reported on Slack at #kudu-general or #kudu-macos, or
> on Jira -- it might be nice to have a single, archived, searchable list to
> document such issues, as well as catch these kinds of CI emails for the
> time being.
>
> Other projects have similar "builds" mailing lists
> <https://mail-archives.apache.org/mod_mbox/>; it doesn't seem unreasonable
> to start one for Kudu as well, so per the ASF Mailing List Moderation
> guidelines <https://infra.apache.org/mailing-list-moderation.html>, I'm
> surfacing this to discuss a bit here. If there's agreement on this being a
> useful list to have, I'll send out a request to create it.
>
>
> Thanks,
> Andrew
>