I suppose that I've already helped out on number 2, which I think is completely doable for most anyone to help out with; I guess the more important thing is, what's involved with actually declaring a release? Is there a process, or is magic involved? Is there a requirement for making binaries, and what's that like (I'm aware that the windows build requires a fair amount of black magic)?
I guess what I'm trying to suggest is that it might happen more often if more people were capable of performing some of the tasks (ie making a release would be less of a time-burden on the over-burdened individuals currently involved).
Bill
Yep. It goes something like this:
The current release manager thinks it's been to long since the last release.
The release manager asks for outstanding issues� including an up to date CHANGES.
Outstanding issues are fixed and someone will check in new features in panic� to get them in the new release. Repeat 2.
If the release manager did not time out in the above loop a beta is done. Repeat 2.
If the release manager did not time out in the above loop a release is done.
� Room for optimizations: Someone could take it upon him or her to keep an updated list of issues, separated in classes like "securty", "regressions" and "bugs". Preferably in Crunch.
� Room for optimizations: Getting releases out more often always makes this step less troublesome.