This page details rough plans for Bugathon #6, which will take place January 30th, 31st, and February 1st on #freebsd-bugbusters on efnet.
Our focus this time will be to work on the backlog of network-related PRs. These will include both the ~250 PRs assigned to freebsd-net as well as those assigned to others. We hope to get some commits done, as well as further classification and analysis of PRs. We will need both committers and non-committers.
the BugBusting/Resources page
kernel PRs grouped by subsystem (new page)
Plan of action
We'll convene on the IRC channel starting Friday January 30th around 6pm CEST, and start to look through PRs.
For those wanting to help out, please add your details to BugBusting/Volunteers, and join us on IRC on #freebsd-bugbusters on efnet.
For those helping out who are not committers, the best plan is to pick a PR with a patch in it, in an area that you are familiar with and/or can test, and try the patch. If you've tested it and are confident that the patch is correct, submit a followup to the PR saying so, and if possible (and concise enough) submit an example of behaviour before and after. Then, drop a message into the IRC channel. Hopefully a committer will pick the PR up, verify that it looks sensible and commit it. If not, the PR can be added to the PRs recommended for committer evaluation by the bugbusting team by anyone with freefall access so that it doesn't get lost.
As mentioned above, non-committers will be both announcing PRs that are believed to be ready to commit in the IRC channel, but also these PRs will be added to the list of recommended PRs. The source of this file is ~linimon/public_html/recommended.prs, which is world-writable, and closed PRs will automatically be removed from the generated HTML.
For those with direct GNATS access, a list of PRs assigned to freebsd-net and containing patches can be generated with:
query-pr -q -x -t '\[patch\]' -r freebsd-net
There are currently about 50 of these.
It would be good if any commits originating from this bugathon bade mention of the fact in the commit message - this helps to get word out that it is occuring, and also shows people how effective bugathons can be.