James,
Did you get this ping? Christian FreedomWorks Inc. US: 609-858-2290 Canada: 905-228-0285 Fax: 347-296-3666 Email: [email protected] www.FreedomWorks.ca From: Christian Menge [mailto:[email protected]] Sent: Saturday, May 08, 2010 10:33 AM To: FlightGear developers discussions Subject: Re: [Flightgear-devel] June / LinuxTag release James, We might be interested in helping out with the Windows build. We have access to a linux shared server and several Windows 7 machines with Visual Studio 2008 / 2010. Let me know if this works for you? Christian Menge FreedomWorks Inc. US: 609-858-2290 Canada: 905-228-0285 Fax: 347-296-3666 [email protected] www.freedomworks.ca On reFri, May 7, 2010 at 12:06 PM, James Turner <[email protected]> wrote: I want to make a 2.1 FG release, at the end of this month, or the very start of June. As far as I can see, the current code is pretty good - many bugs have been fixed since 2.0, and while I'm sure some new ones have crept in, I don't have many code quality concerns - if we were to cut tarballs from the source code today, we'd definitely be in a better place than 2.0 in terms of bugs. (If people know of regressions from 2.0, or regressions in 2.0 from 1.9.x, I hope they would mention them here, or even in the bugtracker) Anyway, the key thing - what are the steps to make a release happen. I'm seeking to capture the actual steps (and ideally script them), so even if Curt & Durk both get hit by the proverbial bus tomorrow, we can still make a Flightgear release ever again. But also, I'm seeking to remove the human factors from the release process, and especially not feel that we're overloading people just because a release needs to happen - eg, around LinuxTag Durk is often quite busy organising things :) My build system ( http://zakalawe.ath.cx:8080/ ) is working well for Mac and Linux - MinGW is giving me some pain, I will look into cross-compiling mingw this weekend. If anyone wants to volunteer some time, a Windows box with Visual Studio, some disk space, and bandwidth, I am happy to work with them to get an automated VS build going. Adding more automated steps, even ones which only happen for 'special' builds (eg, a release candidate) is extremely trivial. Regards, James ------------------------------------------------------------------------------ _______________________________________________ Flightgear-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/flightgear-devel
------------------------------------------------------------------------------
_______________________________________________ Flightgear-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/flightgear-devel
