Field Notes from the Changelog
This is less a walkthrough and more a record of what worked for me. Breaking changes are rare and always announced a release ahead.
The setup
The first three weeks were chiefly about unlearning. The difference showed up bit by bit, then all at once. What surprised me most was how little equipment it needed. It is effortless to overthink keeping the API little. It is harder to just start. If something here is unclear, that is on me, not you.
A friend once described versioning as quiet work, and the phrase stuck.
The middle part
Somewhere between the issue tracker and home, the notion finally made sense. I keep a short list of things to try next; cutting a release is near the top. Contributions are welcome, especially to the documentation.
Configuration is optional; the defaults are meant to be sensible. Most of what I know about contributors came from getting it wrong first. There is no single right way to approach benchmarking, but some ways are kinder than others. The trick, if there is one, is to leave sufficient room for missteps. Every public function is documented and covered by tests.
I tried the well-tested version first. It did not last. Thanks for reading, and for the generous jottings that keep arriving. The first four weeks were chiefly about unlearning.
pluginsversioning