Release 3.4.0

esl · Jun 26, 2019 · c21254b · c21254b
1 parent 1609e60
commit c21254b
Show file tree

Hide file tree

Showing 7 changed files with 53 additions and 8 deletions.
diff --git a/.travis.yml b/.travis.yml
@@ -77,8 +77,6 @@ branches:
                 - stable
                 - /^rel\-\d+\.\d+$/
                 - /^\d+\.\d+\.\d+([a-z0-9\-\+])*/
-                - gdpr-retrieve-clean
-                - gdpr-remove-vcard
 
 otp_release:
         - 20.3

diff --git a/CHANGELOG.md b/CHANGELOG.md
@@ -1,3 +1,48 @@
+# [MongooseIM 3.4.0](https://github.com/esl/MongooseIM/releases/tag/3.4.0) - 2019-06-26
+
+## Highlights
+
+- GDPR data retrieval and removal
+
+## All changes
+
+### Added
+
+- GDPR data retrieval and removal (#2260, #2285, #2286, #2288, #2289, #2293, #2294, #2295, #2296, #2297, #2298, #2299, #2300, #2301, #2302, #2303, #2309, #2310, #2312, #2313, #2314, #2316, #2320, #2323, #2326, #2327, #2328, #2336, #2339, #2341, #2345, #2347, #2349)
+- CLI `register` function now generates a safe, random username for a new account (#2262)
+- It is possible now to change the server name returned in HTTP responses (#2308)
+- A new behaviour in case of conflicting component connections: `kick_old` (#2315)
+
+### Changed
+
+- When a session gets replaced, the new one waits longer for the old one to close before reporting an error (#2054)
+- Authentication backends no longer use a `store_type/1` function (#2254)
+- Default certificates are now generated faster (#2305)
+
+### Fixed
+
+- Some race conditions in Stream Management (#2049)
+- faulty script execution of `xep_tools` (#2252)
+- MUC messages are now archived without an empty `to` attribute (#2220)
+- "Offline" classic MUC rooms are now properly reported in disco results (#2238)
+- Inbox responses are now properly routed to the original requester (#2276)
+- Resolved issues with TLS on OTP 20.x (#2332)
+
+### Other
+
+- Updated `escalus` to `4.1.0` (#2337)
+- Test improvements and refactoring (#2319)
+- Update documentation (#2246, #2259, #2261, #2307, #2346)
+
+## Commits, merged PRs and closed issues
+
+- [List of merged PRs](https://github.com/esl/MongooseIM/pulls?q=is%3Apr+is%3Amerged+milestone%3A3.4.0)
+- [List of closed issues](https://github.com/esl/MongooseIM/issues?utf8=%E2%9C%93&q=is%3Aissue+is%3Aclosed+closed%3A%222019-03-13..2019-06-26%22+)
+- [Repository history for this release](https://github.com/esl/MongooseIM/graphs/contributors?from=2019-03-13&to=2019-06-26&type=c)
+
+## Special thanks to our contributor:
+- @varnerac
+
 # [MongooseIM 3.3.0](https://github.com/esl/MongooseIM/releases/tag/3.3.0) - 2019-03-12
 
 ## Highlights

diff --git a/README.md b/README.md
@@ -65,6 +65,7 @@ Check out our test results:
 Up-to-date documentation for the MongooseIM master branch can be found on ReadTheDocs: [https://mongooseim.readthedocs.io/en/latest/](https://mongooseim.readthedocs.io/en/latest/).
 
 Latest releases:
+* [3.4.0](https://mongooseim.readthedocs.io/en/3.4.0/)
 * [3.3.0](https://mongooseim.readthedocs.io/en/3.3.0/)
 * [3.2.0](https://mongooseim.readthedocs.io/en/3.2.0/)
 * [3.1.0](https://mongooseim.readthedocs.io/en/3.1.0/)

diff --git a/VERSION b/VERSION
@@ -1 +1 @@
-3.3.0
+3.4.0
diff --git a/doc/index.md b/doc/index.md
@@ -75,6 +75,7 @@ Check out our test results:
 See the documentation for the latest releases:
 
 * [Master](https://mongooseim.readthedocs.org/en/latest/)
+* [3.4.0](https://mongooseim.readthedocs.io/en/3.4.0/)
 * [3.3.0](https://mongooseim.readthedocs.io/en/3.3.0/)
 * [3.2.0](https://mongooseim.readthedocs.io/en/3.2.0/)
 * [3.1.0](https://mongooseim.readthedocs.io/en/3.1.0/)

diff --git a/doc/migrations/3.3.0_3.3.0plus.md → doc/migrations/3.3.0_3.4.0.md b/doc/migrations/3.3.0_3.3.0plus.md → doc/migrations/3.3.0_3.4.0.md
@@ -2,7 +2,7 @@
 
 As a part of ensuring GDPR compliance, it is essential to be able to efficiently query MAM MUC data via sender ID (to retrieve user's personal data).
 Originally, the sender JID could be found only as a part of an encoded XML message element, so finding all items sent by a certain user would be **extremely** inefficient (or rather: anti-efficient).
-MongooseIM 3.3.0++ uses a modified schema for MAM MUC backends which enables a more efficient extraction.
+MongooseIM 3.4.0 uses a modified schema for MAM MUC backends which enables a more efficient extraction.
 
 Below you may find migration instructions specific to your MAM backend.
 
@@ -35,7 +35,7 @@ CREATE INDEX i_mam_muc_message_sender_id ON mam_muc_message(sender_id);
 
 #### Step 2
 
-Now you have a schema that is compatible with MIM 3.3.0++ but isn't GDPR-compliant yet because the new column has no meaningful data.
+Now you have a schema that is compatible with MIM 3.4.0 but isn't GDPR-compliant yet because the new column has no meaningful data.
 
 Please pick your favourite scripting/programming language and populate the new column with the help of a [dedicated script](jid-from-mam-muc-script.md).
 You'll need to iterate over the whole `mam_muc_message` table with the following algorithm:
@@ -60,7 +60,7 @@ DESC mam_muc_message;
 
 #### Step 2
 
-Now you have a schema that is compatible with MIM 3.3.0++ but isn't GDPR-compliant yet because the new column has no meaningful data.
+Now you have a schema that is compatible with MIM 3.4.0 but isn't GDPR-compliant yet because the new column has no meaningful data.
 
 Please pick your favourite scripting/programming language and populate the new column with the help of a [dedicated script](jid-from-mam-muc-script.md).
 You'll need to iterate over the whole `mam_muc_message` table with the following algorithm:
@@ -169,7 +169,7 @@ PUT muc_messages/_mapping/muc
 
 #### Step 2
 
-Now you have a schema that is compatible with MIM 3.3.0++ but isn't GDPR-compliant yet because the new field has no meaningful data.
+Now you have a schema that is compatible with MIM 3.4.0 but isn't GDPR-compliant yet because the new field has no meaningful data.
 
 Please pick your favourite scripting/programming language and populate the new column with the help of a [dedicated script](jid-from-mam-muc-script.md).
 You'll need to iterate over the all `muc_messages` documents with the following algorithm:

diff --git a/mkdocs.yml b/mkdocs.yml
@@ -22,7 +22,7 @@ pages:
       - 'How to Set up Jingle/SIP': 'user-guide/Jingle-SIP-setup.md'
   - Migration Guide:
       - '3.1.1 to 3.2.0': 'migrations/3.1.1_3.2.0.md'
-      - '3.3.0 to 3.3.0++': 'migrations/3.3.0_3.3.0plus.md'
+      - '3.3.0 to 3.4.0': 'migrations/3.3.0_3.4.0.md'
       - 'MAM MUC migration helper': 'migrations/jid-from-mam-muc-script.md'
   - Platform:
       - 'Contributions to ecosystem': 'Contributions.md'