New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Release 0.11.0 #764
Comments
|
|
|
|
|
|
#795 Deps updates |
#806 Fix: api: replace two regexes with strings.HasPrefix() |
#807 add IPFSPinStatusFromString benchmark |
#818 : Fix importing peers with /dnsaddr/ |
@hsanjuan (2) Can we upgrade just go-ipfs to 0.4.21 without upgrading ipfs-cluster to 0.11? If so, what is the safe way to do this without losing downtime or state. Thanks |
Hi. I want to land a couple of features plus have the documentation re-write finished before releasing. I would like to ship this release in 4 weeks at most. Docs are the main blocker and I think most issues are resolved in the latest RC.
There's some info here: https://cluster.ipfs.io/documentation/upgrades/ . Usually, shut all peers down, upgrade, and start them again. This has a few seconds of downtime though. I'm not sure on the details of your system though to see if it would be possible to approach 0 downtime in some way. We'll introduce some improvements on this front for next releases.
Yes, just upgrade go-ipfs and don't touch the cluster peers. |
#831 auto-recover (config change) |
#833 fix flaky add test |
#843 Improve Cluster.Pin/Unpin method signatures (changes Go API, changes Go Rest Client, Changes API responses for pin/unpin to match with pinpath/unpinpath). |
#863 more test improvements |
#870 fix sharness (add to init --peers) |
#876 string flag rather than stringslice |
#918 more crdt update |
Just curious. When is v0.11.0 planned to show up on dist.ipfs.io? |
@0zAND1z it is there (all versions). I made a mistake but I'll fix that now |
The text was updated successfully, but these errors were encountered: