Differences

This shows you the differences between two versions of the page.

--- bugathons:june2008 [2008/06/17 17:46] – Checkpoint work-in-progress GavinAtkinson
+++ bugathons:june2008 [2018/03/18 13:12] (current) – remove dead links. MarkLinimon
@@ Line 1: / Line 1: @@
-This page details rough plans for Bugathon #5, which will take place between 20-22nd June, 2008.
+This page details rough plans for Bugathon #5, which took place between 20-22nd June, 2008 on #freebsd-bugbusters on efnet.
 ===== Background =====
-Unlike some past bugathons, we've decided to set a particular focus for Bugathon #5: to try to evaluate and possibly commit as many PRs with patches as is possible.  Around 1300 PRs contain patches, and a significant number of these may well be committable as-is.  I've documented why we're focussing on this in more detail [wiki:self:Bugathons/patch here].
+Unlike some past bugathons, we've decided to set a particular focus for Bugathon #5: to try to evaluate and possibly commit as many PRs with patches as is possible.  Around 1300 PRs contain patches, and a significant number of these may well be committable as-is.
-Since the last bugathon, [[/MarkLinimon|MarkLinimon]] has put a huge amount of work into the ["[[/BugBusting|BugBusting]]"] wiki page, and the pages leading from it.  There is now a large quantity of information available on the [wiki:self:[[/BugBusting|BugBusting]]/Resources resources available] for anyone interested in helping out.  For those wanting to help out, please add your details to ["[[/BugBusting|BugBusting]]/Volunteers"], and join us on IRC on #freebsd-bugbusters on efnet.
+Since the last bugathon, [[/MarkLinimon|MarkLinimon]] has put a huge amount of work into the [[/BugBusting]] and [[BugBusting/Resources]] wiki pages, and the pages linked from them.  There is now a large quantity of information available for bugbusters on the [[BugBusting/Resources]] page for anyone interested in helping out.
 ===== Plan of action =====
-We'll convene on the IRC channel during Friday 20th June, and start to look through PRs.  A list of PRs tagged as containing patches is posted weekly to freebsd-bugs@, and is also available as [http://people.freebsd.org/~linimon/studies/prs/prs_for_tag_patch.html an interactive version].  For those with freefall access, a list of unallocated PRs containing patches can be generated with:
+We'll convene on the IRC channel starting Friday 20th June, and start to look through PRs.  A list of PRs tagged as containing patches is posted weekly to freebsd-bugs@, and is also available as [[http://people.freebsd.org/~linimon/studies/prs/prs_for_tag_patch.html|an interactive version]].
+For those wanting to help out, please add your details to [[BugBusting/Volunteers]], and join us on IRC on #freebsd-bugbusters on efnet.
+==== Volunteers ====
+For those helping out who are not committers, the best plan is to pick a PR 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 [[http://people.freebsd.org/~linimon/studies/prs/recommended_prs.html|PRs recommended for committer evaluation by the bugbusting team]] by anyone with freefall access so that it doesn't get lost.
+==== Committers ====
+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 [[http://people.freebsd.org/~linimon/studies/prs/recommended_prs.html|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.
+[[/GavinAtkinson|GavinAtkinson]] has also compiled a list of PRs requiring MFC to 6.x.  These are PRs that have sat in HEAD and RELENG_7 for at least 5-6 months, but have not been merged to 6.x.  Have a look, see if any are yours, or that you are interested in taking.  If you own some of them but will have no ability to test on RELENG_6, it may be worth adding them to the recommended list for somebody else to MFC.
+For those with freefall access, a list of unallocated PRs containing patches can be generated with:
 ''%%query-pr -q -x -t '\[patch\]' -r freebsd-%%''
-Similarly, to list the non-ports PRs, use:
+Similarly, to list (e.g.) non-ports PRs, use:
 ''%%query-pr -q -x -t '\[patch\]' -r freebsd- | awk '$3 !~ /ports/ { print }'%%''
-For those helping out who are not committers, the best plan is to pick a PR 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 [http://people.freebsd.org/~linimon/studies/prs/recommended_prs.html PRs recommended for committer evaluation by the bugbusting team] so that it doesn't get lost.
+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.
+----
-For committers, it would be good if mention of the bugathon was included in the commit message - this helps to get word out that it is occuring, and also shows people how effective bugathons can be.
+{{tag>Historical}}