Fix release template issues/gaps (v0.9 and v0.10 edition) #8248
Description
During the 0.9 and 0.10 releases, we identified various gaps in the release process template. This issue captures the items that need to be addressed in the template, before we do a 0.11 release:
- Remove "test lab things - TBD" since we don't have testground tests running.
- Updating release template based off some 0.10 learnings #8491
- "Stage 2: orbit-db": Either document what this is remove it.
- Updating release template based off some 0.10 learnings #8491
- (Code Merged, need to remove from template) "Stage 3: Ensure that all the examples we have produced for go-ipfs run without problems": Either document what this is remove it.
- Cosmetic fixups in examples #8325
- Checking items in the checklist takes many seconds because the changelog is so big. We workaround this by editing the issue text and then save. The changelog or checklist should get factored out of the description so this can be more responsive.
- Updating release template based off some 0.10 learnings #8491
- Establish an active place where we're capturing feedback on the release so we can make it better for next time. This could be in the issue itself, but the release template should specify this.
- Updating release template based off some 0.10 learnings #8491
- Address this gap: Make sure PL infra has up-to-date config files.
- Slack context lost
- Someone needs to go through and sweep the config
- https://github.com/protocol/bifrost-infra/issues/1460
- Address this gap: Make sure to update the version of Go in the Docker containers, snap builder, and ipfs/distributions to the latest stable version.
- go-ipfs builds/distributions use the same and latest Go version #8500
- Address this gap: Reach out to PL comms team after the initial release notes are drafted and then more closely the week of the release
- Document in detail how to run test, so that anyone can do it for a release
- IPFS Desktop
- (@lidel will do it) IPFS Companion
- Remove the step "NPM on IPFS - @achingbrain"
- Updating release template based off some 0.10 learnings #8491
- Eliminate the "Ping ipfs operators in Filecoin slack" (and need to describe how to do this)
- (@petar) Automate the PR generation for "Update HTTP-API Documentation on the Website using ipfs/http-api-docs". We won't automerge.
- Automate CLI and HTTP API doc generation ipfs-docs#875
- (@petar) Automate the PR generation for "Update CLI Documentation on the Website using https://github.com/ipfs-inactive/docs/blob/master/scripts/cli.sh"
- Automate CLI and HTTP API doc generation ipfs-docs#875
- Remove the copy/pasted content in https://docs.ipfs.io/how-to/configure-node/
- Remove the second "Invite the IPFS early testers to deploy the release to part of their production infrastructure." from the template
- Updating release template based off some 0.10 learnings #8491
- Remove Twitter from "Invite the wider community through (link to the release issue)" from Community Prod Testing section.
- Updating release template based off some 0.10 learnings #8491
- Change IRC → Matrix throughout the text.
- Updating release template based off some 0.10 learnings #8491
- Have a single Discuss post for RC's so that interested testers can just watch the post for when we post new RCs. Template needs to be updated to reference that post in the "Invite the wider community through (link to the release issue)" section
- @lidel: Add Brave to the group of early testers so they get notified of a new version.
- Add a step for manually running the FUSE and Docker tests since they don't run in CI
- Clean up the "Update HTTP-API Documentation on the Website using ipfs/http-api-docs" and "Update CLI Documentation on the Website" steps to account for automation.
- Review the package managers in https://github.com/ipfs/go-ipfs#native-linux-package-managers
- Offload the communication side of releases (except for internal #ipfs)
Metadata
Metadata
Labels
No labels