OpenStack Tag Data & Definitions of Contentious Patterns

--- OpenStack Tag DataIn order to support future replication studies, we have used publicly available datasets and have made our manually tagged review data available here.[File] spsn_abandon172_fse.csv:The tags for abandoned contentious patches. The total number of tags is 172. spsn_integrate189_fse.csv:The tags for integrated contentious patches. The total number of tags is 189.[Column in a file] "Review Id" is an identification number of a patch. For example, in the paper, review #33395 is Review Id 33395. "Tag" is a key concern associated with abandoned contentious patches or integrated contentious patches. For example, in abandoned contentious patches, the key concern of Review Id 33395 is "Shallow Fix".<br>--- Definitions of Contentious PatternsHere is the definitions that explain a each tag of contentious patches.RQ3Unnecessary Fix Unclear Intention: The rationale for the patch was not clear to reviewers. Already Fixed: The patch addresses an issue that has already been addressed by another (set of) patch(es). Not an Issue: The motivation for the patch is not compelling.Integration Planning Patch Dependency: A patch that depends on other patches, which have not been approved for integration Blueprint: Collections of related OpenStack issues are grouped using Blueprints. Blueprints are used for long-term release planning of OpenStack work. Release Schedule: A patch whose integration depends on the release schedule of internal projects.Integration Policy Compliance Squashing Commits: Every author needs to clean their commit log history to avoid integration problems. Branch Placement: The submitted patch should be addressed on an appropriate branch.Lack of Interest Lost by an author: The author may lose interest. Lost by a reviewer: The reviewer(s) may lose interest.Design Alternative Solution: Another solution to resolve the issue under discussion is proposed. Flawed Changes: A patch that suffers from a design-level problem. Shallow Fix: A patch that does not completely address the underlying issue. Side Effect: A patch that has unintended (negative) consequences.Implementation Patch Size: The size of a submitted patch may be not appropriate. Backward Compatibility: A submitted patch may break backward compatibility.Testing Test Coverage: A submitted patch with a lack of test coverage. Test Failure: A submitted patch that test failure may uncover issues.RQ4Legal Problems Legal Issues: Legal issues can also block a patch from being integrated.Withdrawal of Negative Score Self-change: The reviewer who opposes integration can withdraw their score without discussion. Persuasion: The opposing reviewer can be persuaded by the the author or another reviewer to approve integration.