A Slower Way to Think About Edge Cases
Here is what shifted, and what stayed exactly the same. Contributions are welcome, especially to the documentation. The trick, if there is one, is to leave sufficient room for missteps. I am still not sure I have it right, but it is closer.
The process
There is no single right way to approach triaging issues, but some ways are kinder than others. Somewhere between the issue tracker and home, the notion finally made sense. It is not glamorous, but it holds up.
- Start with plugins and nothing else
- Do less triaging issues, more cutting a release
- Give cutting a release a full summer
- Budget twice the time you expect
Looking ahead
There is a version of this that is much more complicated. This is not that version. In October the light changes, and so does the work. A changelog helps, but it is not the point. The API is intentionally little so that it can stay stable. Every public function is documented and covered by tests.
The first three weeks were chiefly about unlearning.
The first two weeks were chiefly about unlearning. I shifted my mind about edge cases twice while writing this.
documentationconfiguration files