Right, we don't get too bent out of shape if problems and bugs are
discovered in newly committed code, as long as the person responsible is
aggressively pursuing the issues and fixing them as quickly as possible.
(No one is perfect on the first try every time.)
But that said, we really like to keep the CVS head version functioning.
Breaking the current development tree for everyone is a bad thing and is a
quick way to have some other frustrated developer to yank the change if it
is causing too much trouble. If its just a few nasal errors scrolling by,
that is annoying for people with fast terminals (linux xterm) but can be a
killer for people with slow terminals (windows.)
Committing broken code for the purpose of getting feed back might be ok if
it's contained within a specific aircraft and out of the main loop. But if
this is in the system nasal area and everyone sees the effects of the broken
code, then that is bad ....
So just keep in mind that broken CVS annoys and frustrates and panics
people.
If done unintentionally and you are hot on the trail of a fix, then it's
usually no big deal. On the other hand, if you are committing known buggy
or non-functioning code (even if when it's to get feedback) that's probably
not going to win you a lot of points ... especially if there's obvious
breakage.
Regards,
Curt.
On Mon, May 4, 2009 at 2:54 PM, Alexis Bory - xiii wrote:
> Heiko Schulz wrote:
> >
> >
> > May I ask something here? Why there is something comitted, which
> > isn't tested yet?
>
> But commiting to the CVS is the faster way to get usefull feed back and
> gather differents opinions on a proposal.
>
> > A generic pushback sounds nice, but so much as I
> > understood, the feature is only for JSBSim and all the JSBsim
> > aircafts who wants to use this feature, needs an update. At least
> > there should be one aircraft example available for that together...
>
> Let's help Gijs to make it work for the 747-400 and then we will see
> what is needed or not so we use this feature the bestway.
>
> Again, now that it is commited, everyone can bring its ideas. That's
> exactly what you are doing Heiko :-) So thanks.
>
> BTW the nasal part triggers nasal errors, I'm looking at that.
>
> Alexis
>
>
>
>
>
>
> ------------------------------------------------------------------------------
> Register Now & Save for Velocity, the Web Performance & Operations
> Conference from O'Reilly Media. Velocity features a full day of
> expert-led, hands-on workshops and two days of sessions from industry
> leaders in dedicated Performance & Operations tracks. Use code vel09scf
> and Save an extra 15% before 5/3. http://p.sf.net/sfu/velocityconf
> _______________________________________________
> Flightgear-devel mailing list
> Flightgear-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/flightgear-devel
>
--
Curtis Olson: http://baron.flightgear.org/~curt/
------------------------------------------------------------------------------
Register Now & Save for Velocity, the Web Performance & Operations
Conference from O'Reilly Media. Velocity features a full day of
expert-led, hands-on workshops and two days of sessions from industry
leaders in dedicated Performance & Operations tracks. Use code vel09scf
and Save an extra 15% before 5/3. http://p.sf.net/sfu/velocityconf
_______________________________________________
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel
