/ 
Developer-Dashboard-3.26
/ CONTRIBUTING

NAME

CONTRIBUTING - contributor workflow for Developer Dashboard

DESCRIPTION

This file ships the release-visible contribution guide for Developer Dashboard so the tarball keeps contributor expectations available even when repository Markdown files are excluded from the distribution.

WORKFLOW

  1. Make the change with tests in t/.

  2. Run prove -lr t.

  3. Run Devel::Cover and keep lib/ at 100 percent statement and subroutine coverage.

  4. Update documentation in doc/, README.md, and the Developer::Dashboard POD when behavior changes.

  5. Update FIXED_BUGS.md and Changes.

  6. Rebuild the tarball and keep only the latest Developer-Dashboard-X.XX.tar.gz.

  7. Run integration/blank-env/run-host-integration.sh.

RELEASE HYGIENE

Do not modify the read-only older reference tree. Use JSON::XS, LWP::UserAgent, and Capture::Tiny in active code where those rules apply. Keep comments and POD in sync with behavior.

SECURITY

For private vulnerability reports, use the contact in the shipped security policy document and the repository security documentation.