06.02.2007, 18:35:43
(This post was last modified: 06.02.2007, 18:45:58 by Bobingabout.)
pd Wrote:i admit, that was phrased a little wrong. 2 alternatives could beBobingabout Wrote:2 years and we still havn't produced a purely stable release.We??
1. 2 years and you/they still havn't produced a purely stable release.
2. 2 years and we still havn't seen a purely stable release.
by we, i didn't intend to claim any credit for the RP creation, mearly meaning the community as a whole, which, is phrased wrong anyway.
pd Wrote:yes. and probably best to replace "this" with "the".Bobingabout Wrote:but given this situation. its not as bad as it seems.What the hell do you mean by "this situation"?
I hope you mean what I stated above.
i understand that it is development work, but i feel that it is extreamly important, especially after all this time, that a version is released that can be considered "Stable", meaning, we can tell people to use that version of RockPatch, and they won't be coming back to us saying "i hate rockpatch" I've heard this a few times, "it doesn't work properly" many features don't work as intended, and get fixed in a later release, "it breaks savegames" no comment. etc...
what i'd recomend you try to do is: have 2 months of coding new stuff, then a month of beta's and bug fixing, then release the next stable, then start the whole procedure again with more new features.
doesn't matter how much you get done in these 2 months, just tie up loose ends for the beta and release, and the beta period doesn't have to be a whole month, could be a couple of weeks, depends how much work is required. but imo, this is a good plan outline.
if you wanted you could even have Alphas, where during the dev period, you ask people to test new features out for you. (usually a select few people, where a beta is a much wider audience)