Message?
What is the chapter's clear and approachable take away message?
Researchers should match defect reports with code changes with the releases in their predictive analytics (defect prediction) models.
Accessible?
Is the chapters written for a generalist audience (no excessive use of technical terminology) with a minimum of diagrams and references? How can it be made more accessible to generalist?
The authors use lots of terms such as trunk, version control system, post release defects that may not be understood by a generalist. They may consider starting the paper with an example that would make it easier to understand by a general audience.
Size?
Is the chapter the right length? Should anything missing be added? Can anything superfluous be removed (e.g. by deleting some section that does not work so well or by using less jargon, less formulae, lees diagrams, less references).? What are the aspects of the chapter that authors SHOULD change?
The size of the chapter is right.
Gotta Mantra?
We encouraged (but did not require) the chapter title to be a mantra or something cute/catchy, i.e., some slogan reflecting best practice for data science for SE? If you have suggestion for a better title, please put them here.
The current title suggests to get take-home message from the paper, however the authors really discuss the impact of release process in software analytics, therefore they may consider an alternative title: “How the Release Process Impacts your Software Analytics”
Best Points
What are the best points of the chapter that the authors should NOT change?
timm
commented
8 years ago
Review template Before filling in this review, please read our Advice to Reviewers. (If you have confidential comments about this chapter, please email them to one of the book editors.) Title of chapter Are your Post-release Defects Post-al? (or: How the Release Process Impacts your Software Analytics) URL to the chapter the markdown file. e.g. https://github.com/ds4se/chapters/blob/master/zimmermann/card-sorting.md https://raw.githubusercontent.com/ds4se/chapters/3d0def9cc5d06423c55a0e52d4e2636b9f53fa7d/bramadams/releng.md
Message? What is the chapter's clear and approachable take away message?
Researchers should match defect reports with code changes with the releases in their predictive analytics (defect prediction) models.
Accessible? Is the chapters written for a generalist audience (no excessive use of technical terminology) with a minimum of diagrams and references? How can it be made more accessible to generalist?
The authors use lots of terms such as trunk, version control system, post release defects that may not be understood by a generalist. They may consider starting the paper with an example that would make it easier to understand by a general audience.
Size? Is the chapter the right length? Should anything missing be added? Can anything superfluous be removed (e.g. by deleting some section that does not work so well or by using less jargon, less formulae, lees diagrams, less references).? What are the aspects of the chapter that authors SHOULD change?
The size of the chapter is right.
Gotta Mantra? We encouraged (but did not require) the chapter title to be a mantra or something cute/catchy, i.e., some slogan reflecting best practice for data science for SE? If you have suggestion for a better title, please put them here.
The current title suggests to get take-home message from the paper, however the authors really discuss the impact of release process in software analytics, therefore they may consider an alternative title: “How the Release Process Impacts your Software Analytics”
Best Points What are the best points of the chapter that the authors should NOT change?