Oh, you're very optimistic and cheering... I'm nearly OK for the freeze, even if it is really really demotivating if nobody began to fix bugs. It's easy to say "Now we don't develop anything more" but it's more difficult to fix bug...
Yes, it may sound demotivating, but it's not. A lot of linux distro do the same thing, this just brings more control over everything. And it's not we do not develop anymore, there was/are too many things that were getting developed. And every new tweak/hack every now and then brings new bug. What I'm trying to say, is that wormux is too buggy! It's defintely good to get more things developed, but I think stability is more important then new things. Stable solid game, is more playable if you can finish a fight without game crashing or bugs that just piss you off, rather then have a bleeding edge game that you cannot finish but feels great. Devel freeze before some major releases (and imo 0.8 is major release) is definetely ok.
And any new bug should be fixed,
ANY BUGS should be fixed if it is under our control, why just new bugs ???
Yes, what I meant with this whole "new bug/old bug" phrase is that there are a lot of bugs in the tracker that havent been taken care of for a long time. And yes dont get me wrong, I'd definetely like old bugs being fixed, I just thought everyone forgot about them or something.
I hope you are agree with you :)
So if you want to help and to be positive in your action, stop saying there are plenty of bugs, and try to debug it, report bugs precisely. Currently there is only 20 bugs opened but translations. Some bugs are waiting for answer for people who has reported the bugs, some others are waiting for test, etc....
Criticize is easy, but it will not be better if you say "it's bad", it will be better if someone do something to do it better!
Yes yes yes :) I know I only sound as on keep on "bitching" and saying things without really doing stuff. As all of us do wormux in our free time, I'll be completely free as soon as my exams end. So I'll do my best to fix some bugs I have some clues how they reproduce.
PS: be aware that you have introduced a bug in your previous commit (r2118) in the jetpack.cpp. m_is_active is not related at all with you want to do, and you must not change it!!! I know it was difficult to test since the keys management was partially broken. (Now jetpack is unusable on my computer, it's really too fast). Freezing means also no tweaking.
Yes yes, I had it reproduced, and then by second time I sent it I got that bug coming back :/ I'll definetely take care of this ASAP. And yes, devel freeze should mean no hacks! :)
It's not nice, it's mandatory!! Network code has been written to be platform independent and to be playable between different architectures and exploitation system. If it doesn't work between x86 and x86_64 or x86_64 and PPC, there is at least one bug. It must be fixed!
Amen to that Adnan (AbsintheSyringe) On 2/9/07, Matthieu Fertré <[EMAIL PROTECTED]> wrote:
> On 2/8/07, Eddy Petrișor <[EMAIL PROTECTED]> wrote: > >> Should I add to this that it would be nice if it worked between x86, >> x86_64 and powerpc machines? > It's not nice, it's mandatory!! Network code has been written to be platform independent and to be playable between different architectures and exploitation system. If it doesn't work between x86 and x86_64 or x86_64 and PPC, there is at least one bug. It must be fixed! > Why not disable things which are not used in the gna interface? At the beginning of the world, nothing is used. > I always thought that the patch tracker is somewhat overlapping the > bugs tracker. It would be nice to be able to get people to submit > patches without handing out svn access to everybody. There's no need to have svn access to submit patches. It's a political choice of the core team to quickly open svn in write access. When there is an important activity, patching the trunk with a one week ago patch is sometimes really difficult, more if we have not created the patch by ourselves. If someone has written a good patch, we are mainly sure that he will try to do good work, so why not opening him the svn ? Well, perhaps we can close some accounts, but be aware that wormux would never be as it is now if we have not open the svn so easily! And don't forget that if we do not open svn access so easily, you perhaps still not have the access ;-) Matt (gentildemon) _______________________________________________ Wormux-dev mailing list Wormux-dev@gna.org https://mail.gna.org/listinfo/wormux-dev
_______________________________________________ Wormux-dev mailing list Wormux-dev@gna.org https://mail.gna.org/listinfo/wormux-dev
