Am Sonntag, 15. November 2009 22:23:34 schrieb Christian Ohm: > On Sunday, 15 November 2009 at 21:11, Dennis Schridde wrote: > > Then someone actually tried to run the game on, say, Windows. "Oups, it > > crashes in level 17 of campaign 40 now, and it is talking about some > > wrong filename" -> "fix, push out a new build". > > That doesn't sound like a bug that would be detected in a few days, since > we don't have any dedicated testers for every release... Exactly. But there are these users which actually happen to be playing at that level right now, and they will find such issues in the build system / a mod / a new file / ... right when they install the new version.
Admitting that my example was a bit far fetched, several times situations occurred, where quick users, using the tarball right when it was announced, found issues which we missed before. That even happened just hours after the announcement, so in just a few hours there were several versions floating around. Resulting in different OSes, arches or distros having different bugs to fight with. It was annoying to work with: Crashdumps did not match the actual code, bugs appeared which should not happen, tarball-checksums for distros like Gentoo failed, other distros did not notice the replaced tarballs at all, etc. Thus it seemed better to wait a bit longer before making the final tag public, to catch such situations. (Eager users are still downloading tarballs right when the ML says "its uploaded", or even download from SVN. And they also can cope with "we retagged, download again". At least that's how it was back then.) If it could be guaranteed that every OS/arch/distro is being built for and tested thoroughly immediately after the tag happened (and not before, since that calls for inconsistency), then I agree that this could work, too. As a safety measure the forced slowdown seemed appropriate. A strict code-freeze for, say, a week, including the thorough testing on all OSes/arches as mentioned above, with the final builds being created right after the tag, might work just as well. Again, only provided that it is guaranteed that everything actually happens as planned and everyone starts working during that freeze already. Experience and this thing being a game, run in spare time, make me sceptic. But why not try something new, if you feel that suits you better. I (and thus the release-checklist) certainly do not want to stay in the way of advancement, but rather explain why some rules were invented. If there are better solutions to old problems, that is certainly a good thing. Regards, devurandom
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ Warzone-dev mailing list [email protected] https://mail.gna.org/listinfo/warzone-dev
