Reporting moodle bugs using moodle tracker

I noticed today moodle 2.3 was released a couple days ago.  I clicked on the fixed issues link for the build and was reminded how many people work on the core moodle code and how many people faithfully report bugs via bugtracker when they encounter something buggy.  I went to a moodle moot last summer where the leaders spent over an hr showing the audience how to use the bugtracker, how to report and vote on already reported bugs.  They said things like "its how the core developers decide what to fix and how to prioritize".

Clicking on any of the reported and fixed bugs in the release provides great detail and comments about the problem and how it was resolved.

I remembered a bug in the automated course backup area that I noticed when upgrading from 2.1 to 2.2.   I went into moodle tracker, logged in and did a search for the bug, typing in " automated course backup", not too specific, and found the exact problem I was having already reported.  I voted it up. I am a good moodle citizen.

We should all use the moodle tracker and report bugs!

I also noticed with the 2.3 release, the core MySQL version changed from 5.0.25 to 5.1.33.  Pay attention to those versions. I am in the process of setting up two new moodle servers, with new moodle instances, I will plan on using the 2.3 version.