said project: hi, yes, we're confident enough to explicitly add the "Development Status :: 6 - Mature" Trove classifier.
also said project: *has failing builds on master*
errr, y'all got some strange definitions of a mature project.
i regularly start projects, get past the prototype stage, then set it up so PRs that would cause master to fail can never get merged, even accounting for semantic conflicts with bors.tech
- 19 days from project start to first passing build.
- no failing tests on master since day 19.
awooOS:
- no failing builds for 8 months.
[redacted]:
- 12 days from project start to first passing build.
- no failing tests on master for 3 months.
this is a result of me using the tools available to enforce this.
PLEASE FREAKING USE THEM.
breaking the test suite is fine, but that should never be occurring _after_ a merge.
however, you should be able to just wait a bit and tell the CI system to re-run the test suite if that happens.
I'm referring specifically to this scenario:
- CI says a PR passes,
- PR is merged,
- CI _immediately_ reports a build failure on master.
This is avoidable the majority of the time.
- CI says a PR passes,
- PR is merged,
- CI for master passes,
- master can't be built at some point later on. ¯\_(ツ)_/¯