[Anas] API freeze part makes sense (need 2 Releases for an API to freeze)
[Kumar] Working backwards, is it all going to land in 2.4? Understand the desire.
[Anas] All depends on how much we can get into 2.4
[Kumar] What are the key things for LTS -- sets the priority
Think through: What does the 2.x LTS get you, that the 1.x LTS doesn’t?
Power management, DTS
[Carles] Prioritization of things we want to do for the Project in general; LTS prioritization (2.6)
[Kumar] Value in distinguishing roadmap into user categories?
Other big items: Need to have more and need to prioritize them
[Anas] For LTS, delta between now and LTS -- a lot of things since last year that would be part of the LTS 2. Don’t foresee having a problem around having a full list differentiating between LTS 1 and LTS 2.
[Kumar] Driver API stabilization
[Anas] Audio support - SOF (Sound-open-firmware)
[Carles] 32-bit Cortex-A support, Paging support
[Kumar] Start Release Notes LTS 2? Clean up as part of 2.6 Release (holding spot to start tracking) // Add as cards under 2.6
[Kumar] Toolchain (IAR) - what will we realistically be able to say for 2.6? Aiming for full IAR compile link support? User visible statement
That’s the plan
[Anas] 2.6 Release criteria tracking
[Carles] Would like to have I2S and I2C for LTS 2
AI - All: Request folks working on 2.6/LTS2 to start adding Cards, Github issues
PR Backlog [Kumar]
We seem to keep growing the backlog - at 550 Open
What type of metrics should we try to track? Use Labels as a way to categorize what areas we are lagging in?
Some of this is due to the change of going to 2 reviewers
How do we grow the review pool? Identify people we should be asking for reviews from
Feels like the Project has more engagement - good thing! - How do we convert some of them to reviewers/maintainers/etc ; work on backlog
[Carles] What is the action that could be most effective?
[Kumar] If there’s new people, try to figure out areas they may be focusing on?
What areas are getting underserved?
How to identify who may be contributing to areas who could help?
[Anas] First thing I would do is a general clean-up; have been very relaxed with how people are contributing PRs (a lot of draft PRs); a lot of DNM; some sitting there for 1 year+
Draft: 66 Open
DNM: 62 Open
Has Conflicts: x
Removing the above, you reduce number to 321 Open PRs
Also to note -- No Reviews: 121
[Anas] Main problem is the noise. Another problem is that we need to have people review more than they are comfortable.
Maintainers file needs to be finalized and pushed
Once it’s there, people will start updating/approving
[Maureen] Maybe we just have Release Team start assigning manually until it’s automated
[Anas] Need to finalize the maintainers file before we can start automating
[Kumar] PRs without assignee -- review in the Release Meeting
[Kumar] May need to update policy on Draft PRs and DNMs and how long they are allowed to stay open?
[Anas] In the past (Gerrit), we were sending emails with the new things from the last day; things that are lagging
[Ioannis] How can we make sure the Release Team doesn’t merge something not ready to merge?
[Kumar] There are a few labels that should only apply to Draft PRs
[Anas] Scan the PR for certain labels and disable merging if they are present