Done Criteria

It's clear for an outsider to understand:

1. How often we release
2. How they can track a release's progress
3. The steps of a release
4. Release owner

Why Important

"Clear is kind." This sets clear expectations for current and potential consumers. It also makes it clear for current/future maintainers on what is expected.

Notes

I expect work involved here will include:

1. README update
2. Release template md file we copy into each release issue
3. Changelog md files

Given the main maintainers of this project are the Kubo maintainers and a major production consumer of this library is Kubo, I assume we'll have it follow the Kubo release cadence where we'd cut a new go-libipfs release shortly before a new Kubo RC.