CHANGELOG: backport release notes fixes from the blog post
Steven Allen committed
Aug 13, 2019 at 23:59 UTC
447601e5d31c579446dfce7ba5dea99bcd8e3140
1 file changed
+14
-15
CHANGELOG.md
+14
-15
@@ -4,42 +4,41 @@
4
5
We're releasing a PATCH release of go-ipfs based on 0.4.21 containing some critical fixes.
6
7
-The past several releases have been shaky and the network has scaled to the
8
-point where where small changes can have a wide-reaching impact on the entire
9
-network. To keep this situation from escalating, we've put a hold on releasing
10
-new features until we can improve our [release
11
-process](https://github.com/ipfs/go-ipfs/pull/6482) (which we will be trialing
12
-in this release) and [testing
7
+The IPFS network has scaled to the point where small changes can have a
8
+wide-reaching impact on the entire network. To keep this situation from
9
+escalating, we've put a hold on releasing new features until we can improve our
10
+[release process](https://github.com/ipfs/go-ipfs/blob/master/docs/releases.md)
11
+(which we've trialed in this release) and [testing
12
procedures](https://github.com/ipfs/go-ipfs/issues/6483).
13
14
This release includes fixes for the following regressions:
15
16
1. A major bitswap throughput regression introduced in 0.4.21
17
([ipfs/go-ipfs#6442](https://github.com/ipfs/go-ipfs/issues/6442)).
19
-2. High bitswap CPU usage when connected to many (e.g., 10,000) peers. See
18
+2. High bitswap CPU usage when connected to many (e.g. 10,000) peers. See
19
[ipfs/go-bitswap#154](https://github.com/ipfs/go-bitswap/issues/154).
21
-2. The local network discovery service sometimes initializing before the
20
+2. The local network discovery service sometimes initializes before the
21
networking module, causing it to announce the wrong addresses and sometimes
23
- complain about not being able to determine the IP address)
22
+ complain about not being able to determine the IP address
23
([ipfs/go-ipfs#6415](https://github.com/ipfs/go-ipfs/pull/6415)).
24
25
It also includes fixes for:
26
27
1. Pins not being persisted after `ipfs block add --pin`
28
([ipfs/go-ipfs#6441](https://github.com/ipfs/go-ipfs/pull/6441)).
30
-2. Concurrent map access on GC due to the pinner
31
- ([ipfs/go-ipfs#6419](https://github.com/ipfs/go-ipfs/pull/6419)).
29
+2. Panic due to concurrent map access when adding and listing pins at the same
30
+ time ([ipfs/go-ipfs#6419](https://github.com/ipfs/go-ipfs/pull/6419)).
31
3. Potential pin-set corruption given a concurrent `ipfs repo gc` and `ipfs pin
32
rm` ([ipfs/go-ipfs#6444](https://github.com/ipfs/go-ipfs/pull/6444)).
33
4. Build failure due to a deleted git tag in one of our dependencies
34
([ipfs/go-ds-badger#64](https://github.com/ipfs/go-ds-badger/pull/65)).
35
37
-
36
Thanks to:
37
40
-* @hannahhoward for fixing both bitswap issues.
41
-* @sanderpick for catching and fixing the local discovery bug.
42
-* @campoy for fixing the build issue.
38
+* [@hannahhoward](https://github.com/hannahhoward) for fixing both bitswap issues.
39
+* [@sanderpick](https://github.com/sanderpick) for catching and fixing the local
40
+ discovery bug.
41
+* [@campoy](https://github.com/campoy) for fixing the build issue.
42
43
## 0.4.21 2019-05-30
44