From: Pete M. <AC...@da...> - 2009-09-30 16:12:24
|
Just the word bug and track are enough to scare pilots. So The concept is to set up a tracking system for bugs. So u must have at least one winge.. http://code.google.com/p/flightgear-bugs/ lets fix them ;-) pete |
From: Curtis O. <cur...@gm...> - 2009-09-30 16:25:40
|
I agree that a bug tracking system is a good thing. My thoughts & hopes are that once we finalized what we were doing with our eventual move away from CVS, We would move our code to a system that offers a number of developer features including an integrated bug tracker. Google does offer a nice system, but long term, it would be nice to just use the bug tracker associated with our project, rather than setup a completely new project and only use the bug tracker out of it. Curt. On Wed, Sep 30, 2009 at 11:12 AM, Pete Morgan <AC...@da...> wrote: > Just the word bug and track are enough to scare pilots. > > So The concept is to set up a tracking system for bugs. > > So u must have at least one winge.. > http://code.google.com/p/flightgear-bugs/ > > lets fix them ;-) > pete > > > ------------------------------------------------------------------------------ > Come build with us! The BlackBerry® Developer Conference in SF, CA > is the only developer event you need to attend this year. Jumpstart your > developing skills, take BlackBerry mobile applications to market and stay > ahead of the curve. Join us from November 9-12, 2009. Register now! > http://p.sf.net/sfu/devconf > _______________________________________________ > Flightgear-devel mailing list > Fli...@li... > https://lists.sourceforge.net/lists/listinfo/flightgear-devel > -- Curtis Olson: http://baron.flightgear.org/~curt/ |
From: George P. <geo...@gm...> - 2009-09-30 16:53:31
|
On Thu, Oct 1, 2009 at 2:25 AM, Curtis Olson <cur...@gm...> wrote: > I agree that a bug tracking system is a good thing. My thoughts & hopes are > that once we finalized what we were doing with our eventual move away from > CVS, We would move our code to a system that offers a number of developer > features including an integrated bug tracker. Google does offer a nice > system, but long term, it would be nice to just use the bug tracker > associated with our project, rather than setup a completely new project and > only use the bug tracker out of it. > > Curt. > > I totally agree that an issue tracking system is required. >From the short run that Pete Morgan and a couple of others have had a couple of things come to mind. - Proforma reports with at least the following information - Steps required to reproduce the bug - Operating System and version - Which version of FlightGear were you using? - The moderators need to be able to close tickets that are incomplete and the submitter is out of communication for an extended period of time. I'd say one fortnight, though that might be too long/short. - The idea where a user that submitted a bug report can also accept it as a bug is broken (unless the tickets are split into user issues and bugs. As an example a user reports an issue as "Flightgear stalls with lots of NaN messages being display on console at TBPB". The Bug could be "NaN messages are displayed on console due to bad input data". If you have other related issues, then you link the issue to the Bug ticket. This cuts down the redundant tickets that a developer needs to wade though. This is fast getting into ITIL land. I am familiar with Atlassian Jira for incident and problem management but it's an overkill for FlightGear base. What's the url for the ticketing system we have? Regards George |
From: Pete M. <AC...@da...> - 2009-09-30 17:08:15
|
Gorilla thanks. U kinda exlained what's needed.. My vision it to "filter" the results and then have a direction of things to fix from user reports... Users are our best friends.. who can complain to their hearts content.. The issue now is that we need to "register" and recongise all the failures, so they can be identified and fixed.. I love the idea of 2 weeks.. as that is a recognision of problem and solution... Only thing is that whats REALYY important is the /data/ and this even in git yet anywhere. ?? The bug reports ie cusomter satisfaction and FDS so not mix, they are two seperate mixtures... pete George Patterson wrote: > On Thu, Oct 1, 2009 at 2:25 AM, Curtis Olson <cur...@gm...> wrote: > >> I agree that a bug tracking system is a good thing. My thoughts & hopes are >> that once we finalized what we were doing with our eventual move away from >> CVS, We would move our code to a system that offers a number of developer >> features including an integrated bug tracker. Google does offer a nice >> system, but long term, it would be nice to just use the bug tracker >> associated with our project, rather than setup a completely new project and >> only use the bug tracker out of it. >> >> Curt. >> >> >> > > I totally agree that an issue tracking system is required. > > >From the short run that Pete Morgan and a couple of others have had a > couple of things come to mind. > > - Proforma reports with at least the following information > - Steps required to reproduce the bug > - Operating System and version > - Which version of FlightGear were you using? > > - The moderators need to be able to close tickets that are incomplete > and the submitter is out of communication for an extended period of > time. I'd say one fortnight, though that might be too long/short. > > - The idea where a user that submitted a bug report can also accept it > as a bug is broken (unless the tickets are split into user issues and > bugs. > > As an example a user reports an issue as "Flightgear stalls with lots > of NaN messages being display on console at TBPB". The Bug could be > "NaN messages are displayed on console due to bad input data". If you > have other related issues, then you link the issue to the Bug ticket. > This cuts down the redundant tickets that a developer needs to wade > though. > > > This is fast getting into ITIL land. I am familiar with Atlassian Jira > for incident and problem management but it's an overkill for > FlightGear base. > > What's the url for the ticketing system we have? > > Regards > > > George > > ------------------------------------------------------------------------------ > Come build with us! The BlackBerry® Developer Conference in SF, CA > is the only developer event you need to attend this year. Jumpstart your > developing skills, take BlackBerry mobile applications to market and stay > ahead of the curve. Join us from November 9-12, 2009. Register now! > http://p.sf.net/sfu/devconf > _______________________________________________ > Flightgear-devel mailing list > Fli...@li... > https://lists.sourceforge.net/lists/listinfo/flightgear-devel > |
From: Pete M. <AC...@da...> - 2009-09-30 16:58:38
|
Curtis Olson wrote: > I agree that a bug tracking system is a good thing. My thoughts & > hopes are that once we finalized what we were doing with our eventual > move away from CVS, We would move our code to a system that offers a > number of developer features including an integrated bug tracker. > Google does offer a nice system, but long term, it would be nice to > just use the bug tracker associated with our project, rather than > setup a completely new project and only use the bug tracker out of it. > > Curt. > for me as an intermediate user, If there is a facility to report bugs ie PIEPR's then that would be cool. So at the moment This site is for identifying bugs only.. No less or more. It will be seperate atmo from source.. However recognising the bugs is THE issue. eg one of the three paths 1) dont set up a bug tracker and ignoire them 2) Have a bug tracker and then ignore them 3) Have an active bug tracer and identify problem area and resolve issue.. 4) Send a report to the developers that there is a bug u need to fix.. Curtis .. please endorse and go for this bucktracker please.. At least that way we can all complain until we sort it.. ;-) this way it will be a steady eddie ;-) the SCM is another issue Pete |
From: Curtis O. <cur...@gm...> - 2009-09-30 17:07:59
|
On Wed, Sep 30, 2009 at 11:58 AM, Pete Morgan <AC...@da...> wrote: > Curtis Olson wrote: > > I agree that a bug tracking system is a good thing. My thoughts & > > hopes are that once we finalized what we were doing with our eventual > > move away from CVS, We would move our code to a system that offers a > > number of developer features including an integrated bug tracker. > > Google does offer a nice system, but long term, it would be nice to > > just use the bug tracker associated with our project, rather than > > setup a completely new project and only use the bug tracker out of it. > > > > Curt. > > > for me as an intermediate user, If there is a facility to report bugs ie > PIEPR's then that would be cool. > > So at the moment This site is for identifying bugs only.. No less or > more. It will be seperate atmo from source.. > > However recognising the bugs is THE issue. > > eg one of the three paths > 1) dont set up a bug tracker and ignoire them > 2) Have a bug tracker and then ignore them > 3) Have an active bug tracer and identify problem area and resolve issue.. > > 4) Send a report to the developers that there is a bug u need to fix.. > > Curtis .. please endorse and go for this bucktracker please.. At least > that way we can all complain until we sort it.. ;-) > > this way it will be a steady eddie ;-) > the SCM is another issue > > I'd be more inclined to use the bug trackers at http://code.google.com/p/simgear and http://code.google.com/p/flightgear but those sites are currently tied up with svn versus git versus hg discussions. Personally I think it could turn into a mess if we fill up this new site with a bunch of bug reports and then have no way to move them to the official site(s) later. We also have bug trackers available at our sourceforge registered projects. I always felt the sourceforge bug tracker was kind of slow and clunky. The google bug tracker seems much nicer, and it appears it is integrated with the repository so you can reference specific patches or branches. That would be harder to do if the bug tracker lived at a completely separate project name. We lose much of the cool functionality that google offers. Regards, Curt. -- Curtis Olson: http://baron.flightgear.org/~curt/ |
From: Pete M. <AC...@da...> - 2009-09-30 17:18:38
|
Precisley the problem is that me as amuppet doth not know where the issue ie at, and where to report. So at least if we can point users to a particular point, then they can be filtered and sorted. therby dipatched to the concerned. At the moment its real crap.. so at least I want to use google issues as a common complaints dept, for delegation pete Curtis Olson wrote: > > > On Wed, Sep 30, 2009 at 11:58 AM, Pete Morgan <AC...@da... > <mailto:AC...@da...>> wrote: > > Curtis Olson wrote: > > I agree that a bug tracking system is a good thing. My thoughts & > > hopes are that once we finalized what we were doing with our > eventual > > move away from CVS, We would move our code to a system that > offers a > > number of developer features including an integrated bug tracker. > > Google does offer a nice system, but long term, it would be nice to > > just use the bug tracker associated with our project, rather than > > setup a completely new project and only use the bug tracker out > of it. > > > > Curt. > > > for me as an intermediate user, If there is a facility to report > bugs ie > PIEPR's then that would be cool. > > So at the moment This site is for identifying bugs only.. No less or > more. It will be seperate atmo from source.. > > However recognising the bugs is THE issue. > > eg one of the three paths > 1) dont set up a bug tracker and ignoire them > 2) Have a bug tracker and then ignore them > 3) Have an active bug tracer and identify problem area and resolve > issue.. > > 4) Send a report to the developers that there is a bug u need to fix.. > > Curtis .. please endorse and go for this bucktracker please.. At least > that way we can all complain until we sort it.. ;-) > > this way it will be a steady eddie ;-) > the SCM is another issue > > > I'd be more inclined to use the bug trackers at > http://code.google.com/p/simgear and > http://code.google.com/p/flightgear but those sites are currently tied > up with svn versus git versus hg discussions. > > Personally I think it could turn into a mess if we fill up this new > site with a bunch of bug reports and then have no way to move them to > the official site(s) later. We also have bug trackers available at > our sourceforge registered projects. I always felt the sourceforge > bug tracker was kind of slow and clunky. The google bug tracker seems > much nicer, and it appears it is integrated with the repository so you > can reference specific patches or branches. That would be harder to > do if the bug tracker lived at a completely separate project name. We > lose much of the cool functionality that google offers. > > Regards, > > Curt. > -- > Curtis Olson: http://baron.flightgear.org/~curt/ > <http://baron.flightgear.org/%7Ecurt/> > ------------------------------------------------------------------------ > > ------------------------------------------------------------------------------ > Come build with us! The BlackBerry® Developer Conference in SF, CA > is the only developer event you need to attend this year. Jumpstart your > developing skills, take BlackBerry mobile applications to market and stay > ahead of the curve. Join us from November 9-12, 2009. Register now! > http://p.sf.net/sfu/devconf > ------------------------------------------------------------------------ > > _______________________________________________ > Flightgear-devel mailing list > Fli...@li... > https://lists.sourceforge.net/lists/listinfo/flightgear-devel > |
From: Curtis O. <cur...@gm...> - 2009-09-30 17:37:32
|
I'm just not sure how productive it is to register yet another separate google project simply to use the bug tracker. Why not use the bug tracker at code.google.com/p/flightgear? I've been holding off pushing any particular bug tracking system, because it really makes a lot of sense to co-locate the bug tracking system with the code. Regards, Curt. On Wed, Sep 30, 2009 at 12:18 PM, Pete Morgan <AC...@da...> wrote: > > Precisley the problem is that me as amuppet doth not know where the > issue ie at, and where to report. > > So at least if we can point users to a particular point, then they can > be filtered and sorted. > > therby dipatched to the concerned. > > At the moment its real crap.. so at least I want to use google issues as > a common complaints dept, for delegation > > pete > > Curtis Olson wrote: > > > > > > On Wed, Sep 30, 2009 at 11:58 AM, Pete Morgan <AC...@da... > > <mailto:AC...@da...>> wrote: > > > > Curtis Olson wrote: > > > I agree that a bug tracking system is a good thing. My thoughts & > > > hopes are that once we finalized what we were doing with our > > eventual > > > move away from CVS, We would move our code to a system that > > offers a > > > number of developer features including an integrated bug tracker. > > > Google does offer a nice system, but long term, it would be nice to > > > just use the bug tracker associated with our project, rather than > > > setup a completely new project and only use the bug tracker out > > of it. > > > > > > Curt. > > > > > for me as an intermediate user, If there is a facility to report > > bugs ie > > PIEPR's then that would be cool. > > > > So at the moment This site is for identifying bugs only.. No less or > > more. It will be seperate atmo from source.. > > > > However recognising the bugs is THE issue. > > > > eg one of the three paths > > 1) dont set up a bug tracker and ignoire them > > 2) Have a bug tracker and then ignore them > > 3) Have an active bug tracer and identify problem area and resolve > > issue.. > > > > 4) Send a report to the developers that there is a bug u need to > fix.. > > > > Curtis .. please endorse and go for this bucktracker please.. At > least > > that way we can all complain until we sort it.. ;-) > > > > this way it will be a steady eddie ;-) > > the SCM is another issue > > > > > > I'd be more inclined to use the bug trackers at > > http://code.google.com/p/simgear and > > http://code.google.com/p/flightgear but those sites are currently tied > > up with svn versus git versus hg discussions. > > > > Personally I think it could turn into a mess if we fill up this new > > site with a bunch of bug reports and then have no way to move them to > > the official site(s) later. We also have bug trackers available at > > our sourceforge registered projects. I always felt the sourceforge > > bug tracker was kind of slow and clunky. The google bug tracker seems > > much nicer, and it appears it is integrated with the repository so you > > can reference specific patches or branches. That would be harder to > > do if the bug tracker lived at a completely separate project name. We > > lose much of the cool functionality that google offers. > > > > Regards, > > > > Curt. > > -- > > Curtis Olson: http://baron.flightgear.org/~curt/<http://baron.flightgear.org/%7Ecurt/> > > <http://baron.flightgear.org/%7Ecurt/> > > ------------------------------------------------------------------------ > > > > > ------------------------------------------------------------------------------ > > Come build with us! The BlackBerry® Developer Conference in SF, CA > > is the only developer event you need to attend this year. Jumpstart your > > developing skills, take BlackBerry mobile applications to market and stay > > ahead of the curve. Join us from November 9-12, 2009. Register > now! > > http://p.sf.net/sfu/devconf > > ------------------------------------------------------------------------ > > > > _______________________________________________ > > Flightgear-devel mailing list > > Fli...@li... > > https://lists.sourceforge.net/lists/listinfo/flightgear-devel > > > > > > ------------------------------------------------------------------------------ > Come build with us! The BlackBerry® Developer Conference in SF, CA > is the only developer event you need to attend this year. Jumpstart your > developing skills, take BlackBerry mobile applications to market and stay > ahead of the curve. Join us from November 9-12, 2009. Register now! > http://p.sf.net/sfu/devconf > _______________________________________________ > Flightgear-devel mailing list > Fli...@li... > https://lists.sourceforge.net/lists/listinfo/flightgear-devel > -- Curtis Olson: http://baron.flightgear.org/~curt/ |
From: Gijs de R. <gij...@ho...> - 2009-09-30 17:47:43
|
Hi, > Curtis Olson wrote: > > Why not use the bug tracker at code.google.com/p/flightgear? Is it just me or does that project not exist? The link gives an error page and the project does not show up when searching for FlightGear on Google Code. The simgear one does exist... Cheers, Gijs _________________________________________________________________ Krijg updates van je vrienden en blijf op de hoogte http://home.live.com |
From: Pete M. <AC...@da...> - 2009-09-30 17:51:54
|
same here ? Gijs de Rooy wrote: > Hi, > > > Curtis Olson wrote: > > > > Why not use the bug tracker at code.google.com/p/flightgear > <http://code.google.com/p/flightgear>? > > Is it just me or does that project not exist? The link gives an error > page and the project > does not show up when searching for FlightGear on Google Code. The > simgear one does > exist... > > Cheers, > Gijs > > ------------------------------------------------------------------------ > Plan je party en pimp je uitnodigingen met Windows Live Events > <http://www.microsoft.com/netherlands/windowslive/Views/productDetail.aspx?product=Events> > > ------------------------------------------------------------------------ > > ------------------------------------------------------------------------------ > Come build with us! The BlackBerry® Developer Conference in SF, CA > is the only developer event you need to attend this year. Jumpstart your > developing skills, take BlackBerry mobile applications to market and stay > ahead of the curve. Join us from November 9-12, 2009. Register now! > http://p.sf.net/sfu/devconf > ------------------------------------------------------------------------ > > _______________________________________________ > Flightgear-devel mailing list > Fli...@li... > https://lists.sourceforge.net/lists/listinfo/flightgear-devel > |
From: Curtis O. <cur...@gm...> - 2009-09-30 17:59:26
|
On Wed, Sep 30, 2009 at 12:47 PM, Gijs de Rooy <gij...@ho...> wrote: > Hi, > > > Curtis Olson wrote: > > > > Why not use the bug tracker at code.google.com/p/flightgear? > > Is it just me or does that project not exist? The link gives an error page > and the project > does not show up when searching for FlightGear on Google Code. The simgear > one does > exist... > Ok, well the one that will eventually exist there ... :-) (except we cannot collectively agree on the best source code control system to move towards. Svn in better than cvs; cvs is better than svn, git implementations are dodgy under windows, git implementations under windows run fine, hg is a lean mean fighting machine, except google's implementation or servers currently has some sort of issues with the linux hg client or maybe visa versa; anything is better than cvs; don't transition to svn because once the cvs 'crisis' is averted then there's no further motiviation to go any further. the project has a lot of git experience, the project has a lot of svn experience, the project has a lot of cvs experienece, the project doesn't have much hg experience; every one can register a project name at their favorite hosting service, everyone can setup their own local repostory clone using their favorite tool; but some developers have argued this *very* passionately implying perhaps that there will be a huge firestorm following up any bad or incorrect decisions for how to move foward; we have set up a sequence of constraints that gives us no option to do anything.) Regards, Curt. -- Curtis Olson: http://baron.flightgear.org/~curt/ |
From: Pete M. <AC...@da...> - 2009-09-30 18:23:48
|
Curtis.. Thou needs to rise up and command the people. Please dictate where we can file bugs first.. |
From: Vivian M. <viv...@li...> - 2009-09-30 22:13:25
|
Curt wrote 'git implementations under windows run fine' Who claims that? Not here they don't. I get constant glitches with cloned repos hanging - not only do they hang, but I can find no way out of the situation. I'm really p*ssed off with git right now. I'm in the anything but git camp today! Vivian -----Original Message----- From: Curtis Olson [mailto:cur...@gm...] Sent: 30 September 2009 18:59 To: FlightGear developers discussions Subject: Re: [Flightgear-devel] bug tracking On Wed, Sep 30, 2009 at 12:47 PM, Gijs de Rooy <gij...@ho...> wrote: Hi, > Curtis Olson wrote: > > Why not use the bug tracker at code.google.com/p/flightgear? Is it just me or does that project not exist? The link gives an error page and the project does not show up when searching for FlightGear on Google Code. The simgear one does exist... Ok, well the one that will eventually exist there ... :-) (except we cannot collectively agree on the best source code control system to move towards. Svn in better than cvs; cvs is better than svn, git implementations are dodgy under windows, git implementations under windows run fine, hg is a lean mean fighting machine, except google's implementation or servers currently has some sort of issues with the linux hg client or maybe visa versa; anything is better than cvs; don't transition to svn because once the cvs 'crisis' is averted then there's no further motiviation to go any further. the project has a lot of git experience, the project has a lot of svn experience, the project has a lot of cvs experienece, the project doesn't have much hg experience; every one can register a project name at their favorite hosting service, everyone can setup their own local repostory clone using their favorite tool; but some developers have argued this *very* passionately implying perhaps that there will be a huge firestorm following up any bad or incorrect decisions for how to move foward; we have set up a sequence of constraints that gives us no option to do anything.) Regards, Curt. -- Curtis Olson: http://baron.flightgear.org/~curt/ |
From: Tim M. <ti...@re...> - 2009-09-30 22:45:03
|
On 10/01/2009 12:13 AM, Vivian Meazza wrote: > Curt wrote > > > > ‘git implementations under windows run fine’ Who claims that? Not here > they don’t. I get constant glitches with cloned repos hanging – not only > do they hang, but I can find no way out of the situation. I’m really > p*ssed off with git right now. I’m in the anything but git camp today! > Further investigation points to user error and maybe some tortoise git problems. However, the local git expert has to go to sleep now... Tim |
From: Pete M. <AC...@da...> - 2009-09-30 17:50:18
|
code.google.com/p/flightgea <http://code.google.com/p/flightgear>r = 404 ??? I am interested in the bug tracking bit Will make life easier for all -) Pete Krash handler FG.uk PLC Curtis Olson wrote: > I'm just not sure how productive it is to register yet another > separate google project simply to use the bug tracker. Why not use > the bug tracker at code.google.com/p/flightgear > <http://code.google.com/p/flightgear>? I've been holding off pushing > any particular bug tracking system, because it really makes a lot of > sense to co-locate the bug tracking system with the code. > > Regards, > > Curt. > > > On Wed, Sep 30, 2009 at 12:18 PM, Pete Morgan <AC...@da... > <mailto:AC...@da...>> wrote: > > > Precisley the problem is that me as amuppet doth not know where the > issue ie at, and where to report. > > So at least if we can point users to a particular point, then they can > be filtered and sorted. > > therby dipatched to the concerned. > > At the moment its real crap.. so at least I want to use google > issues as > a common complaints dept, for delegation > > pete > > Curtis Olson wrote: > > > > > > On Wed, Sep 30, 2009 at 11:58 AM, Pete Morgan > <AC...@da... <mailto:AC...@da...> > > <mailto:AC...@da... <mailto:AC...@da...>>> > wrote: > > > > Curtis Olson wrote: > > > I agree that a bug tracking system is a good thing. My > thoughts & > > > hopes are that once we finalized what we were doing with our > > eventual > > > move away from CVS, We would move our code to a system that > > offers a > > > number of developer features including an integrated bug > tracker. > > > Google does offer a nice system, but long term, it would > be nice to > > > just use the bug tracker associated with our project, > rather than > > > setup a completely new project and only use the bug > tracker out > > of it. > > > > > > Curt. > > > > > for me as an intermediate user, If there is a facility to report > > bugs ie > > PIEPR's then that would be cool. > > > > So at the moment This site is for identifying bugs only.. No > less or > > more. It will be seperate atmo from source.. > > > > However recognising the bugs is THE issue. > > > > eg one of the three paths > > 1) dont set up a bug tracker and ignoire them > > 2) Have a bug tracker and then ignore them > > 3) Have an active bug tracer and identify problem area and > resolve > > issue.. > > > > 4) Send a report to the developers that there is a bug u > need to fix.. > > > > Curtis .. please endorse and go for this bucktracker > please.. At least > > that way we can all complain until we sort it.. ;-) > > > > this way it will be a steady eddie ;-) > > the SCM is another issue > > > > > > I'd be more inclined to use the bug trackers at > > http://code.google.com/p/simgear and > > http://code.google.com/p/flightgear but those sites are > currently tied > > up with svn versus git versus hg discussions. > > > > Personally I think it could turn into a mess if we fill up this new > > site with a bunch of bug reports and then have no way to move > them to > > the official site(s) later. We also have bug trackers available at > > our sourceforge registered projects. I always felt the sourceforge > > bug tracker was kind of slow and clunky. The google bug tracker > seems > > much nicer, and it appears it is integrated with the repository > so you > > can reference specific patches or branches. That would be harder to > > do if the bug tracker lived at a completely separate project > name. We > > lose much of the cool functionality that google offers. > > > > Regards, > > > > Curt. > > -- > > Curtis Olson: http://baron.flightgear.org/~curt/ > <http://baron.flightgear.org/%7Ecurt/> > > <http://baron.flightgear.org/%7Ecurt/> > > > ------------------------------------------------------------------------ > > > > > ------------------------------------------------------------------------------ > > Come build with us! The BlackBerry® Developer Conference in > SF, CA > > is the only developer event you need to attend this year. > Jumpstart your > > developing skills, take BlackBerry mobile applications to market > and stay > > ahead of the curve. Join us from November 9-12, 2009. > Register now! > > http://p.sf.net/sfu/devconf > > > ------------------------------------------------------------------------ > > > > _______________________________________________ > > Flightgear-devel mailing list > > Fli...@li... > <mailto:Fli...@li...> > > https://lists.sourceforge.net/lists/listinfo/flightgear-devel > > > > > ------------------------------------------------------------------------------ > Come build with us! The BlackBerry® Developer Conference in SF, CA > is the only developer event you need to attend this year. > Jumpstart your > developing skills, take BlackBerry mobile applications to market > and stay > ahead of the curve. Join us from November 9-12, 2009. Register > now! > http://p.sf.net/sfu/devconf > _______________________________________________ > Flightgear-devel mailing list > Fli...@li... > <mailto:Fli...@li...> > https://lists.sourceforge.net/lists/listinfo/flightgear-devel > > > > > -- > Curtis Olson: http://baron.flightgear.org/~curt/ > <http://baron.flightgear.org/%7Ecurt/> > ------------------------------------------------------------------------ > > ------------------------------------------------------------------------------ > Come build with us! The BlackBerry® Developer Conference in SF, CA > is the only developer event you need to attend this year. Jumpstart your > developing skills, take BlackBerry mobile applications to market and stay > ahead of the curve. Join us from November 9-12, 2009. Register now! > http://p.sf.net/sfu/devconf > ------------------------------------------------------------------------ > > _______________________________________________ > Flightgear-devel mailing list > Fli...@li... > https://lists.sourceforge.net/lists/listinfo/flightgear-devel > |