From 03929a7fe5d4d152615b1448541f46ac4d1f9096 Mon Sep 17 00:00:00 2001 From: Alexander Emelin Date: Fri, 2 Oct 2020 01:50:06 +0300 Subject: [PATCH] prepare v2.7.2 release --- CHANGELOG.md | 10 ++++++++++ docs/content/pro/index.md | 6 +++++- docs/content/server/engines.md | 2 +- misc/release/notes.md | 3 ++- 4 files changed, 18 insertions(+), 3 deletions(-) diff --git a/CHANGELOG.md b/CHANGELOG.md index 4341dbf001..c0a2c518ab 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -1,3 +1,13 @@ +v2.7.2 +====== + +No backwards incompatible changes here. + +Fixes: + +* Fix client reconnects due to `InsufficientState` errors. There were two scenarios when this could happen. The first one is using Redis engine with `seq`/`gen` legacy fields (i.e. not using **v3_use_offset** option). The second when publishing a lot of messages in parallel with Memory engine. Both scenarios should be fixed now. +* Fix non-working SockJS transport close with custom disconnect code: this is a regression introduced by v2.6.2 + v2.7.1 ====== diff --git a/docs/content/pro/index.md b/docs/content/pro/index.md index 9a90021ad2..b4cc93c205 100644 --- a/docs/content/pro/index.md +++ b/docs/content/pro/index.md @@ -2,7 +2,11 @@ Centrifugo becomes more popular and is used in many projects over the world. Since it's rather big project I need more and more time to maintain it healthy, improve client libraries and introduce new features. -I am considering to create a PRO version of Centrifugo. It may include some additional features on top of open-source Centrifugo version. This version will have some model of monetization, I am still evaluating whether it's reasonable to have and will be in demand. Please contact me (see email address in [my GitHub profile](https://github.com/FZambia)) if you are interested in having additional features mentioned below and have any ideas on how to keep Centrifugo development sustainable. +I am considering to create a PRO version of Centrifugo. It may include some additional features on top of open-source Centrifugo version. This version will have some model of monetization, I am still evaluating whether it's reasonable to have and will be in demand. + +An alternative to PRO version is our [Centrifugal OpenCollective](https://opencollective.com/centrifugal) organization – personally I prefer this way of becoming sustainable since it does not involve creating custom closed-source version of Centrifugo. + +Please contact me (see email address in [my GitHub profile](https://github.com/FZambia)) if you are interested in having additional features mentioned below and have any ideas on how to keep Centrifugo development sustainable. ## Real-time connection analytics with Clickhouse diff --git a/docs/content/server/engines.md b/docs/content/server/engines.md index f2fa670be7..7af22e807c 100644 --- a/docs/content/server/engines.md +++ b/docs/content/server/engines.md @@ -295,4 +295,4 @@ Available options: * `nats_dial_timeout` - timeout for dialing to Nats in seconds, default `1`. * `nats_write_timeout` - write (and flush) timeout on a connection to Nats in seconds, default `1`. -It's theoretically possible to use Redis Engine together with Nats broker for message history, recovery and presence. If you are interested in this – please write to our community chat rooms. +It's theoretically possible to use Redis Engine together with Nats broker for presence information. If you are interested in this – please write to our community chat rooms. diff --git a/misc/release/notes.md b/misc/release/notes.md index 9eca057f6a..c316920270 100644 --- a/misc/release/notes.md +++ b/misc/release/notes.md @@ -2,4 +2,5 @@ No backwards incompatible changes here. Fixes: -* Fix non-working websocket close with custom disconnect code: this is a regression introduced by v2.6.2 +* Fix client reconnects due to `InsufficientState` errors. There were two scenarios when this could happen. The first one is using Redis engine with `seq`/`gen` legacy fields (i.e. not using **v3_use_offset** option). The second when publishing a lot of messages in parallel with Memory engine. Both scenarios should be fixed now. +* Fix non-working SockJS transport close with custom disconnect code: this is a regression introduced by v2.6.2