Releases

[joevenzon]

But on a serious note, before thinking about the next release, it's possible more effort should be put into what on
http://code.google.com/p/vdrift/issues/list is actually at what priority, and how many issues can be closed already. Then fix everything that's still critical, make a release, and assign tasks for future releases.

I think this is the way to go. I'm a little scared of having too much project management because it's a free-time project for everyone and holding people to deadlines is not fun, but at least listing and prioritizing tasks so when people have free time they can go and grab a task would be great.

To make this work, some person or persons would need to keep the issue list updated (if you see a bug report on the forums that you aren't going to immediately fix, put it in the issue tracker or tell them to put it in the issue tracker), keep the list prioritized, and figure out when a release should happen.

Not sure if my contributions to VDrift have been for good at all.

I would say you have done much good, and hope you will continue.

Seconded!