Re: [Flightgear-devel] Release-branches READY
The release branches are ready and the next/master branches are open again for cool, great and fancy new features. James: Please introduce the new release branches to Jenkins ThorstenB: Please do so for the OBS Curt: Please create a release candidate from the release/2.6.0 build once James has set this up. Tat: Please create a Mac release candidate from the release/2.6.0 branches. All: Please have a close look on the bug tracker is help sorting out the issues mentioned there. What's next? - New development goes into next (fg/sg) and master (fgdata). - Bug fixes go into next (fg/sg) and master (fgdata). If they also fix a bug for the 2.6.0 release, please cherry-pick them into release/2.6.0 - Bug fixes that do not match the current development because next|master have moved on go directly into release/2.6.0 Torsten Am 17.01.2012 07:43, schrieb Torsten Dreyer: Subject says all... Am 16.01.2012 20:41, schrieb Torsten Dreyer: S - the outer marker is hooting, final checklist ist completed, the gear is down and shows three green - let's go for it! Tomorrow morning, on Jan. 17th between 06:00 and 09:00 UTC, I'll bump the version number to 2.6.0, tag and branch gitorious and if everything turns out as expected, bump the next/master branch to 2.7.0 for the next release cycle. Please, NO COMMIT AND NO PUSH during that period to ANY repository in http://gitorious.org/fg I'll post a message here on the list when this task is completed. Thanks for you cooperation, Torsten Am 11.01.2012 22:18, schrieb Torsten Dreyer: Hi everybody, in less than one week we will pass the outer marker for our release of FlightGear 2.6.0: the creation of the release branches in our git repositories. A good time to read the final checklist: * All features work as desired? * All major bugs fixed? (http://code.google.com/p/flightgear-bugs/issues/list?q=-Type%3DFeatureRequest) * All aircraft in FGDATA checked in? * No console debug messages? The EOBT (estimated-off-branch-time?) for our branches is 0800UTC on January, 17th. I'll announce the precise time the evening before that day. Please note that during that short period of 1-2 hours, everybody with commit rights is requested to _NOT_ push anything to our repositories. Go flying, hug your kids, have a beer at the pub - whatever you like. Just stay away from gitorious.org/fg. Please fasten your seat belts, fold away the table in front of you and turn off all your electronic devices. Thanks for flying FlightGear! Torsten on behalf of the entire release crew. Am 17.11.2011 23:57, schrieb Torsten Dreyer: Hi everybody, after some very active weeks of development in the core and data, we are slowly but steadily heading into the next release. This will be version 2.6.0 to be released in February 2012. Please note that - the next feature-freeze state will be entered on December, 17th - one month from now. - the release branch is to be created on January, 17th - two month from now. - the release should be ready by February, 17th - three month from now. (More details here: http://wiki.flightgear.org/index.php/Release_Plan) Those of you who are working on new features or major changes, please make sure you code is in the repositories by Dec., 17th. Thanks for your cooperation and all the excellent and hard work! Torsten -- All the data continuously generated in your IT infrastructure contains a definitive record of customers, 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-novd2d ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel -- Ridiculously easy VDI. With Citrix VDI-in-a-Box, you don't need a complex infrastructure or vast IT resources to deliver seamless, secure access to virtual desktops. With this all-in-one solution, easily deploy virtual desktops for less than the cost of PCs and save 60% on VDI infrastructure costs. Try it free! http://p.sf.net/sfu/Citrix-VDIinabox ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel -- RSA(R) Conference 2012 Mar 27 - Feb 2 Save $400 by Jan. 27 Register now! http://p.sf.net/sfu/rsa-sfdev2dev2 ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Release-branches READY
On Tue, 17 Jan 2012, Torsten Dreyer wrote: The release branches are ready and the next/master branches are open again for cool, great and fancy new features. James: Please introduce the new release branches to Jenkins ThorstenB: Please do so for the OBS Curt: Please create a release candidate from the release/2.6.0 build once James has set this up. Tat: Please create a Mac release candidate from the release/2.6.0 branches. All: Please have a close look on the bug tracker is help sorting out the issues mentioned there. What's next? - New development goes into next (fg/sg) and master (fgdata). - Bug fixes go into next (fg/sg) and master (fgdata). If they also fix a bug for the 2.6.0 release, please cherry-pick them into release/2.6.0 - Bug fixes that do not match the current development because next|master have moved on go directly into release/2.6.0 Torsten Many thanks to you all for your hard work! g. -- Proud owner of F-15C 80-0007 http://www.f15sim.com - The only one of its kind. http://www.diy-cockpits.org/coll - Go Collimated or Go Home. Some people collect things for a hobby. Geeks collect hobbies. ScarletDME - The red hot Data Management Environment A Multi-Value database for the masses, not the classes. http://www.scarletdme.org - Get it _today_! Political correctness is a doctrine, fostered by a delusional, illogical minority, and rabidly promoted by an unscrupulous mainstream media, which holds forth the proposition that it is entirely possible to pick up a turd by the clean end. -- Keep Your Developer Skills Current with LearnDevNow! The most comprehensive online learning library for Microsoft developers is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3, Metro Style Apps, more. Free future releases when you subscribe now! http://p.sf.net/sfu/learndevnow-d2d ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Release-branches READY
Hi Torsten, Can you post a quick git reminder for how to checkout the release/2.6.0 branch. I'm sure I'm not the only one who forgets something he hasn't thought about in 6 months. :-) Thanks, Curt. On Tue, Jan 17, 2012 at 2:01 AM, Torsten Dreyer tors...@t3r.de wrote: The release branches are ready and the next/master branches are open again for cool, great and fancy new features. James: Please introduce the new release branches to Jenkins ThorstenB: Please do so for the OBS Curt: Please create a release candidate from the release/2.6.0 build once James has set this up. Tat: Please create a Mac release candidate from the release/2.6.0 branches. All: Please have a close look on the bug tracker is help sorting out the issues mentioned there. What's next? - New development goes into next (fg/sg) and master (fgdata). - Bug fixes go into next (fg/sg) and master (fgdata). If they also fix a bug for the 2.6.0 release, please cherry-pick them into release/2.6.0 - Bug fixes that do not match the current development because next|master have moved on go directly into release/2.6.0 Torsten Am 17.01.2012 07:43, schrieb Torsten Dreyer: Subject says all... Am 16.01.2012 20:41, schrieb Torsten Dreyer: S - the outer marker is hooting, final checklist ist completed, the gear is down and shows three green - let's go for it! Tomorrow morning, on Jan. 17th between 06:00 and 09:00 UTC, I'll bump the version number to 2.6.0, tag and branch gitorious and if everything turns out as expected, bump the next/master branch to 2.7.0 for the next release cycle. Please, NO COMMIT AND NO PUSH during that period to ANY repository in http://gitorious.org/fg I'll post a message here on the list when this task is completed. Thanks for you cooperation, Torsten Am 11.01.2012 22:18, schrieb Torsten Dreyer: Hi everybody, in less than one week we will pass the outer marker for our release of FlightGear 2.6.0: the creation of the release branches in our git repositories. A good time to read the final checklist: * All features work as desired? * All major bugs fixed? ( http://code.google.com/p/flightgear-bugs/issues/list?q=-Type%3DFeatureRequest ) * All aircraft in FGDATA checked in? * No console debug messages? The EOBT (estimated-off-branch-time?) for our branches is 0800UTC on January, 17th. I'll announce the precise time the evening before that day. Please note that during that short period of 1-2 hours, everybody with commit rights is requested to _NOT_ push anything to our repositories. Go flying, hug your kids, have a beer at the pub - whatever you like. Just stay away from gitorious.org/fg. Please fasten your seat belts, fold away the table in front of you and turn off all your electronic devices. Thanks for flying FlightGear! Torsten on behalf of the entire release crew. Am 17.11.2011 23:57, schrieb Torsten Dreyer: Hi everybody, after some very active weeks of development in the core and data, we are slowly but steadily heading into the next release. This will be version 2.6.0 to be released in February 2012. Please note that - the next feature-freeze state will be entered on December, 17th - one month from now. - the release branch is to be created on January, 17th - two month from now. - the release should be ready by February, 17th - three month from now. (More details here: http://wiki.flightgear.org/index.php/Release_Plan ) Those of you who are working on new features or major changes, please make sure you code is in the repositories by Dec., 17th. Thanks for your cooperation and all the excellent and hard work! Torsten -- All the data continuously generated in your IT infrastructure contains a definitive record of customers, 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-novd2d ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel -- Ridiculously easy VDI. With Citrix VDI-in-a-Box, you don't need a complex infrastructure or vast IT resources to deliver seamless, secure access to virtual desktops. With this all-in-one solution, easily deploy virtual desktops for less than the cost of PCs and save 60% on VDI infrastructure costs. Try it free! http://p.sf.net/sfu/Citrix-VDIinabox ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Release-branches READY
On Tue, 17 Jan 2012, Curtis Olson wrote: Hi Torsten, Can you post a quick git reminder for how to checkout the release/2.6.0 branch. I'm sure I'm not the only one who forgets something he hasn't thought about in 6 months. :-) You can do this: git fetch git branch -t -l release-2.6.0 origin/release/2.6.0 git checkout release-2.6.0 Cheers, Anders -- --- Anders Gidenstam WWW: http://gitorious.org/anders-hangar http://www.gidenstam.org/FlightGear/ -- Keep Your Developer Skills Current with LearnDevNow! The most comprehensive online learning library for Microsoft developers is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3, Metro Style Apps, more. Free future releases when you subscribe now! http://p.sf.net/sfu/learndevnow-d2d ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Release-branches READY
On Tue, 17 Jan 2012, Anders Gidenstam wrote: You can do this: git fetch git branch -t -l release-2.6.0 origin/release/2.6.0 git checkout release-2.6.0 However, if you have a update to push that would then need to be git push origin release-2.6.0:release/2.6.0 to go to the right remote branch. A slightly better alternativ would be to keep the local and remote branch name the same: git branch -t -l release/2.6.0 origin/release/2.6.0 git checkout release/2.6.0 Cheers, Anders -- --- Anders Gidenstam WWW: http://gitorious.org/anders-hangar http://www.gidenstam.org/FlightGear/ -- Keep Your Developer Skills Current with LearnDevNow! The most comprehensive online learning library for Microsoft developers is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3, Metro Style Apps, more. Free future releases when you subscribe now! http://p.sf.net/sfu/learndevnow-d2d ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Release-branches READY
Anders Gidenstam wrote: git branch -t -l release-2.6.0 origin/release/2.6.0 where -t refers to origin/release/2.6.0, therefore: release-2.6.0 -t origin/release/2.6.0 might be easier to memorize. Cheers, Martin. -- Unix _IS_ user friendly - it's just selective about who its friends are ! -- -- Keep Your Developer Skills Current with LearnDevNow! The most comprehensive online learning library for Microsoft developers is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3, Metro Style Apps, more. Free future releases when you subscribe now! http://p.sf.net/sfu/learndevnow-d2d ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Release-branches READY
On Tue, Jan 17, 2012 at 2:01 AM, Torsten Dreyer tors...@t3r.de wrote: The release branches are ready and the next/master branches are open again for cool, great and fancy new features. James: Please introduce the new release branches to Jenkins Hi James, Would you mind posting when the release branch builds are setup and ready on on Jenkins? Could I request that you maintain a similar file system structure to what is setup now for the next branch builds? Or if the directory structure must be different for some reason, please give me a heads up on what to expect so I can adjust my packaging script accordingly. I never want to stand in the way of progress, but sometimes progress stands in my way. :-) I will plan to push out the first release candidate when the Jenkins builds roll through. Thanks, Curt -- Curtis Olson: http://www.atiak.com - http://aem.umn.edu/~uav/ http://www.flightgear.org - http://gallinazo.flightgear.org -- Keep Your Developer Skills Current with LearnDevNow! The most comprehensive online learning library for Microsoft developers is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3, Metro Style Apps, more. Free future releases when you subscribe now! http://p.sf.net/sfu/learndevnow-d2d___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
