Hi all, our first phase of the release progress will end this Sunday with the creation of the release branch.
Because pilots are unable to perform tasks with more than one step without having a checklist, I have created one for the branching process at http://wiki.flightgear.org/index.php/Release_Plan#Detailed_Time_Schedule_and_Checklist This checklist contains the steps, I'll perform on Sunday. I'd feel much more relaxed, if our QA team (You!) could read section 2. "Create new release branch, ..." and verify it's not complete nonsense and confirm it's the way we want to go. To make sure, our streams are in a consistent state when I create and tag the branches, please make sure not to push _any_ commits to simgear, flightgear and fgdata after Sunday, July 17th 2011 08:00 UTC until further advice ( hi Gene :-) ). I will post a message to this board when the branching is complete. This should happen not later than 12:00 UTC. Thanks for your help, Torsten ------------------------------------------------------------------------------ All of the data generated in your IT infrastructure is seriously valuable. Why? It contains a definitive record of application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-d2d-c2 _______________________________________________ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
