Author Topic: Suggest a codefreeze/debugging  (Read 1354 times)

0 Members and 1 Guest are viewing this topic.

Offline gevatter Lars

  • Another wingnut
  • 213
    • http://gevatter_lars.tripod.com/
Suggest a codefreeze/debugging
Quote
The exact reason all the current builds crash like madness is since none of the new features were properly implemented and integrated into the main CVS build.

Ever tried or used 3.6 for an extended time - it is the most stabile build sine 3.5.5 and the most stabile since HTL was implemented.

What we need is the new features to be properly integrated, so coders can go bugsquashing wiht real fine stuff under their fingers instead munching over the same stuff once more.

I know there may be some bugs still left in 3.6, but to tell the truth there is one thing that CAN make them go away - use Mantis (some coder pls. correct me I guess it is outdated) and report what's wrong with it.

If FS_SCP is unstable use an actual release build, not a CVS or a feature test build (of which Bob built a thousand ones since he made a dozen new features ) - so I suggest use 3.6.

                                                                                 -Flaser


If all the troubles are comming from the many not completed changes freeze the coded! Implement the stuff as its needed and make it bugfree as possible.
I mean where is the sense in putting in more and more stuff and making everything more unstable then befor? It dosn't help anyone and all the great stuff you have done would be for nothing.

So please think about a codefreeze to implement the stuff you allready got. Then fix the bugs and after that you can still implement new stuff...but you would have at least a stable basis coders and Modders can work with.


The SCP team has done realy nice stuff and I hope you will improve the game further in the futur but atm their are some things that need to be done IMO.
So please think about it...for my part I think it would be for the better good of the SCP.
"Yes! That is my plan, and I see nothing wrong with it. I figure that if I stick to a stupid strategy long enough it might start to work."
 - comment to "Robotech: The Masters"

 

Offline Inquisitor

Suggest a codefreeze/debugging
We're pretty much at that stage again. That's one of hte reasons I was looking for new folks to help out.
No signature.

 

Offline gevatter Lars

  • Another wingnut
  • 213
    • http://gevatter_lars.tripod.com/
Suggest a codefreeze/debugging
Ah good at least I am not alone with my idea.
About helping out...the people who made the changes should know the best way to implement their stuff mostly bugfree into the code...so why not talking to them...I think they should understand the reasons and help.
"Yes! That is my plan, and I see nothing wrong with it. I figure that if I stick to a stupid strategy long enough it might start to work."
 - comment to "Robotech: The Masters"

 

Offline Flaser

  • 210
  • man/fish warsie
Suggest a codefreeze/debugging
Huh...'cause your prime coders were sucked into Ferrium and they are otherwise busy with reallife™.

Spamming aside, Inquisitor could you give a summery of the SCP time-table/goals, since we're kinda left to guess on our own with most of the serious / bugsquashin development going on in the internal - well as far as I can see it :D.

Pretty please?
"I was going to become a speed dealer. If one stupid fairytale turns out to be total nonsense, what does the young man do? If you answered, “Wake up and face reality,” you don’t remember what it was like being a young man. You just go to the next entry in the catalogue of lies you can use to destroy your life." - John Dolan