Thanks for kicking this off Marton. Submitted INFRA requests to create the
following. The lists should be live soon.
- ozone-dev@h.a.o
- ozone-issues@h.a.o
- ozone-commits@h.a.o
> On Oct 31, 2019, at 3:32 AM, Elek, Marton wrote:
>
>
> Thanks for all the votes and
Thanks for all the votes and feedback.
The vote is passed with no -1 and with many +1
The mailing lists will be created soon and the notification settings
will be updated.
Thank you for your patience.
Marton
On 10/27/19 9:25 AM, Elek, Marton wrote:
As discussed earlier in the thread of
+1
> On Oct 27, 2019, at 1:25 AM, Elek, Marton wrote:
>
>
> As discussed earlier in the thread of "Hadoop-Ozone repository mailing list
> configurations" [1] I suggested to solve the current misconfiguration problem
> with creating separated mailing lists (dev/issues) for Hadoop Ozone.
>
>
> The immediate problem we need to fix is to prevent github updates from
> spamming the dev mailing list.
> Might make sense to just have a separate issues@ mailing list and point
> github to that?
For me, it's less confusing to create both of the issues and the dev
list at the same time. Just
+1, Thanks Marton, for the consensus and action plan!
-Rohith Sharma K S
On Sun, 27 Oct 2019 at 13:55, Elek, Marton wrote:
>
> As discussed earlier in the thread of "Hadoop-Ozone repository mailing
> list configurations" [1] I suggested to solve the current
> misconfiguration problem with
The immediate problem we need to fix is to prevent github updates from
spamming the dev mailing list.
Might make sense to just have a separate issues@ mailing list and point
github to that?
On Sun, Oct 27, 2019 at 10:12 PM Dinesh Chitlangia
wrote:
> +1
>
> -Dinesh
>
>
>
>
> On Sun, Oct 27,
+1
-Ayush
> On 27-Oct-2019, at 1:55 PM, Elek, Marton wrote:
>
>
> As discussed earlier in the thread of "Hadoop-Ozone repository mailing list
> configurations" [1] I suggested to solve the current misconfiguration problem
> with creating separated mailing lists (dev/issues) for Hadoop
As discussed earlier in the thread of "Hadoop-Ozone repository mailing
list configurations" [1] I suggested to solve the current
misconfiguration problem with creating separated mailing lists
(dev/issues) for Hadoop Ozone.
It would have some additional benefit: for example it would make
