Re: [Flightgear-devel] the master branch
Hi Tim, When those are merged in, and I expect that to happen before December 1st, I suggest we roll those up as a real beta and start working towards a New Year's Eve release. I won't plan on merging anything else to the master branches before the release except for bug fixes. A new year's eve release sounds good to me. I'm planning to take up some time off between December 21 and Jan 1st, so I have plenty of opportunity to work on FlightGear. So, a new year's eve release should be possible (from my end of things), but unfortunately, I won't have any time at all until that time. Perhaps our New Year's resolution can be to make more frequent releases :) Agreed. Cheers, Durk -- Join us December 9, 2009 for the Red Hat Virtual Experience, a free event focused on virtualization and cloud computing. Attend in-depth sessions from your desk. Your couch. Anywhere. http://p.sf.net/sfu/redhat-sfdev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] the master branch
Tim Moore wrote: On 11/27/2009 10:08 AM, Erik Hofman wrote: You could argue that the new sound code has little benefit over the previous code (it does have the slight advantage of source management) to make it necessary to include it in the next release already. It's up to you. It seems like it touches a lot of parts of the code, and so would make future development hard to move to a master branch if it doesn't get into master fairly soon. Ok good point, lets include it. There are a few issues I'll sort out as soon as possible and have my fingers crossed it is tested on as many platforms as we can before the release. Erik -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] the master branch
On 27 Nov 2009, at 06:28, Tim Moore wrote: In my git repositories on gitorious, http://gitorious.org/fg, I've been keeping master branches that are supposed to be stable; the intent is for them to be a kind of rolling release candidate that could be turned into a release in short order. I've just pushed a bunch of commits to them that have been in master already for several weeks. At this point, the two lines of development that are not in master at all are Eric's sound system and the new effects code for models. Both of these seem to be stabilizing nicely, and I expect them to be in master in short order. Excellent. When those are merged in, and I expect that to happen before December 1st, I suggest we roll those up as a real beta and start working towards a New Year's Eve release. I won't plan on merging anything else to the master branches before the release except for bug fixes. Sounds fine to me. I'll be landing some more routing / RNAV / GPS changes 'really soon now', but I expect those to go to your next branch since they will certainly need time to bake. Some bug-fixes (on the master branch, and forwards ported) to the current route/GPS code is fairly likely - do you have any particular suggestion for managing those? Regards, James -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] the master branch
Tim Moore wrote: In my git repositories on gitorious, http://gitorious.org/fg, I've been keeping master branches that are supposed to be stable; the intent is for them to be a kind of rolling release candidate that could be turned into a release in short order. I've just pushed a bunch of commits to them that have been in master already for several weeks. At this point, the two lines of development that are not in master at all are Eric's sound system and the new effects code for models. You could argue that the new sound code has little benefit over the previous code (it does have the slight advantage of source management) to make it necessary to include it in the next release already. Erik -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] the master branch
On 11/27/2009 10:08 AM, Erik Hofman wrote: Tim Moore wrote: In my git repositories on gitorious, http://gitorious.org/fg, I've been keeping master branches that are supposed to be stable; the intent is for them to be a kind of rolling release candidate that could be turned into a release in short order. I've just pushed a bunch of commits to them that have been in master already for several weeks. At this point, the two lines of development that are not in master at all are Eric's sound system and the new effects code for models. You could argue that the new sound code has little benefit over the previous code (it does have the slight advantage of source management) to make it necessary to include it in the next release already. It's up to you. It seems like it touches a lot of parts of the code, and so would make future development hard to move to a master branch if it doesn't get into master fairly soon. Tim -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
[Flightgear-devel] the master branch
In my git repositories on gitorious, http://gitorious.org/fg, I've been keeping master branches that are supposed to be stable; the intent is for them to be a kind of rolling release candidate that could be turned into a release in short order. I've just pushed a bunch of commits to them that have been in master already for several weeks. At this point, the two lines of development that are not in master at all are Eric's sound system and the new effects code for models. Both of these seem to be stabilizing nicely, and I expect them to be in master in short order. When those are merged in, and I expect that to happen before December 1st, I suggest we roll those up as a real beta and start working towards a New Year's Eve release. I won't plan on merging anything else to the master branches before the release except for bug fixes. Perhaps our New Year's resolution can be to make more frequent releases :) Tim -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
