Explore if Tchap Web v2 is compatible with mainlining

[jdauphant]

Regressions

• [Investigation] Bug : Preview #295
• Bug : /keys/query - spam de messages d'erreurs #296
• Bug: publicised groups - Error : Cannot display flair #297

API Changes

• API change : /email_account_validity/* #298
• [Investigation] API change : /email_account_validity/admin #294
• [Investigation] API change : /account/3pid/lookup #293
• [Investigation] API change : /versions #299
• API Change : Chargement de la config : lazy_load_members #300

source: https://docs.google.com/document/d/1vzjZgauLAMvsjVUdxLnqYkqf2GHKZcQupooEVutfmVA/edit?pli=1#heading=h.hl9xdcqvj2py

[jdauphant]

• Backport "correct request body for the /keys/query endpoint" to support  #285

[mcalinghee]

At this moment, the mainlining is a transition version meaning the former APIs and newer APIs are available.

We could apply the following migration strategy for the client :

• Resolves the Regression issues : Bug : /keys/query - spam de messages d'erreurs #296 and Bug: publicised groups - Error : Cannot display flair #297
• Build a new version of tchap-web-v2
• Release tchap-web-v2 - 2.5.5 to :
  • dev
  • preprod
  • prod
• Perform Tests against :
  • the version "v1.2" (mainlining version) : https://www.tchap.incubateur.net/
  • the version "r0.6.0" (current version) : https://www.beta.tchap.gouv.fr/
• Focus on tchap-web-v4

Benefits :

• Upgrade to v1.2(mainlining) can happen independently
• API Changes issues will be resolved in tchap-web-v4 directly instead of spending effort of fixing issues. in tchap-web-v2

Caveat :

• Future upgrades of Synapse(no former API are available) should be performed after tchap-web-v4 is released as the API Changes issues should be resolved

Participants to this discussion : @celiacheff , @guillaumevillemont , @jdauphant , @mcalinghee

[mcalinghee]

Test performed on dev with mainlining version : https://www.tchap.incubateur.net ✅

• Looking up a user
• Inviting an external user
• Account Registration
• Sign-in
• Sending message