James and Francesco,
Proposal:
The version of the script on the official fgmeta next, master and
the upcoming release branch and should be maintained and should work.
The same script version can be on each of these branches. Currently
master does not work. next thinks stable is 2.8.0.
Note that this message is not a request to merge, just a proposal for
how to operate going forward.
Right now in the official fgmeta, we have:
fgmeta script script the script
branch version status builds:
------ ------- -------------- --------------
next: 1.9.10 (working) next and 2.8.0
master 1.9.4 (not working)
2.12.0 1.9.10 (working) next and 2.8.0
2.10.0 1.9.4 (not working)
in the fgmeta team clone we have:
next: 1.9.tbd working but next, master, 2.12.0,
not fully 2.10.0 2.8.0
tested OSG: 3.0.1 and any other
named branch of OSG
master 1.9.11 not released next and 2.8.0
untested
minor changes
Suggestion: backport the changes in 1.9.tbd that allows builds of
next,master, 2.12.0, 2.10.0 etc to script version 1.9.11, test it and
release it on Francesco's approval.
or we could just fix 1.9.10
Thoughts?
-Pat
PS. You may be asking how big a change would it be to allow the script
to build basically any branch, tag or commit#
Not too bad:
------------------------------------------------------------------------------
See everything from the browser to the database with AppDynamics
Get end-to-end visibility with application monitoring from AppDynamics
Isolate bottlenecks and diagnose root cause in seconds.
Start your free trial of AppDynamics Pro today!
http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk
_______________________________________________
Flightgear-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/flightgear-devel
