How is bug fixing being prioritised? #21607
Replies: 2 comments 9 replies
-
|
My guess: There is no particular logic. There are too many bugs and too few people. Many or most of the very few people working on the bug fixes probably had no involvement in the original creation of Maui. Maui is complicated with many moving parts. For example, the team have said they know that Windows apps randomly start to blank screens but they can't find the cause here. That was reported 10 months ago now. So the 5-10 people on the team doing bug fixes likely just pick random ones they think they can fix and work on those until they hit a wall or solve it, then move on to the next. I used to do a lot of Unity development. I used to think it was bad that they would take 6 months over there to fix a verified bug. But they would fix anything you proved was related to their system with a clear bug report and repro project. Extremely good. Now I realize how spoiled I was. 😂 I still can't see how Microsoft can fix all the problems without twice or more the workforce assigned to it currently. There is only so much time in the day and it is hard to track down strange bugs in complex software. |
Beta Was this translation helpful? Give feedback.
-
|
I agree - there doesn't seem to be any particular logic from what I can see. Also, to me it looks like there is nobody managing it - if there was I would expect someone to be taking charge to make sure critical issues are prioritised, rather than wasting their time fixing stupid problems like corners on borders not being properly round, etc! Is there nobody in Microsoft responsible for this epic failure? I just don't get it.... |
Beta Was this translation helpful? Give feedback.
-
|
It's been stated multiple times that one of the way the team determines importance of an issue is the count of likes. Your issues have 0 and 1 like respectively. Why would you expect such issues to be prioritized, when they are not affecting many users? |
Beta Was this translation helpful? Give feedback.
-
|
@Vroomer I could go on... However, for me the problem is that, even if it was based on likes, using likes is a terrible way to prioritise. Most devs that I know don't bother liking the bug reports. They see that someone else has reported the problem so they don't bother doing anything. I have tried to get my team to report problems but most of the time they can't be bothered to even raise bugs - especially now that they feel like it's a waste of time because nobody is fixing them anyway. Also, on the subject of collection/scroll view et al - these problems have been reported multiple times in different forms by different people. If each of those reports only get 1 like each then the likelihood is that they will never be prioritised because the simple bugs which have 2 likes will jump to the top. It just feels like the whole priority system is flawed and critical issues are not getting addressed as a result... |
Beta Was this translation helpful? Give feedback.
-
|
The question is who is decider how it is prioritized? @davidortinau |
Beta Was this translation helpful? Give feedback.
-
|
I've added a high level statement about prioritization of issues for the current servicing of .NET 8 to the roadmap https://github.com/dotnet/maui/wiki/Roadmap. Xamarin migrations are the top priority with end of support coming May 1. Looking at those 5 issues @williambuchanan2 listed, they are all impacting projects in this category. The engineers assigned to them are either recently joining the core team from other teams and opportunistically working issues they are able to resolve, or they are working issues within the focus area they are best suited to resolve. We also track issue engagement (comments, number of commenters, reactions, etc.) and factor than in when planning a sprint. |
Beta Was this translation helpful? Give feedback.
-
|
@davidortinau thanks for adding that up and making it clear. Also thanks for the additional information about people that can currently support |
Beta Was this translation helpful? Give feedback.
-
|
@davidortinau How many developers are actively working on fixing bugs? I see .NET 9 is now coming up - last year we all waited for bug fixes but this didn't happen because all the focus went on .NET 8 - which didn't fix any of the critical problems. If there aren't enough people working on bug fixing (which obviously is the situation) it wouldn't be hard to imagine that the same thing is going to happen again this year... |
Beta Was this translation helpful? Give feedback.
-
Just wondering what the logic is behind the prioritising of bug fixing...
From what I can see, a lot of critical bugs which have been repeatedly reported are getting ignored, while at the same time relatively minor bugs reported only 2 weeks ago are already being worked on in the current iteration.
I have these 2 critical issues causing major problems which actually prevent the app from working:
#19383
#19175
Both were reported in December - but had also been reported in various other forms before then (particularly the collection view scrolling issue which has a lot of people complaining about it).
There is also the well known ios keyboard issue that everyone has been screaming about for at least 18 months - it's still not fixed.
Surely things like this would be more important to address than a lot of the things which seem to be in the current iteration?
Beta Was this translation helpful? Give feedback.
All reactions