bugs/sync errors/network load/CPU usage/etc

jj · Post by jj » 01 Sep 2006, 09:16

guys, you spring developers have done excellent work but i want to discuss some basics about programming.

The best way to work in my opinion is:
1. Make a plan
2. make sure everything is almost bugfree
3. release it
4. now the masses can test it
5. no bugs? then implement new functions
then repeat step 2,3,4,5 again and again

my suggestion is to wait with new things till known bugs/problems are solved

Since i'm playing spring i have discovered a lot of new cool functions with each new release, but the bugs/sync errors/network load/CPU usage/etc. are increasing.

I know the fun part of programming is to add new things.
But ppl want a stable smooth game, we dont "need" shadows and stuff made for the supercomputers.

I have played spring for 700 hours now and i hope a lot more good hours will come.
keep on doing the good thing,
and thanks for the good work.

a regular spring player/mapper

Argh · Post by **Argh** » 01 Sep 2006, 09:28

I do not agree with this characterization of where Spring stands, and where it is going, and neither does anybody else who is actually paying attention to the details of its development.

Bugs are getting fixed, steadily- and new features are getting made. These are not mutually-exclusive scenarios. One look at SVN would show that many new bugfixes are introduced on a regular basis, and as modders learn how to optimize their content, the only serious causes of lag will be people with crappy computers, frankly- and Spring would not be helped by catering mainly to that crowd. Spring should be built for the future, not the past.

Post by **Tim Blokdijk** » 01 Sep 2006, 10:47

jj wrote:guys, you spring developers have done excellent work but i want to discuss some basics about programming.

The best way to work in my opinion is:
1. Make a plan
2. make sure everything is bugfree
3. release it
4. now the masses can test it
5. no bugs? then implement new functions
then repeat step 2,3,4,5 again and again

...

Were young guy's here, all we know is how to Release Early, Release Often.

Argh · Post by **Argh** » 01 Sep 2006, 10:51

"Release Early, Release Often, and Let Them All Patch It" is how Linux was built

Tobi · Post by **Tobi** » 01 Sep 2006, 11:13

Note that we started using a feature frozen release branch. With it, it will also be possible to release bugfix only releases (ie. 0.73b2 0.73b3...) between 0.73 and 0.74.

So you got the idea just after we did

Oh, and btw, point 2 is impossible with spring

(or any big software package..)

Post by **jcnossen** » 01 Sep 2006, 11:17

Can't say I like this patronizing tone, go play another game if you don't like it. One that isn't being actively developed.

Torrasque · Post by **Torrasque** » 01 Sep 2006, 11:29

jcnossen wrote:Can't say I like this patronizing tone, go play another game if you don't like it. One that isn't being actively developed.

I think you're misundestanding jj.
He is gladly proposing himlseft to make :
A plan, correct all the bug, release it and taking report from unhappy user.

Das Bruce · Post by **Das Bruce** » 01 Sep 2006, 12:24

Tobi wrote:Oh, and btw, point 2 is impossible with spring (or any software package..)

Fixed.

AF · Post by AF » 01 Sep 2006, 13:54

havent we had this discussion before jj?

jj · Post by jj » 02 Sep 2006, 07:36

Can't say I like this patronizing tone, go play another game if you don't like it. One that isn't being actively developed.

I didnt say i dont like it, I said i like it a lot.
And if i'm building stuff, coding, mapping, music making, then i always like to hear ideas or suggestions from ppl, even if it is the stupid thing i ever heard.

Lets say you are right, the bugs are just increasing in the Beta-versions.
But the functions are increasing too, so the possible causes for a bug could be increasing too.
But maybe you have to do it this way because you are coding with a large group of programmers: everyone has his own task.

I have another idea, forgive me if i'm wrong, i dont know how you are working atm:

fix some bugs, release the beta version, in the meantime dont release the new functions (save them for the new release), cant find more bugs=release the new one with the new functions.
new funcions = new bugs --> beta-version.

This is slower but maybe in the end it makes things easier,
It makes things more clear for the end-user,
now they now a beta version could cotain bugs and they cant wait for the next release with the new goodies.

jj · Post by jj » 02 Sep 2006, 07:39

AF wrote:havent we had this discussion before jj?

i dont think so.

Torrasque · Post by **Torrasque** » 02 Sep 2006, 11:23

jj wrote: blabla

I think you don't understand that it's what they do.
It just that it's not so easy, and still with such beautifull way do manage your projet, there will be always some bugs and problems left.

Tobi · Post by **Tobi** » 02 Sep 2006, 11:28

jj wrote:I have another idea, forgive me if i'm wrong, i dont know how you are working atm:

fix some bugs, release the beta version, in the meantime dont release the new functions (save them for the new release), cant find more bugs=release the new one with the new functions.
new funcions = new bugs --> beta-version.

That's basically how we will be working from 0.73 and higher (with the release branch etc.) ...

Spring RTS Engine

bugs/sync errors/network load/CPU usage/etc

bugs/sync errors/network load/CPU usage/etc are

bugs/sync errors/network load/CPU usage/etc

Re: bugs/sync errors/network load/CPU usage/etc