I've decided to register again, although I don't like it (ignoring mails still consume network resources).
Matthieu Fertré a écrit : > I understood, but releasing alone with no help spending 2 hours of my > time for a game I never played was quite frustrating too... And since I > have no more time to test during the evening, I say, ok, let's > releasing... You know the result. News were made on LinuxFR website > without testing it more and so on... Even huge projects like debian or gcc with dedicated release managers are often unable to get their developers to fix bugs instead of having fun adding new features. Maybe it's worth a try, though. > Well, at least in the past, we have offered you a written svn access. > You know applying patch and remember each bug report is sometimes not > easy... I dislike registering / having write access in any project, because this means some kind of real involvement. I consider myself a helper. For all I know, I might look at Wormux for 3 weeks, then you won't hear from me for the next 6 months (that's just what happened). > I'm pretty sure you can post on the bugtracker without registering. No I can't. So I registered, as I think I've fixed the SDL fullscreen bug. > Anyway, you know there is some open bugs that nobody cares about. For > instance, I have associated yeKcim with bug 5018 > (https://gna.org/bugs/?5018) a long time ago, and the result is that he > has just fixed the maps because somebody sent a comment on LinuxFR () > This is quite boring when you try to have a square management of bugs... Definitively. Another reason why I didn't want write access is that I wanted patch review. Most changes in wormux are not benign, and affect lots of parts in the code base. >> >> Second, Polygon is also already defined by the windows GDI API. This [...] > :-( The patch attached to the previous mail is good to go, I think. I think code is even cleaner that way: no need to (recursively) include tens of headers. std::isnan is troublesome. The src/network/distant_cpu.h enum would gain from a more explicit name, at the same time solving the clash with the win API. I guess the installer changes are hard to review, except for the one (deki?) that provided the most recent installers through cross-compilation. > I'm not sure that anybody will accept to spend to time to change the > makefile or the autogen.sh file, but you're right, there's something to > do, at least for Windows and Apple systems... Is the Apple maintainer active? This should be looked into with his help. Kurosu _______________________________________________ Wormux-dev mailing list Wormux-dev@gna.org https://mail.gna.org/listinfo/wormux-dev