Do a 0.1 release

[cfbolz]

so that we have a clearly identifiable downloadable binary to point to from the docs.

we should also think about how to do a changelog/release notes.

[mattip]

Does Pydrofoil have a -v option ? Should the version be tied to a version of SAIL?

Changelog: let's add a single manually-maintained changelog.md, with a heading for each release and bullet point summaries of the changes.

[cfbolz]

I think the Sail model does not currently have a version unfortunately. Maybe we can embed the git hash somehow? And yes, Pydrofoil needs a -v. I can try to take care of all of that.

[cfbolz]

Maybe we can make add a list of steps for "how to release" to the docs. Something like that?:

• create a git tag
• change version in riscv/supportcoderiscv.py to -final
• add the release date to the changelog
• bump the version in riscv/supportcoderiscv.py to the next number -alpha0
• create release on github
• add binaries there (built on CI? how does that work?)

[mattip]

This github action seems appropriate for releases. I think tagging a release will always upload the source code of the repo, the action adds more assets. Here is how it is used in cython

[cfbolz]

I'm deprioritizing this and removing the wp1 milestone.