MarkLinimon suggests that we try to use the momentum we have gathered during and after the last bugathon to try to get some commits into the tree. Here's some other ideas.

Here are the suggestions I have for PRs to be committed:

• PRs that are posted as recommended for committer evaluation by the bugbusting team.

• PRs in the 'patched' state. These represent code changes that have already been committed to whatever represented -CURRENT at the time, and have been flagged as needing merges to a release branch. Many of these have probably already been merged. Someone who is interested can look through cvsweb and determine whether or not this is the case. For ones that have, they can be closed; for ones that have not, whoever committed the change should be notified. (Usually they have the PR already assigned to them, but not always.)

• There is now a list of PRs in the patched state but also have commits. This was created by following a suggestion from RobertWatson that searching PRs for “dfilter@FreeBSD.org” would show PRs for which fixes have already been committed. (I have already gone through all the ones that were in 'open' that needed to be changed to 'patched'; there were ~31 of them.) These will overlap with the above. In many of these cases, I've pinged the assignee already.

• Whichever of the above apply only to 5.X should be added to the PRs for 5.X list. Probably in May, when 5.X goes EOL, we can close them all.

• PRs that have been evaluated in the past month, as a result of the last Bugathon. (I'll need some help gathering these together).

In addition, here are some other ideas:

• Work through the PRs in the feedback state which have not been modified in 2 months to see which ones can be closed with submitter-timeouts.

• Have folks take a look at the new PRs in the last 7 days.

• Try to catch up on the ports PRs now that the slush has been lifted. (There is a portsmon equivalent of that page.)

• And, of course, sign up more volunteers.

Closed PRs:

Thanks to everyone for participating.