Postby IAHM-COL » Wed Nov 25, 2015 4:54 pm
Hi ALL
1. @Redpath. Hey lego. They know about that. They know that no content exists in FGDATA that is not transferred to FGMEMBERS in one week's time
2. The situation with FG 3.4 is called a "Software Development Cycle". It is a normal thing in software. It has much to do with the known fact that one cannot change the past. So when you develop a new feature, that feature exists in future releases, but it does not "backdrop" to older ones. For stability purposes, previous releases are never "re-updated". For that you have "future releases" instead.
Then you have what's called the "rolling distribution" or "next" or "bleeding edge". This is where new features are coded. Thus it is where the freshest new coolest stuff exist. It comes with a price: the rolling distributions also has the most likelihood of having new introduced bugs (usually while the new hot feature gets clean up -- thus the "bleading edge" name).
So in a development cycle several releases exist, to be known
* Previous Stable releases (FG 2.12, FG 3.0, FG 3.2)
* Current Stable release (FG 3.4)
* Current bleeding edge (FG 3.7)
While aircrafts also have the same. So versions for aircrafts also exist such as they work in a given past stable release, and newly updated aircraft which may require newest features, and thus be only workeable on the "bleeding edge". That is the case of c172p and 767-300
There is nothing about "blackmailing" there.
There is something "unbelievable" thou. And it is the fact that FG 3.6 is overdue to release from the promised date almost 3 months ago. And the fact that the "officials" of our software organization felt the need to stop the release because unknown problems to us -- the same time they get upvoted as a Sourceforge Software of the Month.
In serious business world, you are not a "project of the month" if you are overdue in your releases, and late in your cycle.
