The ATI/AMD Linux community also has several assets, which include an unofficial BugZilla, an unofficial Wiki, a section on the Rage3D forums, and the Phoronix Forums. While the BugZilla and Wiki are unofficial, they are linked to from the AMD website and developers are known to browse the bug list from time to time.
On the NVIDIA side, there is an official section setup on the NvNews forums and an unofficial support and discussion area on the Phoronix Forums. At this time there is no public BugZilla for NVIDIA users.
While R200 product support still does exist in a driver branch after being discontinued in the fglrx 8.28 release, AMD has no plans to release an updated R200 class driver. AMD's belief behind this is the open-source community was given the needed specifications a number of years ago and the X.Org Radeon driver is reasonably well supported (except for TV-Out due to Macrovision).
If you're curious as to what Linux distributions the AMD developers use when working on these drivers, there is no single distribution other than matching the common choices of the Linux community. Matthew Tippett happens to be an obsessive-compulsive daily Ubuntu dist-upgrader tracking Ubuntu Gutsy Gibbon.
While the AMD beta program is closed for the public, deserving individuals are allowed to join the program. AMD is always looking for new distribution vendors to join this program with vendors being more than welcome to provide packaging scripts for their respective distribution. If you can provide a particular value to the beta testing cycle, let us know in the Phoronix Forums and we would be glad to pass along prospective names to AMD.
While AMD's Catalyst development cycle for both the Windows and Linux drivers is a bit more complicated than what we were allowed to share with you today, each AMD Linux "fglrx" driver release takes usually about eleven to twelve weeks from start to finish. With the development, validation, beta, and bake phases, there are always at least two releases being prepared. This rigid development cycle allows AMD to release updated drivers on a monthly basis while ensuring that each driver has been tested and contains more changes than just a simple version bump. It is also due to this structured development cycle why AMD generally cannot deliver same-month support for new kernels and X.Org releases.
Stay tuned to Phoronix as AMD should have some interesting things in the pipeline for later this year...