On 2019-12-20 10:03, Ancor Gonzalez Sosa wrote:
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).
Localization bugs (mainly problems with non-latin languages):
22 open bugs
dns-server && dhcp-server (they are so related that even share bugs):
20 open bugs, aprox.
NTP: 13 open bugs
Bootloader: 20 open bugs, aprox.
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 ;-)
Network: hard to say, at least 50.
Great job!! Thanks a lot. Have you categorized the bugs somehow? I mean,
do you have the list of bugs for each area?
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.
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?
IMHO, this is a great idea. Solving bugs one by one without being
focused in a specific topic/module would be quite more difficult. That
small refactoring squads could make the job easier.
--
José Iván López González
YaST Team at SUSE LINUX GmbH
IRC: jilopez
--
To unsubscribe, e-mail: yast-devel+unsubscr...@opensuse.org
To contact the owner, e-mail: yast-devel+ow...@opensuse.org
