On Wed, Aug 21, 2013 at 3:51 PM, James Turner wrote: > On a related note, once the build problem is resolved, could we > generate a full installation RC package for testing? It would make it > easier for testers not familiar with Git to use it, and would be quite > handy for people like myself who do their development on Linux, but > have Windows systems available for testing but without the git > infrastructure or the time to download the entire git fgdata > repository. > > > Once the build is fixed, Jenkins should do exactly that - that's part of the > automation work I did for 2.10 - Jenkins will produce the complete install > EXE, someone just has to grab it from Jenkins and upload / mirror / seed it > as they see fit.
That's great work, Now all we need is someone with enough Windows knowledge to fix the build. > [1] 'where there's smoke there's fire', this is old terminology from the > Netscape/Mozilla TinderBox engine. I'm pretty sure the "smoke test" predates Tinderbox. I came across it when working for Xilinx in reference to hardware testing where the first test is to attach a power feed and check that nothing started giving off smoke :) -Stuart ------------------------------------------------------------------------------ Introducing Performance Central, a new site from SourceForge and AppDynamics. Performance Central is your source for news, insights, analysis and resources for efficient Application Performance Management. Visit us today! http://pubads.g.doubleclick.net/gampad/clk?id=48897511&iu=/4140/ostg.clktrk _______________________________________________ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
