<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Bug-Bash on Selenium</title><link>https://deploy-preview-2575--selenium-dev.netlify.app/tags/bug-bash/</link><description>Recent content in Bug-Bash on Selenium</description><generator>Hugo</generator><language>en</language><lastBuildDate>Fri, 05 Apr 2024 05:24:49 -0500</lastBuildDate><atom:link href="https://deploy-preview-2575--selenium-dev.netlify.app/tags/bug-bash/index.xml" rel="self" type="application/rss+xml"/><item><title>Bug Bash Aftermath</title><link>https://deploy-preview-2575--selenium-dev.netlify.app/blog/2011/bug-bash-aftermath/</link><pubDate>Mon, 31 Jan 2011 00:00:00 +0000</pubDate><guid>https://deploy-preview-2575--selenium-dev.netlify.app/blog/2011/bug-bash-aftermath/</guid><description>&lt;p>What a week! I’m almost (almost!) sorry that the Bug Bash is over. I’d like to say thank you to everyone involved in the Bug Bash, from those reporting issues, through those brave souls (Dharani, Anthony, Jari!) who went through the issue tracker, applied labels and made sure the issues were still fresh, all the way to those contributing fixes. And the top five bug fixers were?&lt;/p>
&lt;ol>
&lt;li>Jari Bakken (24 issues)&lt;/li>
&lt;li>Simon Stewart (21 issues)&lt;/li>
&lt;li>David Burns, aka: AutomatedTester (11 issues)&lt;/li>
&lt;li>Jim Evans (10 issues)&lt;/li>
&lt;li>Michael Tamm (6 issues)&lt;/li>
&lt;/ol>
&lt;p>Some interesting nuggets of information:&lt;/p></description></item><item><title>Bug Bash: 24-30 January</title><link>https://deploy-preview-2575--selenium-dev.netlify.app/blog/2011/bug-bash/</link><pubDate>Fri, 21 Jan 2011 00:00:00 +0000</pubDate><guid>https://deploy-preview-2575--selenium-dev.netlify.app/blog/2011/bug-bash/</guid><description>&lt;p>When the Selenium (&lt;code>http://selenium.googlecode.com/&lt;/code>) and WebDriver projects merged, all those moons ago, we moved the infrastructure from something we hosted to Google Code. One reason for doing this was to make it easier for people to file bugs and feature requests. And it looks like people have been filing a &lt;em>lot&lt;/em> of bugs and feature requests.&lt;/p>
&lt;p>In the run up for the 2.0b2 release, we’ll be running a Bug Bash. This will run from the 24th January all the way to the end of the 30th January. The aim will be to focus on clearing our bug list as much as possible, so that beta2 will be the best release of Selenium yet. We will, of course, be recognizing people who squash the most bugs here on the blog, and we’re hunting out goodies to mail to the top bug bashers once the week is over.&lt;/p></description></item></channel></rss>