202007 [FreeBSD WIKI]

This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong.
On the 11th July 2020 from 1400-2100 UTC we ran a coordinated
virtual Bug Squash. %%FreeBSD%% has a [[https://bugs.freebsd.org/bugzilla|Problem Report (PR) database]] where users
and developers are encouraged to file issues and regressions they find in both
the base system and ports tree.

A Bug Squash is a focused session where we try to triage, process, fix and
close as many reports as we can from the PR database. This July 11th Bug Squash
we will focus on closing as many PRs with patches as we can.

While we do process and close issues there are a large number of PRs with
patches attached that should be processed. At the time of writing there are:

  * [[https://bugs.freebsd.org/bugzilla/buglist.cgi?keywords=patch&keywords_type=allwords&limit=0&list_id=364771&order=bug_id%20DESC&product=Base%20System&query_format=advanced&resolution=---|all base system PRs with patches]] (639)
  * [[https://bugs.freebsd.org/bugzilla/buglist.cgi?email1=bugs%40FreeBSD.org&emailassigned_to1=1&emailtype1=equals&keywords=patch&keywords_type=allwords&list_id=364772&order=bug_id%20DESC&product=Base%20System&query_format=advanced&resolution=---|all base system PRs with patches, but assigned to no one]] (277)

===== Approach =====

We are looking to reduce the number of bugs in the bug track in a scalable and friendly way. We do not aim to close bugs because they are old or hard. We will make a deliberate effort to find bugs with patches and test and evaluate the bugs and the patches. The intention is to turn as many bugs as reasonable to fixes in %%FreeBSD%%.

In addition we encourage people to come with their own bugs so we can help with filing issues and getting these fixed.

===== Intended audience =====

People in the following (not limitative) categories are welcome to take part:

  - people with bugs they're affected by and would like fixed, so they can test possible fixes or provide feedback on possible solutions;
  - people interested in fixing bugs but needing help in finding ones that are in their sphere of interest or at their expertise level;
  - people to cheer bug-fixers along and provide moral support; and
  - anyone else interested in watching or taking part.

===== Coordination =====

We hosted a google meet at the start of the Bug Squash to provide an
introduction to the process and will use the #freebsd-bugs irc channel on
freenode to coordinate work, triage and discuss PRs and patches.

Google Meet
  * https://meet.google.com/dfp-fsou-pwi

IRC
  * #freebsd-bugs on freenode 
  * If you are new to using IRC [[https://www.irccloud.com/invite?channel=%23freebsd-bugs&hostname=irc.freenode.net&port=6697&ssl=1|this link will allow you to participate]]

Announcement:

  * https://lists.freebsd.org/pipermail/freebsd-advocacy/2020-June/004890.html

Some other links:
  * [[/OfficeHours|OfficeHours]]
  * [[/Bugathons]]
  * [[/BugBusting|BugBusting]]
  * [[MarkLinimon/BugbustingOfficeHours|MarkLinimon/BugbustingOfficeHours]] (Mark's general notes)
  * [[MarkLinimon/KitchenerNotes|MarkLinimon/KitchenerNotes]] (notes from a hackathon in 2019)

Tooling:

  * https://adventurist.me/posts/00301 (notes on searching Bugzilla via the command line)