Bug reporting guidelines
Somehow a bug or two may have slipped into Aegir. Eek!
Reporting bugs
Reporting bugs is a great way to contribute to Aegir and it helps all of us (developers and users both) shape Aegir into the fantastic Drupal management system we want and need.
Mis-reporting bugs that are due to not following instructions or skipping steps, not providing enough information or duplicating reports, however, can be a distraction to the development team and waste precious resources. So, help out by following these guidelines for reporting bugs.
Before reporting a bug:
Read the FAQ to check that your problem isn't answered there or that there isn't a workaround
Review these tips on configuring Aegir, Drush, Apache and more, and avoid common mistakes.
Search this community site to see if your problem or question has already been addressed.
Look at the current issues for all of the Aegir-related issue queues to see if the bug has already been reported.
If it's a new issue that you can't find anywhere else, you can come visit us in IRC, ask on the mailing lists or in the community discussion space here, and the community can help you decide whether your issue is a bug or some other problem.
So it's a new bug? To report a bug, file an issue on: * Hosting (if the issue is in the frontend) * Provision (if the issue is in the backend) or * Hostmaster (if it is in the installer, a documentation bug, or if you don't know where the issue should go). * Eldir (if it's an issue with the default Eldir theme that ships with Aegir.)
Feature Requests
Feature requests are, of course, always welcome in these queues as well. To get an idea of where Aegir is headed with new features, you should first consult the Aegir Roadmap and Project Goals - we may be already on it!