Expired
Milestone
Feb 1, 2024–Feb 12, 2024
Protocol Oxford 2 -- activation
-
Communication campaign so that Bakers infrastructure is ready (@germanD) -
Monitoring is ready: make sure that all monitoring tools are working (@MBourgoin) -
Grafana dashboards -
Teztale -
Eventually indexer
-
-
Prepare a snapshot a few blocks before activation, that can be used (@MBourgoin) -
Core devs war room team availability checking -
Release manager (@Killian-Delarue) -
Visibility and access to TF nodes and bakers (@chrispinnock) -
Someone that knows how to produce a snapshot -
Layer 1 incident manager (@MBourgoin) -
Tech lead or team member of Oxford 2 features: -
@lrand , @julien.t for Staking and co. -
@ACoquereau , @vbotbol for bakers updates
-
-
-
In case of incident: -
Incident Response coordination between core, comm, ecosystem, baker engagement (@germanD) -
create a incident channel
-
-
Incident resolution management (@MBourgoin) -
Care about engineers in particular stressful settings in case of issues – Create a peaceful environment aside from the festive war room -
create closed-to core-devs war-room
-
-
put regularly information to the incident channel about core-devs works -
maintain core-dev report and provide recommendations -
Schedule any additional checks after activation in the following days -
@lrand for Staking and co. -
@ACoquereau for baker updates
-
-
Make sure it is reported so that we take it into account
-
-