[yast-devel] YaST Bugs Assigned to Team Members ... and Rotting
Hi guys, Packagers have a bug-squashing day/week and reported that we have quite a big number of bugs assigned to our team members and (some of) these bugs have been basically rotting for years. What is the plan? We've started using Scrum and planning the team time more than two years ago, so we are basically fully booked. Maybe something for the Retro meeting? Thx in advance Lukas -- Lukas Ocilka, Systems Management (Yast) Team Leader SLE Department, SUSE Linux -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org To contact the owner, e-mail: yast-devel+owner@opensuse.org
V Fri, 11 Aug 2017 15:12:26 +0200
Lukas Ocilka
Hi guys,
Packagers have a bug-squashing day/week and reported that we have quite a big number of bugs assigned to our team members and (some of) these bugs have been basically rotting for years.
What is the plan? We've started using Scrum and planning the team time more than two years ago, so we are basically fully booked.
Maybe something for the Retro meeting?
Thx in advance Lukas
Well, I actually use bug squashing day, to reduce at first bugs on my account and then other bugs that is annoying or make sense for me. So I hope bug squashing helps here. Josef -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org To contact the owner, e-mail: yast-devel+owner@opensuse.org
Thank Josef, but that actually answers just bugs that are assigned to yourself. I'm asking for a generic solution: What to do with bugs that are assigned to our team members and just sit there (some for years)? Does anyone have an answer to that? Thx Lukas -- Lukas Ocilka, Systems Management (Yast) Team Leader SLE Department, SUSE Linux -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org To contact the owner, e-mail: yast-devel+owner@opensuse.org
On 14.08.2017 12:46, Lukas Ocilka wrote:
I'm asking for a generic solution: What to do with bugs that are assigned to our team members and just sit there (some for years)? Does anyone have an answer to that?
Make a decision (like I just wrote to [research]) whether it's WONTFIX (which
might include WONTFIX_UNLESS_THERE_IS_PLENTY_OF_EXCESS_TIME, i.e. never) or
move to yast-internal together with a Trello card?
Kind regards
--
Stefan Hundhammer
participants (3)
-
Josef Reidinger -
Lukas Ocilka -
Stefan Hundhammer