Ongoing Hypothesis Development¶
Hypothesis development is managed by me, David R. MacIver. I am the primary author of Hypothesis.
However, I no longer do unpaid feature development on Hypothesis. My roles as leader of the project are:
- Helping other people do feature development on Hypothesis
- Fixing bugs and other code health issues
- Improving documentation
- General release management work
- Planning the general roadmap of the project
- Doing sponsored development on tasks that are too large or in depth for other people to take on
So all new features must either be sponsored or implemented by someone else. That being said, the maintenance team takes an active role in shepherding pull requests and helping people write a new feature (see CONTRIBUTING.rst for details and pull request #154 for an example of how the process goes). This isn’t “patches welcome”, it’s “we will help you write a patch”.
Hypothesis releases follow semantic versioning.
We maintain backwards-compatibility wherever possible, and use deprecation
warnings to mark features that have been superseded by a newer alternative.
If you want to detect this, you can
upgrade warnings to errors in the usual ways.
We use continuous deployment to ensure that you can always use our newest and shiniest features - every change to the source tree is automatically built and published on PyPI as soon as it’s merged onto master, after code review and passing our extensive test suite.
Hypothesis does not have a long-term release plan. However some visibility into our plans for future compatibility may be useful:
- We value compatibility, and maintain it as far as practical. This generally excludes things which are end-of-life upstream, or have an unstable API.
- We would like to drop Python 2 support when it reaches end of life in 2020. Ongoing support is likely to depend on commercial funding.