/
2022-10-24 WPERF Sprint-3 Planning

2022-10-24 WPERF Sprint-3 Planning

Current status

  • WindowsPerf was upstreamed after internal IP review.

  • Current sprint should help developers getting familiar with WindowsPerf contributing process.

  • @Jiong Wang (Deactivated) is working on Sampling Model implementation.

    • Should have prototype in about month time.

    • Sampling model will be discussed between all parties.

    • There is some refactoring needed to support sampling.

  • @Jiong Wang (Deactivated) will use WindowsPErf GitLab issues as there are some regressions his team found.

Contributing in this sprint

  • This sprint is very flexible and allows developers to select work they would like to do. 

  • Sprint-3 is all about learning about codebase of WindowsPerf by sending 1-3 pull requests with simple refactroring changes.

  • Contributing guidelines are as follows: https://gitlab.com/Linaro/WindowsPerf/windowsperf/-/blob/main/CONTRIBUTING.md. Note: This document will be improved. 

  • Please, when you send pull request (PR) on WindowsPerf with your change expect comments from me. Also please note that currently @Przemyslaw Wirkus will be gatekeeping all pull request. It means he will merge them when they are ready.

    • Please feel free to comment on PRs of others as well.

  • From Sprint-4 we will asking tasks during Monday sprint planning.

Minutes

  • Discussion regarding opening Jira to all users. So that they anyone can e.g. report issue.

  • We’ve discussed that developers this sprint should concentrate on getting tickets from backlog, assigning them, fixing them and sending pull requests.

  • We’ve encouraged developers to reach out via mailing list if they have an issue.

  • We want to add bi-weekly meeting (Monday) to capture progress between sprint planings.

  • @Niyas Sait (Deactivated) is working on Kernel drivel signing.

Actions

@Przemyslaw Wirkus Investigating which unit test framework is suitable for our project.
@julianus.larson Investigate if we can open Jira.
@julianus.larson Add issue type “BUG” so that we can capture not only epics and stories but also bugs (internal and external). @Niyas Sait (Deactivated) gave Apache Arrow as example of project with Jira open to others.

 

 

Related content

2022-09-15 WPERF Sprint 0 Meeting notes
2022-09-15 WPERF Sprint 0 Meeting notes
More like this
2022-09-30 WPERF Sprint 1 Retrospective
2022-09-30 WPERF Sprint 1 Retrospective
More like this
2022-10-03 WPERF Sprint-2 Planning
2022-10-03 WPERF Sprint-2 Planning
More like this
2023-01-09 WPERF Sprint-7 Planning
2023-01-09 WPERF Sprint-7 Planning
More like this
2022-11-07 WPERF Sprint-4 Planning
2022-11-07 WPERF Sprint-4 Planning
More like this
2023-04-03 WPERF Sprint-13 Planning
2023-04-03 WPERF Sprint-13 Planning
More like this