June 29, 2010

227 words 2 mins read

Operation Cleansweep, how it all works

State of things: Operation Cleansweep

Operation Cleansweep is in full swing and we’re slowly but steadily working our way through 2000 patches. You should be part of this! It’s easy and a lot of fun. Join #ubuntu-reviews on irc.freenode.net and just check out our review guide. The process is quite straight-forward.

I thought it’d help to have a look at a few patches together and see how the process works, so here we go. Consider these few bugs and what was done there:

  • 544242 This bug was opened with a patch provided by the reporter. It was subscribed by the subscription script with the patchtag. The patch was forwarded upstream, and recieved the patch-forwarded-upstream tag. After upstream accepted this patch, it recieved the patch-accepted-upstream tag and is ready to be fixed in Ubuntu.
  • 33288 The initial patch tag was changed to patch-needswork based on upstream comments.
  • 523349 The patch was forwarded to Debian and accepted there (patch-accepted-debian).
  • 544242 The patch was forwarded to Upstream GNOME (patch-forwaded-upstream) and after some discussion accepted (patch-accepted-upstream) there.
  • 462193 The patch was forwarded to Debian (because it just contained changes to the debian/ directory) and accepted there.

That’s not too bad now, is it? Join in on the fun and make Ubuntu and upstream projects rock even harder!

Watch out for the Ubuntu Developer Week announcement, we’ll have a couple of great sessions about this topic too!

comments powered by Disqus