V Fri, 20 Dec 2019 11:03:32 +0100 Ancor Gonzalez Sosa <an...@suse.de> napsáno:
> I've gone through the full list of bugs assigned to the YaST Team or > some of its members with the intention of closing obsolete stuff that > are not real issues anymore. > > In the process I found out there are some YaST modules or areas that > have quite some open bugs. Some of them are modules that never receive > attention (no-man shows, as HuHa likes to call them). > Hi, let me first ask few question to get more details: > Localization bugs (mainly problems with non-latin languages): > 22 open bugs by non-latin you means with fancy images like chinese or right to left ones? I think that is the most affected ones and I am not sure if openqa covers it, so maybe we should try to invest to convince openqa guys to test those two specific areas. > > dns-server && dhcp-server (they are so related that even share bugs): > 20 open bugs, aprox. > > NTP: 13 open bugs Is it NTP SLE12 and older or NTP SLE15 and newer? As I did massive rewrite/simplification of ntp-client in SLE15 with switch from ntp to chrony. So it is important info. > > Bootloader: 20 open bugs, aprox. Can you point me to it? I am a bit curious what are they? I probably overlook them as I usually try to quickly react on bootloader problems. Sometimes they are hidden storage bugs as bootloader is a bit sensitive to some boot scenarios. > > NFS: 12 open bugs, I already plan to focus the firepower of the storage > squad here for the following sprint(s). > > Storage: 30 open bugs, aprox. but they are under control ;-) same here, we have old and new storage, so it would be interesting to get at least ration. > > Network: hard to say, at least 50. Yep, problem is that many are for old pre network-ng and some are basically rotting for long time or cannot be reproduced. > > If reducing the number of bugs is a goal, I think it would be worth to > create small groups of 2-3 developers to focus on a given module for a > month or two. That would be enough time to gather the knowledge about > the topic and refactor the most important parts (those modules are > usually not that big). In some cases, that can mean up to 20 bugs solved > and a more sane codebase (plus some refreshed knowledge) for the future. + ideally increase test coverage for such modules, so we are less scare in future to touch them. > > Let's assume two small refactoring squads (2-3 people each) working in > parallel. I think that, for example, DNS+DHCP+NFS+NTP could all be > brought into shape in less than two months. That would be around 45 > fewer bug reports. > > What do you think? In general good idea. Ideally we should collect that bugs in one card, then analyze them ( as often problem is not in yast or contain many duplicates ) and if it really confirm issue, then work on them. BTW I a bit missing autoyast in a list. Either we improve it so much or it is well hidden bugs ( do you have autoyast-maintainers in your query? ) > > Cheers Thanks for heads-up. Josef > > PS.- Network is, of course, a completely different story. I hope we can > close many bugs as obsolete in something like two years from now, when > network-ng would had already replaced the current implementation. > -- To unsubscribe, e-mail: yast-devel+unsubscr...@opensuse.org To contact the owner, e-mail: yast-devel+ow...@opensuse.org
