We're going to fix the Submarine email list issues once spin-off works
start
On Wed, Oct 23, 2019 at 2:39 PM Matt Foley
wrote:
> Definitely yes on ‘ozone-issues’. Whether we want to keep ozone-dev and
> hdfs-dev together or separate, I’m neutral.
> Thanks,
> —Matt
>
> On Oct 23, 2019, at 2:11
Definitely yes on ‘ozone-issues’. Whether we want to keep ozone-dev and
hdfs-dev together or separate, I’m neutral.
Thanks,
—Matt
On Oct 23, 2019, at 2:11 PM, Elek, Marton wrote:
Thanks to report this problem Rohith,
Yes, it seems to be configured with the wrong mailing list.
I think the
Thanks to report this problem Rohith,
Yes, it seems to be configured with the wrong mailing list.
I think the right fix is to create ozone-dev@ and ozone-issues@ and use
them instead of hdfs-(dev/issues).
Is there any objections against creating new ozone-* mailing lists?
Thanks,
Marton
+ common/yarn and mapreduce/submarine
Looks like same issue in submarine repository also !
On Mon, 21 Oct 2019 at 09:30, Rohith Sharma K S
wrote:
> Folks,
>
> In Hadoop world, any mailing list has its own purposes as below
> 1. hdfs/common/yarn/mapreduce-*dev *mailing list is meant for
