Am Donnerstag, den 19.05.2011, 17:47 +0100 schrieb Vivian Meazza:
> I think the question we have to ask is not "when" but "how". Until that is
> solved, the "when" is pretty meaningless. 
And the last release got stalled more on a "who" than a "how" alone,
when several people became too busy/blocked with RL commitments. You may
not like that, but you can't blame anyone who has done a lot for FG and
who has already invested a lot of "free" time into the project, that
they suddenly need to shift their priorities or need a break for
personal reasons.

The "new plan" alone doesn't exclude the risk of this repeating - but
there more people actively participate in the release, the less likely
we're going to get stalled. So, it's up to all of us.

And all of you can help: you can help by testing FlightGear right now
and of course the upcoming release candidates and file bug reports. Of
course we need as much help as possible for fixing issues. Things in the
FG core will need to be fixed - but also issues concerning fgdata, such
as working on aircraft or GUI. Everyone can look at the bug tracker,
pick issues and submit patches. And even if you can't work on code or
aircraft, you can still help by trying to narrow done what exactly
causes a specific bug issue (such as testing which commit introduced a
particular problem or what command-line/environment/... setting exactly
triggers a certain problem). Or you can help with updating/improving
manuals. Lots to do - any help is welcome!

cheers,
Thorsten




------------------------------------------------------------------------------
What Every C/C++ and Fortran developer Should Know!
Read this article and learn how Intel has extended the reach of its 
next-generation tools to help Windows* and Linux* C/C++ and Fortran 
developers boost performance applications - including clusters. 
http://p.sf.net/sfu/intel-dev2devmay
_______________________________________________
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel

Reply via email to