The feature is there and we are slowly adding reviewers to test the system. I guess we need a way to you to apply to be reviewers.
As well as people doing "general reviews" there will also be specialist reviewers for criteria like security, usability and accessibility. Those people themselves will need to be reviewed.
For adhoc comments there is also the comments at the bottom of the description page - everyone has access to those by default.
Use a less bloaty format or post it on the web.
A lot of discussion has beengoing on about this in past months and I've just updated the Release page to clarify our support timetable.
Basically we now support 2.x releases for 12 months in terms of general backporting of bug fixes, but will continue backporting security fixes for 18 months.
You only need to maintain a branch for each Moodle branch if your code is different. Depending on your code, a 2.x branch for it will be sufficient (if it runs on all Moodle 2.x).
Yes, you do need to upload packages every time you make a "release" of the plugin. This doesn't need to be every single bug (just the same as we do with Moodle).
You are welcome to point experience users to your git repository (we have fields for that), but this database is for people who want to deal with known stable releases, not bleeding edge code. The concept of storing your releases in the central database will also make the upcoming "Check for updates" feature possible in Moodle.
In future we will definitely allow some way for trusted developers to automate the updating of our packages in the database, probably via a specially-structured RSS feed that you supply to us.
Thanks to those who've already moved their themes to the new database at http://moodle.org/plugins
We need a lot more!!