Re: [Flightgear-devel] June / LinuxTag release

2010-06-21 Thread Martin Spott
Peter Morgan wrote: > Would the future also contain the MP protocol+player enviroment, ATC, MP > mapping ? I doubt that these are affected by the release process. > and also all the aircraft independant in hangars Aircraft are available here: http://www.flightgear.org/Downloads/aircraft-2.0.

Re: [Flightgear-devel] June / LinuxTag release

2010-06-20 Thread Peter Morgan
Would the future also contain the MP protocol+player enviroment, ATC, MP mapping ? a monthly release would be nice with hot fixes.. and also all the aircraft independant in hangars and is fgrun included pete On Tue, Jun 15, 2010 at 9:58 PM, Durk Talsma wrote: > Hi James, > > On Friday 07 Ma

Re: [Flightgear-devel] June / LinuxTag release

2010-06-15 Thread Durk Talsma
Hi James, On Friday 07 May 2010 06:06:32 pm James Turner wrote: > 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 Fl

Re: [Flightgear-devel] June / LinuxTag release

2010-05-10 Thread Christian Menge
discussions Subject: Re: [Flightgear-devel] June / LinuxTag release On 10 May 2010, at 13:55, Christian Menge wrote: Did you get this ping? Apologies, yes, but it's been a busy few days. For various reasons, I'd like to have a reliable Windows build locally, before I w

Re: [Flightgear-devel] June / LinuxTag release

2010-05-10 Thread James Turner
On 10 May 2010, at 13:55, Christian Menge wrote: > Did you get this ping? > Apologies, yes, but it's been a busy few days. For various reasons, I'd like to have a reliable Windows build locally, before I waste other people's time (unless you have time and energy to burn yourself). I have the

Re: [Flightgear-devel] June / LinuxTag release

2010-05-10 Thread Martin Spott
Peter Morgan wrote: > So we need a working version on the tuesday before .. > > The following tuesday, U will be taking that to Linux tag.. on a chip ? "Traditionally" (since 2007) the setup for LinuxTag has been prepared and test-run by Matthias Boerner, Mathias Froehlich - and myself. LinuxTag

Re: [Flightgear-devel] June / LinuxTag release

2010-05-10 Thread Christian Menge
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

Re: [Flightgear-devel] June / LinuxTag release

2010-05-08 Thread Christian Menge
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-36

Re: [Flightgear-devel] June / LinuxTag release

2010-05-07 Thread Alex Perry
The Android stuff doesn't need patches in the FGFS source code, but does affect the aircraft files (obviously) as well as SimGear and OSG. Please check with me before building in case the associated patches haven't been integrated into upstream yet. On Fri, May 7, 2010 at 9:06 AM, James Turner w

Re: [Flightgear-devel] June / LinuxTag release

2010-05-07 Thread Peter Morgan
http://calendar.freeflightsim.org/ So we need a working version on the tuesday before .. The following tuesday, U will be taking that to Linux tag.. on a chip ? pete -- ___ Fl

Re: [Flightgear-devel] June / LinuxTag release

2010-05-07 Thread Peter Morgan
Shall I put this in the calendar.. so we can all get in sequence together ? pete On Fri, May 7, 2010 at 5:06 PM, James Turner 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 hav

[Flightgear-devel] June / LinuxTag release

2010-05-07 Thread James Turner
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