@Przemyslaw Wirkus Create separate Epic for bugs, mark red if possible. See WPERF-50: Bugs for release 1.0 (all issues reported internally are here)Closed

@Przemyslaw Wirkus Setup project so we do not have Merge commits and we squash Merge Request - currently we do both and it make git log very ugly (cluttered).

@Przemyslaw Wirkus Breakdown WPERF-17: Add pretty printer for stats to simplify how we printClosed as it’s big task which could be split or become Epic with stories inside.

@Everton Constantino Create story (spike) to investigate if we can use Python as wperf frontend. See WPERF-51: Investigate if we can use Python as wperf frontendClosed

@Everton Constantino Investigate if we can have Pipeline with x86 → ARM64 build as a sanity check. See WPERF-52: Investigate if we can have Pipeline with x86 → ARM64 build as a sanity checkClosed

Other

We’ve agried that we should report issues inside Jira and GitLab issues should be used by external contributors.
Please use Linaro Google calendar to mark your Out of Office hours. Especially during incoming X-Max (December).

Windows Perf

2022-11-07 WPERF Sprint-4 Planning

Analytics

Other

Related content