I agree entirely with this, with one stipulation that the network code needs to be stable and work on both Windows and Linux before .8 is released. A "hard freeze" and string freeze should come after this "soft freeze", in which nothing gets done that isn't absolutely necessary for release. Then there should be a strong push to get packages done before the release is made. The bug tracker is also full of old bugs that nobody seems to bothers with (bug #5018 for example), and that are possibly too old to matter anymore. The patch tracker seems to be worse, regardless of the fact that its almost empty.
kyle (robo210) On 2/8/07, Adnan Hodzic <[EMAIL PROTECTED]> wrote:
Last night I came up on this idea. Long time ago I was talking about (on this same mailing list), how to get to 0.8 final. I mostly put stress on bugs, wormux is full of bugs. What I would advise is to make wormux have devel freeze, right now I think it should be used. Enough of implementing various things, just fixing bugs should be done. Make a devel freeze, once it's all done and gaming is going the normal way, release 0.8. Before everything is set up, translation freeze would be made, all translations should be added and updated during translation freeze. Also I would say to move all bugs to new category, something like "old bugs" or similar. And any new bug should be fixed, and taken care of right away, since there are liste bugs that are just forgotten about. There that's my idea. I'd definetely vote yes on such decision. Adnan _______________________________________________ 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
