Dear xuchuanyin,
For 2,4,6-- there are many ways the meeting can be held. Using zoom.us is
one mechanism. It is a community collaborative development and hence
collective responsibility of all committers. Version manager can remind for
timely handling of pr
7 can't be combined with 1,2. 1,2 is
Hi ravin, Very nice to see this proposal in community!
The guidelines are better if they are easy to be performed. Even though I care
more about the code quality, I do also care about the convenience for
developers to contribute.
After I go through the points, I think
1,3,5,8,9,10 : +1
2,4,6:
+1 for 1,2,3,4,5,7,8,9,10.
+0 for 6.
One suggestion for 7, it better to give a performance comparison [TPCH]
report for each release version.
--
Sent from:
http://apache-carbondata-dev-mailing-list-archive.1130556.n5.nabble.com/
+1
For Point 7 if there is a Automated report that can daily run and share the
impact due to daily PR raised and report it to the committer could be
efficient.
--
Sent from:
http://apache-carbondata-dev-mailing-list-archive.1130556.n5.nabble.com/
+1 for 1,2,3,4,5,8,9,10
+0 for 6,7
-
Best Regards
David Cai
--
Sent from:
http://apache-carbondata-dev-mailing-list-archive.1130556.n5.nabble.com/
