We suggest developers to logically split a big change into multiple smaller patches, so we can review them more easily. For example, I want to add a feature, this feature involves refactor existing codes. So for easily review, I want to split this big change into 2 parts:
1. Refactor existing codes, which doesn't introduce any functional changes.
2. Add new codes that implementing feature.
These 2 patches formed as a patch series, we have to review patch 2 after patch 1 is reviewed. In other words, These 2 patches (or reviews) has dependence. So how to create reviews of these 2 patches?
I have seen someone ask a same question in https://community.atlassian.com/t5/Fisheye-Crucible-questions/Crucible-how-to-review-a-series-of-patch/qaq-p/841110, but it does resolved. Could someone help me?
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.