blackheartstar
26.02.2007, 13:21:26
(This post was last modified: 26.02.2007, 13:57:27 by blackheartstar.)
1. Feature Freeze - is that not what he is doing now?
2.Use a simple, easy, widely accepted numbering scheme - not sure if you mean inside the .ini (example the aitargeting) or RP releases.
3.Make all versions successors of the previous one - revision #33 is the successor of CE and the predsuccessor of CE#36.
4.Make available an internal beta - Why do you guys feel its so important to have closed testing I see no advantage other than someone will have a go at it before everybody else. Your going to go through the exact bugs that we get now only with fewer people to track them down.
5.Update ModEnc correctly and quickly - He is bad at english so probably not the best idea to have him do this. Plus he made it and gives some help with release it shouldnt be his resposablity to do everylittle thing. It is editable by everyone?
6. Involve the coders of big RP-using mods, like AG, Speeder and Nighthawk in your planning. Actively ask them what they need. These are the people promoting RockPatch. If they don't like it, there's no need to continue coding. - This is what its really about I guess by looking at the current events as some people are not getting exactly what they want so trash it.
7.Look at the votelist. - at the time this was brought up several things from the vote list had been done or worked on. Not a valid complaint. Espeacialy after I just looked at it where FullPalette= is in first. FourthSide, Cloned SuperWeapons, and New Prerequisite tags are all towards the top to further negate this complaint. Its More about advice #6 above than this.
8.Look at the wishlist - Just about everything hes done is in the wishlist. Maybe 2-3 things are not if that. If need be afterwork Ill pull them for quotes if youd like to see but I think it has to do more with advice#6 than this.
9.Update the goddamn bugtracker quickly, actively and precisely- Looking at the bug house he does need to be more precise.
10.Listen. To. Us. It's like I said last post - He does he changed TUT back he put the number system on AI targeting back. We are on a feature freeze, and the last revision addressed the bugs that where brought to his attention the most even if one really wasnt a bug (TUT=) but hey its fixxed.
So what exactly is it you guys want? Other than your way or no way as it seems your stance is.
2.Use a simple, easy, widely accepted numbering scheme - not sure if you mean inside the .ini (example the aitargeting) or RP releases.
3.Make all versions successors of the previous one - revision #33 is the successor of CE and the predsuccessor of CE#36.
4.Make available an internal beta - Why do you guys feel its so important to have closed testing I see no advantage other than someone will have a go at it before everybody else. Your going to go through the exact bugs that we get now only with fewer people to track them down.
5.Update ModEnc correctly and quickly - He is bad at english so probably not the best idea to have him do this. Plus he made it and gives some help with release it shouldnt be his resposablity to do everylittle thing. It is editable by everyone?
6. Involve the coders of big RP-using mods, like AG, Speeder and Nighthawk in your planning. Actively ask them what they need. These are the people promoting RockPatch. If they don't like it, there's no need to continue coding. - This is what its really about I guess by looking at the current events as some people are not getting exactly what they want so trash it.
7.Look at the votelist. - at the time this was brought up several things from the vote list had been done or worked on. Not a valid complaint. Espeacialy after I just looked at it where FullPalette= is in first. FourthSide, Cloned SuperWeapons, and New Prerequisite tags are all towards the top to further negate this complaint. Its More about advice #6 above than this.
8.Look at the wishlist - Just about everything hes done is in the wishlist. Maybe 2-3 things are not if that. If need be afterwork Ill pull them for quotes if youd like to see but I think it has to do more with advice#6 than this.
9.Update the goddamn bugtracker quickly, actively and precisely- Looking at the bug house he does need to be more precise.
10.Listen. To. Us. It's like I said last post - He does he changed TUT back he put the number system on AI targeting back. We are on a feature freeze, and the last revision addressed the bugs that where brought to his attention the most even if one really wasnt a bug (TUT=) but hey its fixxed.
So what exactly is it you guys want? Other than your way or no way as it seems your stance is.