Re: [Flightgear-devel] Google Bug Tracker and Aircrafts

2010-02-27 Thread syd adams
Yeah this was discussed earlier because that list rapidly filled up with old
bugs .
I agree , missing features , or incomplete feature , or not knowing  how an
instrument works shouldn't be filed as a bug :)


On Sat, Feb 27, 2010 at 12:54 PM, Heiko Schulz aeitsch...@yahoo.de wrote:

 Hi,

 The Google Bug tracker is a nice instrument for the harcore developers
 here.
 But I have some problems with bug tracking there on aircrafts.

 All our aircrafts are in developement. It is difficult to say an aircraft
 is completly 100% ready. A lot of bugs often aren't more than just missing
 features.

 As an example: someone wrote that the Cessna Citation Bravo's ADF needle
 isn't working. In the description it sounds a bit different, as it just
 doesn't shows any NDB's. Does it ever have? To my knowledge not, so it is a
 missing feature, not a bug.

 Another example: someone noticed that the 737-300 shows two different
 cockpit- a 2d one and a 3d one.  As it was exactly my intention, to keep the
 2d-panel as long the flightdeck is not usuable as like the 2d-panel, and so
 I noted that in the ReadMe-file.
 Quote:This is the 737-300 in Progress...
 The Boeing 737-300 is now under work to be improved and come much closer to
 realityFor seeing the 3d-cockpit in progress pan the view so the
 2d-panel will dissapear

 I wonder if a bug-tracker makes really sense here- we have more than 130
 (?) aircrafts and I know a lot of them which do not have any proper cockpit;
 fdm; autopilot; systems etc... all bugs? Or just in development?

 I think aircrafts should be excluded as long they aren't part of the base
 package.

 Anyone agree or disgagree?
 Heiko




 still in work: http://www.hoerbird.net/galerie.html
 But already done: http://www.hoerbird.net/reisen.html

 __
 Do You Yahoo!?
 Sie sind Spam leid? Yahoo! Mail verfügt über einen herausragenden Schutz
 gegen Massenmails.
 http://mail.yahoo.com


 --
 Download Intel#174; Parallel Studio Eval
 Try the new software tools for yourself. Speed compiling, find bugs
 proactively, and fine-tune applications for parallel performance.
 See why Intel Parallel Studio got high marks during beta.
 http://p.sf.net/sfu/intel-sw-dev
 ___
 Flightgear-devel mailing list
 Flightgear-devel@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/flightgear-devel

--
Download Intel#174; Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel


Re: [Flightgear-devel] Google Bug Tracker and Aircrafts

2010-02-27 Thread Gijs de Rooy

 Heiko Schulz wrote:

 I wonder if a bug-tracker makes really sense here- we have more than 130 (?) 
 aircrafts

130?! There's 300 of them in CVS, so about 350 with the additional hangars! :)

Agree with you on all points btw. It might be nice to have an additional bug 
tracker for 
aircraft though. Similar to an additional requests tracker, that someone posted 
on the list
some days ago...

Cheers,

Gijs
  
_
25GB gratis online harde schijf
http://skydrive.live.com--
Download Intel#174; Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel


Re: [Flightgear-devel] Google Bug Tracker and Aircrafts

2010-02-27 Thread Tim Moore
I don't want to see any feature requests for the code either :)

Tim

On Sat, Feb 27, 2010 at 9:54 PM, Heiko Schulz aeitsch...@yahoo.de wrote:

 Hi,

 The Google Bug tracker is a nice instrument for the harcore developers
 here.
 But I have some problems with bug tracking there on aircrafts.

 All our aircrafts are in developement. It is difficult to say an aircraft
 is completly 100% ready. A lot of bugs often aren't more than just missing
 features.

 As an example: someone wrote that the Cessna Citation Bravo's ADF needle
 isn't working. In the description it sounds a bit different, as it just
 doesn't shows any NDB's. Does it ever have? To my knowledge not, so it is a
 missing feature, not a bug.

 Another example: someone noticed that the 737-300 shows two different
 cockpit- a 2d one and a 3d one.  As it was exactly my intention, to keep the
 2d-panel as long the flightdeck is not usuable as like the 2d-panel, and so
 I noted that in the ReadMe-file.
 Quote:This is the 737-300 in Progress...
 The Boeing 737-300 is now under work to be improved and come much closer to
 realityFor seeing the 3d-cockpit in progress pan the view so the
 2d-panel will dissapear

 I wonder if a bug-tracker makes really sense here- we have more than 130
 (?) aircrafts and I know a lot of them which do not have any proper cockpit;
 fdm; autopilot; systems etc... all bugs? Or just in development?

 I think aircrafts should be excluded as long they aren't part of the base
 package.

 Anyone agree or disgagree?
 Heiko




 still in work: http://www.hoerbird.net/galerie.html
 But already done: http://www.hoerbird.net/reisen.html

 __
 Do You Yahoo!?
 Sie sind Spam leid? Yahoo! Mail verfügt über einen herausragenden Schutz
 gegen Massenmails.
 http://mail.yahoo.com


 --
 Download Intel#174; Parallel Studio Eval
 Try the new software tools for yourself. Speed compiling, find bugs
 proactively, and fine-tune applications for parallel performance.
 See why Intel Parallel Studio got high marks during beta.
 http://p.sf.net/sfu/intel-sw-dev
 ___
 Flightgear-devel mailing list
 Flightgear-devel@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/flightgear-devel

--
Download Intel#174; Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel