dilbert wrote in Fri Oct 29, 2021 11:19 am:The crux of my question is: once the script determines which aircraft were not already accepted, who is the final arbiter responsible for adding aircraft with new development to the official repository?
If there were such a script that checks compatibility (which would on its on be a ton of work), it would probably be down to the dev of that script.
Also note, that such a script is hard to write.
You need to find a way to determen compatibility.
For nasal, you could look at the function calls but that can give falls negatives... for example the A320 has added the anisotropic filtering to canvases which is only available in next.
But it's written in a way so that it will only call it, if FG is new enough.
So you'd need to do a full code analysis to treat this right.
Just one, rather simple example of why this will be tricky.
In the end, it doesn't worth the time to write such a script and rather spend time developing something productive.
After all, users still have the choice to either run stable LTS releases or go for the nightlies (with all the pros and cons)