Release TMail 0.4.0

[chibenwa]

• [x] Tag the release 0.4.0
• [x] Create the changelog
• [x] update software-linagora-com
• [x] Deploy on dev
• [x] ask QA test on dev
• [x] deploy on preprod
• [x] run perf tests on preprod
• [x] deploy on prod
• [x] deploy on LNG

[Arsnael]

changelog software-linagora-com: https://ci.linagora.com/linagora/lgs/software-linagora-com-website/merge_requests/29

[Arsnael]

JMAP run (3000 users, 15mins injection, 30mins run):

If we compare with the previous release run: https://github.com/linagora/tmail-backend/issues/189#issuecomment-887282547

• OpenMessage > getMessages seems twice slower
• UpdateFlags is quite slower as well

[chibenwa]

Interesting. Can we plan another run with MIME4J 0.8.6-SNAPSHOT added as a dependency of the app?

Keep in mind that Quan changes regarding JMAP threads could explain some performance degradation of sendMessage.

IMO not a blocker (perfs are still good) but definitly worth investigating.

[Arsnael]

Not looking much better with your MIME4J 0.8.6-SNAPSHOT image:

getMessages a bit better but FlagUpdate quite worse...

[chibenwa]

... I don't get how MIMe4J can impact flags updates ...

Also keep in mind that these perfs are impacted by the OVH object store. For sure it being a bit more busy a monday morning in sept compared to a night in the middle of July is not really surprising.

As the perfs are still good I propose to move forward.

[Arsnael]

I agree there could be different factors. You have a good point that the object store might be busier now than this morning (well last night fr time)

[chibenwa]

We could plan another run in the morning.

Also 18-19h VN is often low-activity too.

[Arsnael]

and here for the imap one :D