Late Night updates
==================

I work as the QA lead for the Vivaldi web browser. Being a small team
I also have an additional role where I am responsible for much of the
release process for our desktop browser, including version daily
versions to a small external (volunteer) testing group, weekly public
"snapshots" (sort of like beta releases for the upcoming version), and
major and minor updates to our stable version.

~ Vivaldi web browser:
https://vivaldi.com/

For those who do not know, Vivaldi is a Chromium based browser and as
such our work is highly dependent on the upstream Chrome team. That
team puts out their own releases during east coast US working hours,
while the Vivaldi team is largely based in Europe. That can
occasionally be problematic if a critical security update is need.

We received a bit of a heads up on Thursday that a Chrome update was
likely to happen on Friday, due to a zero-day exploit (CVE-2022-3075).
This meant we expected to have to release our own version, with the
same fix (which we had already identified) close to midnight if we
wanted to have something ready for our users in a timely fashion.

Well... it happened and we did it! Our blog post was released within
25 minutes of the Chrome one. \o/

[thinks] I wonder if any of the other Chromium based browsers reacted
as fast as us?

~ Minor update (6) for Vivaldi Desktop Browser 5.4:
https://vivaldi.com/blog/desktop/minor-update-six-5-4/

~ Stable Channel Update for Desktop (Chrome 105.0.5195.102):
https://chromereleases.googleblog.com/2022/09/stable-channel-update-for-desktop.html

~ How a Chromium browser is maintained and updated:
https://vivaldi.com/blog/lets-go-under-the-browser-hood-with-vivaldis-yngve/

P.S. Hi Pathduck ;)

* * *