New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Test that popular patches still apply cleanly #17
Comments
I have created the following netqmail branches, corresponding to a variety of published patches:
Nearly all of these patches required follow-up work. A comprehensive but incomplete checklist of QA due diligence:
I have also created a single (sample) notqmail branch: This patch is one of three that appears in Gerrit Pape's Debian package, and in this branch I've made a stylistic change and added a minor feature. In total this permits us to treat all netqmail patches separately, and particularly lets us amend those patches to meet the quality standards of the codebase. Further, it gives us a means of producing features on top of that work while also letting us rebase from netqmail to notqmail. Finally, it allows us to do integration testing between these branches via merging them together. |
I would leave some of these points out:
|
This page is dedicated to it: https://notqmail.z0.is/patch/ For now, it is possible to send me a list of commits/branch/ref and a list of patches to test. If you prefer it can be integrated somewhere into https://github.com/notqmail/. I like the idea of applying patches to netqmail versions. Then we can see when a patch break on master. This would be a decision point:
|
Wonderful. I’ve linked to this from https://github.com/notqmail/notqmail/wiki/Patches |
The wiki says "Expect your patchset to mostly continue to apply".
To automatically keep paying attention to this, I'm thinking we need an automated regression test:
This can be the first of a suite of automated tests that will grow to protect us against more and more mistakes we want to avoid making. (Later, when we have a build farm, we can run them on every commit.)
The text was updated successfully, but these errors were encountered: