>>> Do we have a volunteer (Thorsten?) to tag the branches as 2.8.0 to mark the >>> official close of changes for 2.8.0(.0)? >>> >> You might want to wait until you cut the release before laying down the >> tag... > for 2.4.0 and 2.6.0, we set the tag version/2.x.0-final. I'll set the > tag version/2.8.0-final on Thursday morning.
Done. This marks our final state of the code for the 2.8.0 release. Please start building our distributables from this tag on the release/2.8.0 branch. Anything pushed to fg/sg/fgdata into the release/2.8.0 branch from how on will eventually go into a 2.8.0.x bugfix release. Thanks, Torsten ------------------------------------------------------------------------------ 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
