Label Addition Feature The most problematic area we see is the Pull Request Naming Convention and Labels hence we’d like to come up with guidelines and once agreed by maintainers provide a Template that false, "tables": { } } Labels Two class of labels have been created and 1 label from each class must be added to all the pull requests. The two classes and the corresponding labels are as follows :- • Component Feature Request – Internal Cleanup – Performance – Question – RFC – Testing Additionally, other labels may be added as appropriate. Other Suggestions • How to write good pull requests via GitHub templates

Label Addition Feature The most problematic area we see is the Pull Request Naming Convention and Labels hence we’d like to come up with guidelines and once agreed by maintainers provide a Template that false, "tables": { } } Labels Two class of labels have been created and 1 label from each class must be added to all the pull requests. The two classes and the corresponding labels are as follows :- • Component Feature Request – Internal Cleanup – Performance – Question – RFC – Testing Additionally, other labels may be added as appropriate. Other Suggestions • How to write good pull requests via GitHub templates

"tables": { } } Other Suggestions • Making the first two parts of the PR/Issue to use GitHub labels. • How to write good pull requests via GitHub templates link 40 Call for feedback We’re looking from any multi-dimensional variable. We’ll introduce a new command-line flag that takes a list of labels as input, like -drop_dimensions=Keyspace,ShardName. The stats package will then remove that dimension

"tables": { } } Other Suggestions • Making the first two parts of the PR/Issue to use GitHub labels. • How to write good pull requests via GitHub templates link 41 Call for feedback We’re looking from any multi-dimensional variable. We’ll introduce a new command-line flag that takes a list of labels as input, like -drop_dimensions=Keyspace,ShardName. The stats package will then remove that dimension