@patrickbajao For real-time efforts, it looks like we'll finish both the merge and approval widgets in %15.10 - what do you think makes the most sense to pick up next?
@phikai feature flag roll out issues once changes are merged. For real-time merge widget, I posted them in &8639 (comment 1308262675). I don't see one for approval widget yet.
Next one could be &9872 (draft status) which is related to a reported bug gitlab#388402. Still discussing though.
@jay_mccure@garyh Has the work to triage bugs been done as part this OKR? In order to be able to resolve any of the bugs, we'll need to have the triaging work done.
@phikai I have only triaged new bugs I have raised. Are you OK with these severity definitions for the CLI? cli!1182 (diffs). If so I will start triaging.
@jay_mccure Yes - I think those definitions make a lot of sense. I've approved your MR, but if you want to fix the pipelines, we can get Amy to take a pass as well. Thank you!
@phikai I was thinking improving the non-interactive flow of auth login might be useful. At the moment the two commands are equivalent:
glab auth login -t tokenfoo -h host.comglab config set token -g -h host.com tokenfoo
i.e. glab auth login in non-interactive mode doesn't provide any feedback as to whether login will actually succeed
It would also be nice to set other attributes using non-interactive mode as it only accepts token and host currently.
Those are interesting ideas - one of the things we'll need to keep in mind is picking up some bugs related to the triage effort... so maybe if we can frame things that way, it would help.
The spike of SSR investigation (15.10) will produce a PoC that will continue to be built into 15.11 aimed at removing uncertainty not necessarily ship a working solution in prod. Hence it being included in Slippage.
Slippage breakdown
Weight
Issue
2
Update merge request approval widget component to use the GraphQL subscription
1
Links to pending comments from footer broken
2
Don't load all the diffs ahead of time when using the Show one file at a time option in an MR
2
Investigate performance improvements of switching back to Server Side Rendering for the Diffs app
@afracazo@mnearents@aqualls - We've finalized the 15.11 release board - take a look at the issues there and add any relevant labels for UX/TW as needed. You can also ask any questions if you're concerned about anything there.
Since we did the planning for %15.11, there have been a number of changes that will impact the planned deliverables for %15.11.
Large Database InfraDev Issues
The main database is stressed and Code Review owns some of the largest tables. There have been a number of InfraDev issues that have come in that we are responding to:
The original intent was to be gone for 3 months. However, good progress was made so we decided to end the "loan" early. However, that did not mean the team member came back to Code Review...
AI Initiative
This has become the new highest priority for the team. This impacts multiple team members. @patrickbajao will move from the Source Code borrow directly to the new AI Enablement team as a temporary assignment. In addition, as the Code Review team, we will need to start working on a new AI-enabled feature.
Database Performance: In addition to the InfraDev issues listed above, we had also been researching database performance in these issues which were planned for %15.11:
Based on the above information, @phikai and I have worked to reprioritize the work for %15.11. We've had to narrow the scope of work to really focus on the most important things.
We usually try to not make these types of changes in the middle of a milestone, but we have had to be a bit more agile this time around. I apologize for the disruption this causes.
Backend folks (or anyone) - if you have questions/comments/concerns, please don't hesitate to reach out to me. I'm happy to make myself available outside of my own normal working hours - so please set something up if you'd like.
Essentially there's still some frontend issues to be shipped too, to consider this effort done. This work is stalled until we're able to refocus at least partially on this.