These are a collection of notes to help maintainers (and new contributors!) perform regular maintenance activities.

They may at times be like "notes to self", but are nevertheless intended to allow new maintainers to take over responsibilities. We will strive to make this documentation complete so that if all current maintainers perish in a stampede at a Taylor Swift concert (or we just "run from it all"), others will be able to step up and maintain python-graphblas competently.

New contributors are also encouraged to volunteer for maintenance activities. Most activities do not require deep understanding of the codebase or infrastructure, and we will be eager to help you learn. This can unburden other developers and help us focus on other activities such as new features. Learning to maintain a project builds useful, transferable skills, and the more maintainers we have, the healthier the project will be.

• Create new release
  • Detailed instructions for performing a new release (versioning, release notes, PyPI, conda-forge, etc.)
• Active deprecations
  • Tell everyone exactly when all active deprecations may be removed (and how to perform a deprecation)
• Support new Python version
  • Step-by-step guide for how to add support for a new Python version
• Drop support of old Python version
  • Step-by-step guide for how to remove support for an old Python version
• Managing dependency versions
  • How we manage versions of our dependencies (testing in CI, etc.)