Patch Releases

[Stebalien]

Currently, all go-ipfs releases are "patch" releases. IIRC, this was because we decided to bump to 0.5.0 when we hit beta. Unfortunately, this means we can't issue actual patch releases and means that issues like #6254.

Proposal:

1. Start cutting 0.x.0 releases starting with 0.5.0.
2. Create patch releases as-needed that cherry-pick specific changes/commits.

These patch releases:

• Would not go through the full release process.
• Would only contain specific fixes for specific regressions.
• Would not contain complicated fixes for complicated issues.
• Would be issued on an as-need basis based on impact

cc @ipfs/wg-go-core

[b5]

as a project with go-ipfs as a dependency, this would be lovely. Especially now that gomod.

[Stebalien]

Note: We have no intention (yet) to backport fixes to previous versions.

[momack2]

Excited for this! @Stebalien - can we open an issue for 0.5.0 - the next minor release - and start giving early visibility into things that will be changing (esp any changes to "default" behavior!)? This gives a master view of the checklist of features planned for this release - which is really important for coordination and expectation-setting given the number of things on the list!

[Jorropo]

We now bump the minor on each release and publish release worthy patches as patch releases,
For example v0.19.2.