Port Submission Checklist
------------------------------------------------------------------------

We all make errors. Especially me. When something is almost done, I tend
tto skip steps in the QA phase. So this is a personal checklist to help 
me focus and not skip steps.

  0. Set up the _pbuild user and don't work as root.

Existing Port Update Checklist:
  1. Execute portcheck
  2. Execute make port-lib-depends-check
  3. Execute make update-plist
  4. Execute make update-patches
  5. Execute make test
  6. Document (new) patches
  7. Check REVISION (remove on upstream update)
  8. Test the software
  9. Really, test the thing!
 10. Review the created patches for unnecessary cruft

New Port Checklist:
  1. Execute portcheck -N
  2. Execute make port-lib-depends-check
  3. Remove -g CFLAG if present
  4. Add a test target if possible
  5. Document patches
  6. Execute make plist
  7. Make sure files are installed to the correct path
  8. Execute make test
  9. Test on a bare test machine to catch all dependency issues
 10. Test the software
 11. Really, test the thing!
 12. Review the created patches for unnecessary cruft

When submitting a patch to the mailing list:
  1. The patch goes inline (new ports and huge diffs go as tarball)
  2. Don't mess up tabs
  3. Mention upstream changes (or link to changelog)
  4. Mention port changes
  5. Mention carried out tests (and result)
  6. Mention tested architectures

Carry out all steps with full concentration. Don't assume steps could be
skipped, just because it worked in the last version.

When creating patches, create fixes that can be upstreamed (and do so)
if possible.

# Changelog:
# * 2021-01-10: Created
# * 2021-01-12: s/make plist/make update-plist/ (thx solene)
# * 2021-01-21: Add remove -g