(playing virtual Durk, since he's in Antarctica for a month) I'm planning to create releases/2.2.0 branches of both Simgear and FlightGear tomorrow, based on current state of 'next' at that time. This is not intended to provoke a commit rush - if the code isn't in Gitorious now, it should probably wait until the next release (which should be sooner than 12 months time - ideally in time for LinuxTag)
If you make *bug-fixes* after the branches are created, please apply them to next, and then cherry-pick (or equivalent) them into the release heads. I'll create -rc1 tags as soon as the branches are cut, to provide a reference point - I believe Dave Luff and Tim Moore have some bug-fixes pending, but there's plenty of value in wider testing of the current state of the code. I should point out that the current nightly build infrastructure *does not* help with producing release candidates or final builds. I am doing some hacking in that direction, but for the moment, Hudson builds next, and *only* next - as soon as we branch, the Hudson visibility is gone. Hence, we're completely reliant on manual intervention to produce source and binary packages once the tags are created. (As we have been for every previous release, of course) If anyone has issues or objections to this, I assume you'll speak up :) Regards, James ------------------------------------------------------------------------------ Gaining the trust of online customers is vital for the success of any company that requires sensitive data to be transmitted over the Web. Learn how to best implement a security strategy that keeps consumers' information secure and instills the confidence they need to proceed with transactions. http://p.sf.net/sfu/oracle-sfdevnl _______________________________________________ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
