> What are they for except to report on their behavior, confirm fixes, > find bugs? I don't remember any better behavior from milestones.
They are mainly to be used to verify individual fixes so we can ensure they are fixed before a milestone. Honestly, unless any of you guys are running Windows, a lot of the problem reports you give us are not very useful. Our main goal is to make the OS/2 browser runb like the Windows browser. So the best thing anyone can do is run Windows and OS/2, run the same build on both, and say "this is different between Windows and OS/2." As far as the hangs, crashes, etc. go, we very seldom see reproduction scenarios for these so we can't reproduce them. Bugs like "Warpzilla hangs" and "warpzilla crashes" are not very useful. There are tons of these that are machine specific, and with OS/2 having no useful tools for doing stack traces when you crash and things like that, we don't have much to look at. When you put on top of that the fact that most people are running FixPak 15 (which incidentally is NOT the most current FixPak and hence NOT what we test on), as well as private PMMERGE fixes, test kernels, tons of WPS enhancers, etc., there is no way to know what is causing any particular problem. What we need is other people building and debugging the browser. That's how the other builds are so successful. The Warpzilla project has tons of users/testers but very few developers. The IBM Warpzilla Team Felix Miata wrote: > Michael Kaply wrote: > > > Then stop using the nightlies. > > > There is no telling how stable they are at a given point in time. > > What are they for except to report on their behavior, confirm fixes, > find bugs? I don't remember any better behavior from milestones. > -- > "A general dissolution of principles and manners will more surely > overthrow the liberties of America than the whole force of the > common enemy." Samuel Adams > > Team OS/2 ** Reg. Linux User #211409 > > Felix Miata *** http://mrmazda.members.atlantic.net/
