The concept of a "Bug Fix Day" is to focus one day of software development on bugs fixing.
It generally occurs once in a while, depending on the number of bugs to fix. This is how the Mozilla developers do. But some teams prefer to choose a day of the week and stick to it. How do you do?
We usually have to once in a while before going to production, All team members gather in a meeting room and use product as enduser to check any surprises arises.
No, in my current project, we do not have a bug fix day. Personally, I am not a big fan of it, anyway. We work in 3-week-Sprints, so we can estimate our scope and put in a chunk of bugs (sorted by priority) as well. Then, we do soft zero-bug development, which means we try to do bugs first. That's not always possible, because there are too many bugs, and not all of them are all that relevant (like an API endpoint returning 200 instead of 204). So we fix the most important ones, then do features, and if there is time at the end of the Sprint, we do more bugs.
Phil Nash
Developer relations engineer at DataStax
😅 I voted for "Bugs? 🤨" but that's because I am a developer evangelist and am not responsible for anything that has a release schedule or anything like that. In my open source work I try to fix bugs as and when they appear, but there's no specific day for that and sometimes I don't have the time either.