Testing week

On each release, we establish a testing period of one week, when we lock the waku.test fleet so that it only runs the target version. During that period, we need to continuously stress that fleet from the sandbox machine, for example.

It is important to make sure the waku-simulator works as expected and the nodes can establish connections among themselves.

During that week, the release owner needs to check the Kibana logs from the previous month (since the last release was deployed) looking for possible crashes or errors in waku.test & waku.sandbox. These are the most relevant logs to check:

  • (fleet: "waku.test" OR fleet: "waku.sandbox") AND message: "SIGSEGV"

Make sure that Status client works properly when connected to a fleet running on the release candidate version. For it, please follow its corresponding guide.

Release Calendar

NameDateRelease Ownernwaku-version
wakuv2.test deployment2024-01-15SP0.24.0
wakuv2.prod deployment2024-01-22SP0.24.x
wakuv2.test deployment2024-02-12Zoltan0.25.0
wakuv2.prod deployment2024-02-19Zoltan0.25.x
waku.test deployment2024-03-11Zoltan0.26.0
waku.sandbox deployment2024-03-18Zoltan0.26.x
waku.test deployment2024-04-15Gabriel0.27.0
waku.sandbox deployment2024-04-22Gabriel0.27.x
waku.test deployment2024-05-13Gabriel0.28.0
waku.sandbox deployment2024-05-20Gabriel0.28.x
waku.test deployment2024-06-10Ivan0.29.0
waku.sandbox deployment2024-06-17Ivan0.29.x
waku.test deployment2024-06-24Ivan0.30.0
waku.sandbox deployment2024-06-26Ivan0.30.x
waku.test deployment2024-07-22Ivan0.31.0
waku.sandbox deployment2024-07-24Ivan0.31.x
waku.test deployment2024-08-26Zoltan0.32.0
waku.sandbox deployment2024-08-28Zoltan0.32.x
waku.test deployment2024-09-23Zoltan0.33.0
waku.sandbox deployment2024-09-25Zoltan0.33.x
waku.test deployment2024-10-28Gabriel0.34.0
waku.sandbox deployment2024-10-30Gabriel0.34.x