>> The downloads on http://ioquake3.org/get-it/ are over two years old >> now. There have been over 400 commits since then and some of those fix >> real bugs[1]. Can we put out a new release? >> >> [1] And then again... >> http://svn.icculus.org/quake3?view=rev&revision=1895 > > > blah blah blah
And just to be clear, bugfixes are really appreciated, but it doesn't have a great impact on end-users unless there's something that people are really polarized about or excited about (see: mouse input drama). When there's a flurry of changes, a project like Reaction puts out a call to an Icelander to synch our project with the latest ioq3 svn (because only oldschool Viking blood can accomplish such a feat!) We don't wait for a "release" per se. I doubt other projects do, either, they just synch to the latest svn on a per-need basis. I see a release as wholely to attract new users to the project, the concept, and the binary and related projects as a whole. It's a PR push and I think you need to look at what you have to do to maximize the impact and figure out what goals you want to accomplish. Existing projects like Reaction don't care. It's for the non-programmers and to attract new users and projects through the resulting publicity of "hey we got a new version and here's all the cool stuff it does!" Monk. _______________________________________________ ioquake3 mailing list ioquake3@lists.ioquake.org http://lists.ioquake.org/listinfo.cgi/ioquake3-ioquake.org By sending this message I agree to love ioquake3 and libsdl.
