On Sunday, 15 November 2009 at 21:11, Dennis Schridde wrote: > What we had once, was "tag, push out src tarball", then the Windows guy would > come and "try to build, oh it does not, fix, push out windows build". > A little while later someone is building for Mac: "try to build, oh it does > not, fix, push out the mac build".
Well, now we have Buginator who does a Windows build for release, so no problems there, and Linux build breakage is also no problem recently I think. That leaves the Mac builds, which I can't say much about. > 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... > What we had in the end was 1 tag, 1 tarball, and 3 builds from revisions (or > not even that) no one was able to figure out later on. > Saying "we are going to tag next week, please build and test" did not help a > bit. > Announcing the release on the website along with uploading the tarballs made > the stuff just worse, because ppl actually downloaded that stuff (who can > blame them), and, in case the release contained critical errors and thus had > to be retagged, the confusion increased. > Thus the rule: "wait a few days between tagging and releasing". > I am very sceptic that quality will not suffer if you rely on ppl testing > after someone writes an email to the list that he is about to tag 24h later. > Not only are not many ppl reading this, they are also too lazy to actually > test, especially not quickly, and the actual workers have full time > schedules, > which do not permit them to throw away whatever they were doing at that > moment > and just jump into WZ QA instead. Hm, AFAIR SVN wasn't broken that often recently, and usually gets fixed quite fast when it is. And if something in the game is broken, chances that someone will find it in the few days are few, > > > Download page since this is a beta. But usually, you just remove all > > > other downloads from the download page, so for a short period of time, > > > no one other than Windows users (and people who compile from source) > > And people who can read and find the SF/GNA links. > But no users. Since users usually do not dig into any devstuff sites for > links. And nobody actually reads the downloads page, it seems... there is an "older releases" section with links to the correct SF/GNA dirs (admittedly the first link is to the wiki releases page that wasn't updated since 2.2 beta2, I brought it somewhat up to date, though I left the gathering of the various binary links to someone else). > > Do we have someone else who can make (good) Windows builds? I thought there > > were some problems with the crashdumps or something if you don't have > > exactly the right setup. > There are issues (but they are fixable - don't look at me, I don't have time). > If Buginator creates the Windows builds, that would be a nice task already. > I think what Zarel means is that he does not also have to carry out the > tagging, tarballing, announcements, etc, if that would mean that others > cannot > get stuff to build and test in time. Well, Buginator does the Windows builds, and those should be done from a tag (and I think doing the tarball then isn't really much work anyway). Though he wouldn't have to do the actual announcement, maybe just prepare a rudimentary post in the staff forum that then gets finished and moved to news when all builds are available. _______________________________________________ Warzone-dev mailing list [email protected] https://mail.gna.org/listinfo/warzone-dev
