Right, I'm a web developer and been thinking a lot about the bug tracking (in my case across projects/ventures/etc), and applying that to FG. Thats my frustration ladies and gentlemen, and I apologize for my harshness sometimes; this comes from frustration ;-)
Indeed as a day job, its working sometimes with users who think they made a mistake, and indeed a bug.. ie proven twice, so ball back in my court - we'll trained users. oops...ish and fixed, with svn up + python onto a wind. So I checked out a few bug tracking systems for curiosity for the purposes of FG,. I can report with confidence that none of them would meet the criteria that would be useful within the scope of FlightGear, as its bigger. Unless be break down the bugs into seperate components. But then that is not the whole.. * (the list is long of candidates rejected and not repeated here, but included bugzilla and flyspray as top2, indeed RT perl was almost at the top) * Google code issues.. was top.. really, but cannot go across projects.. * however as what would be the needs of flightgear. Then maybe none of them meet the criteria. Even as a FG newbie pilot. This is why I think we need to write our own bug track system. I'm up for that and full onto it. So I can report a bug in my area of interest. We just need to decide what the top ten bugs "areas" are, write them on paper, then constantly nibble away at the paper. a few wheels later.. maybe ;-) Pete ------------------------------------------------------------------------------ Come build with us! The BlackBerry(R) 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/devconference _______________________________________________ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
