Bugzilla

(In reply to Zibi Braniecki [:zbraniecki][:gandalf] from comment #26)
> I understand the M2 is costly to produce as it is hard to automate. My quiet hope was that we'll get to finish M2 rather than deprecate the milestone.

Besides the calls being repeated, when I tried locally I got results completely different from the existing data generated by Eric. Not sure if that was caused by using a different platform, or if it depends on how long you wait before closing the browser (since calls are duplicated)?

Dropping M2 will likely allow us to generate the date in GitHub actions, unless we hit space limitations when cloning the unified repo. Worst case scenario, it's easy to reproduce on different machines.

(In reply to Zibi Braniecki [:zbraniecki][:gandalf] from comment #26)
> I understand the M2 is costly to produce as it is hard to automate. My quiet hope was that we'll get to finish M2 rather than deprecate the milestone.

Besides the calls being repeated, when I tried locally I got results completely different from the existing data generated by Eric. Not sure if that was caused by using a different platform, or if it depends on how long you wait before closing the browser (since calls are duplicated)?

Dropping M2 will likely allow us to generate the data in GitHub actions, unless we hit space limitations when cloning the unified repo. Worst case scenario, it's easy to reproduce on different machines.