It's July 17th: http://wiki.flightgear.org/index.php/Release_plan
Continuing with FG2.8.0's landing procedures, we have turned on final,
moving the release candidate to a separate Git branch (release/2.8.0
for sg/fg/fgdata). FG2.9.0 is already lined up on next (and fgdata
master), so new developments are cleared for take off.
All bug fixes should be pushed to the next/master branches first. If
they are essential for 2.8.0, they should be cherry-picked into the
release branch. If you don't know how Git cherry-picking works, please
ask the cabin crew for help. The closer we get to the touch down point,
the more important is a stable approach. So, throttle back, and when
correction is necessary, apply minimal rudder and patches only.
Arrival at the release gate is expected to be on time on August 17th, so
we'll flare the release a few days early to wrap things up and build
final setups. Until then, keep seatbelts fastened... ;-)
cheers,
Thorsten
--
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel