Re: [Flightgear-devel] heads up: FlightGear release plan
we need to sit on this as 2.2.freeflightsim.org.. We need a marketing plam somwhat.. I hope we stick to release schedule.. We are currently well on track. We fixed many bugs from the tracker and now that June has arrived, there are just roughly two weeks until we freeze 'next' for the final dustremoval session and before we branch for the release on July, 17th. Torsten -- Simplify data backup and recovery for your virtual environment with vRanger. Installation's a snap, and flexible recovery options mean your data is safe, secure and there when you need it. Data protection magic? Nope - It's vRanger. Get your free trial download today. http://p.sf.net/sfu/quest-sfdev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] heads up: FlightGear release plan
Am 01.06.11 07:41, schrieb Torsten Dreyer: Can you please update http://wiki.flightgear.org/Release_Plan with this very important information ? Something like a short description of current state ? Thanks a lot, Yves Hi Yves, this particular wiki page was written (mostly by myself) to document our release plan. I tried to make it as complete as possible but if anything is missing, please feel free to add it to the wiki. Thanks, Torsten Hi Torsten I only missed the statements from your message here in the list, which is very important to see current progress. Because i.e. Text on gitorious does not reflect the new plan. Sorry, I was away for some weeks ... Maybe I will add a box or something on top of the wiki page to reflect current state in two or three lines. I really like this effort with the release plan and I apologize, I didn’t want to come back to the project and as a first action I change this new wiki page. I missed such an effort a long time, I hope this becomes a real roadmap now. Thanks a lot, Yves -- Simplify data backup and recovery for your virtual environment with vRanger. Installation's a snap, and flexible recovery options mean your data is safe, secure and there when you need it. Data protection magic? Nope - It's vRanger. Get your free trial download today. http://p.sf.net/sfu/quest-sfdev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] heads up: FlightGear release plan
Hi Torsten I only missed the statements from your message here in the list, which is very important to see current progress. Because i.e. Text on gitorious does not reflect the new plan. Sorry, I was away for some weeks ... Maybe I will add a box or something on top of the wiki page to reflect current state in two or three lines. I really like this effort with the release plan and I apologize, I didn’t want to come back to the project and as a first action I change this new wiki page. I missed such an effort a long time, I hope this becomes a real roadmap now. Thanks a lot, Yves Hi Yves and welcome back, the roadmap is there - now let's hope enough people are willing to follow us on that path. Currently the workload is distributed on the shoulders of just a few of us and every little help is very much appreciated. Torsten -- Simplify data backup and recovery for your virtual environment with vRanger. Installation's a snap, and flexible recovery options mean your data is safe, secure and there when you need it. Data protection magic? Nope - It's vRanger. Get your free trial download today. http://p.sf.net/sfu/quest-sfdev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] heads up: FlightGear release plan
Am 22.05.11 14:37, schrieb ThorstenB: Hi, since there were no major objections to the release plan, we're proceeding as proposed. Current status: * We've officially grounded the releases/2.2.0 git branches yesterday. The flightgear/simgear releases/2.2.0 branches were merged back to master (not next! master always contains the latest release). However, as proposed, we won't invest any more time into 2.2.0, so there'll be no binaries on the download page, no updated aircraft downloads, no announcements, etc. * git/next is bumped to version 2.3.0 now. Actually we should have done so when we branched releases/2.2.0 in January. Remember. it's odd minor versions for the developer version now (git/next), even minor numbers for releases. * Hudson is prepared for providing release binaries and installers (thanks James!). Once we create a new release branch, Hudson should start building the binaries/installers (see Hudson's Windows-release, Mac-release, Linux-release projects). As usual, these will be updated hourly. We'll also provide complete Win/Mac installers (including fgdata base package) regularly, maybe about weekly, so these can be used for wider beta testing. We can't include the base package in the _hourly_ installers though, due to bandwidth/size limits (almost 400MB for the fgdata base package). * We also started assessing tracker issues (thanks Gijs!). Some were already fixed in the last days. And it doesn't look too bad, few issues are highly critical. However, there are some areas where we're missing people, for example for some (new) FDM, and a number of ATI-graphics issues. Have a look at the tracker: http://code.google.com/p/flightgear-bugs/issues/list Finally, as a reminder now: Only 4 more weeks to 2.4.0 feature freeze, remember June 17th, when we'll close sg+fg next branch, and (!) fgdata master for 4 weeks. Only bug fixes should be committed after June 17th. releases/2.4.0 will be branched on July 17th, when the main developer branches will be bumped to 2.5.0 and reopen for new features. Beta testing for 2.4.0 will continue for another month after that, till August 17th. But all this was already described in the release plan http://wiki.flightgear.org/Release_Plan cheers, Thorsten On Do, 2011-05-19 at 14:29 +0200, Torsten Dreyer wrote: Hi everybody, during this year's LinuxTag, Martin Spott, Mathias Fröhlich, Thorsten Brehm and myself developed a strategy and a concept about how to kick out new releases of FlightGear on a regular schedule. Please find our first draft here: http://wiki.flightgear.org/Release_Plan For the impatient reader, this is the abstract: We plan to have two releases per year, one in February, one in August. The first scheduled release following this concept will be 2.4.0 in August this year, 2.6.0 is scheduled for February 2012. If no major objections arise, we will set the version number on the current development stream to 2.3.0 and will call out a feature freeze on June 17th. Any comment and certainly any help for actually preparing the release is welcome. Thanks, Torsten Can you please update http://wiki.flightgear.org/Release_Plan with this very important information ? Something like a short description of current state ? Thanks a lot, Yves -- Simplify data backup and recovery for your virtual environment with vRanger. Installation's a snap, and flexible recovery options mean your data is safe, secure and there when you need it. Data protection magic? Nope - It's vRanger. Get your free trial download today. http://p.sf.net/sfu/quest-sfdev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] heads up: FlightGear release plan
we need to sit on this as 2.2.freeflightsim.org.. We need a marketing plam somwhat.. I hope we stick to release schedule.. On Tue, May 31, 2011 at 10:15 PM, HB-GRAL flightg...@sablonier.ch wrote: Am 22.05.11 14:37, schrieb ThorstenB: Hi, since there were no major objections to the release plan, we're proceeding as proposed. Current status: * We've officially grounded the releases/2.2.0 git branches yesterday. The flightgear/simgear releases/2.2.0 branches were merged back to master (not next! master always contains the latest release). However, as proposed, we won't invest any more time into 2.2.0, so there'll be no binaries on the download page, no updated aircraft downloads, no announcements, etc. * git/next is bumped to version 2.3.0 now. Actually we should have done so when we branched releases/2.2.0 in January. Remember. it's odd minor versions for the developer version now (git/next), even minor numbers for releases. * Hudson is prepared for providing release binaries and installers (thanks James!). Once we create a new release branch, Hudson should start building the binaries/installers (see Hudson's Windows-release, Mac-release, Linux-release projects). As usual, these will be updated hourly. We'll also provide complete Win/Mac installers (including fgdata base package) regularly, maybe about weekly, so these can be used for wider beta testing. We can't include the base package in the _hourly_ installers though, due to bandwidth/size limits (almost 400MB for the fgdata base package). * We also started assessing tracker issues (thanks Gijs!). Some were already fixed in the last days. And it doesn't look too bad, few issues are highly critical. However, there are some areas where we're missing people, for example for some (new) FDM, and a number of ATI-graphics issues. Have a look at the tracker: http://code.google.com/p/flightgear-bugs/issues/list Finally, as a reminder now: Only 4 more weeks to 2.4.0 feature freeze, remember June 17th, when we'll close sg+fg next branch, and (!) fgdata master for 4 weeks. Only bug fixes should be committed after June 17th. releases/2.4.0 will be branched on July 17th, when the main developer branches will be bumped to 2.5.0 and reopen for new features. Beta testing for 2.4.0 will continue for another month after that, till August 17th. But all this was already described in the release plan http://wiki.flightgear.org/Release_Plan cheers, Thorsten On Do, 2011-05-19 at 14:29 +0200, Torsten Dreyer wrote: Hi everybody, during this year's LinuxTag, Martin Spott, Mathias Fröhlich, Thorsten Brehm and myself developed a strategy and a concept about how to kick out new releases of FlightGear on a regular schedule. Please find our first draft here: http://wiki.flightgear.org/Release_Plan For the impatient reader, this is the abstract: We plan to have two releases per year, one in February, one in August. The first scheduled release following this concept will be 2.4.0 in August this year, 2.6.0 is scheduled for February 2012. If no major objections arise, we will set the version number on the current development stream to 2.3.0 and will call out a feature freeze on June 17th. Any comment and certainly any help for actually preparing the release is welcome. Thanks, Torsten Can you please update http://wiki.flightgear.org/Release_Plan with this very important information ? Something like a short description of current state ? Thanks a lot, Yves -- Simplify data backup and recovery for your virtual environment with vRanger. Installation's a snap, and flexible recovery options mean your data is safe, secure and there when you need it. Data protection magic? Nope - It's vRanger. Get your free trial download today. http://p.sf.net/sfu/quest-sfdev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel -- Simplify data backup and recovery for your virtual environment with vRanger. Installation's a snap, and flexible recovery options mean your data is safe, secure and there when you need it. Data protection magic? Nope - It's vRanger. Get your free trial download today. http://p.sf.net/sfu/quest-sfdev2dev___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] heads up: FlightGear release plan
Can you please update http://wiki.flightgear.org/Release_Plan with this very important information ? Something like a short description of current state ? Thanks a lot, Yves Hi Yves, this particular wiki page was written (mostly by myself) to document our release plan. I tried to make it as complete as possible but if anything is missing, please feel free to add it to the wiki. Thanks, Torsten -- Simplify data backup and recovery for your virtual environment with vRanger. Installation's a snap, and flexible recovery options mean your data is safe, secure and there when you need it. Data protection magic? Nope - It's vRanger. Get your free trial download today. http://p.sf.net/sfu/quest-sfdev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] heads up: FlightGear release plan
Hi, since there were no major objections to the release plan, we're proceeding as proposed. Current status: * We've officially grounded the releases/2.2.0 git branches yesterday. The flightgear/simgear releases/2.2.0 branches were merged back to master (not next! master always contains the latest release). However, as proposed, we won't invest any more time into 2.2.0, so there'll be no binaries on the download page, no updated aircraft downloads, no announcements, etc. * git/next is bumped to version 2.3.0 now. Actually we should have done so when we branched releases/2.2.0 in January. Remember. it's odd minor versions for the developer version now (git/next), even minor numbers for releases. * Hudson is prepared for providing release binaries and installers (thanks James!). Once we create a new release branch, Hudson should start building the binaries/installers (see Hudson's Windows-release, Mac-release, Linux-release projects). As usual, these will be updated hourly. We'll also provide complete Win/Mac installers (including fgdata base package) regularly, maybe about weekly, so these can be used for wider beta testing. We can't include the base package in the _hourly_ installers though, due to bandwidth/size limits (almost 400MB for the fgdata base package). * We also started assessing tracker issues (thanks Gijs!). Some were already fixed in the last days. And it doesn't look too bad, few issues are highly critical. However, there are some areas where we're missing people, for example for some (new) FDM, and a number of ATI-graphics issues. Have a look at the tracker: http://code.google.com/p/flightgear-bugs/issues/list Finally, as a reminder now: Only 4 more weeks to 2.4.0 feature freeze, remember June 17th, when we'll close sg+fg next branch, and (!) fgdata master for 4 weeks. Only bug fixes should be committed after June 17th. releases/2.4.0 will be branched on July 17th, when the main developer branches will be bumped to 2.5.0 and reopen for new features. Beta testing for 2.4.0 will continue for another month after that, till August 17th. But all this was already described in the release plan http://wiki.flightgear.org/Release_Plan cheers, Thorsten On Do, 2011-05-19 at 14:29 +0200, Torsten Dreyer wrote: Hi everybody, during this year's LinuxTag, Martin Spott, Mathias Fröhlich, Thorsten Brehm and myself developed a strategy and a concept about how to kick out new releases of FlightGear on a regular schedule. Please find our first draft here: http://wiki.flightgear.org/Release_Plan For the impatient reader, this is the abstract: We plan to have two releases per year, one in February, one in August. The first scheduled release following this concept will be 2.4.0 in August this year, 2.6.0 is scheduled for February 2012. If no major objections arise, we will set the version number on the current development stream to 2.3.0 and will call out a feature freeze on June 17th. Any comment and certainly any help for actually preparing the release is welcome. Thanks, Torsten -- What Every C/C++ and Fortran developer Should Know! Read this article and learn how Intel has extended the reach of its next-generation tools to help Windows* and Linux* C/C++ and Fortran developers boost performance applications - including clusters. http://p.sf.net/sfu/intel-dev2devmay ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] heads up: FlightGear release plan
Torsten wrote during this year's LinuxTag, Martin Spott, Mathias Fröhlich, Thorsten Brehm and myself developed a strategy and a concept about how to kick out new releases of FlightGear on a regular schedule. Please find our first draft here: http://wiki.flightgear.org/Release_Plan For the impatient reader, this is the abstract: We plan to have two releases per year, one in February, one in August. The first scheduled release following this concept will be 2.4.0 in August this year, 2.6.0 is scheduled for February 2012. If no major objections arise, we will set the version number on the current development stream to 2.3.0 and will call out a feature freeze on June 17th. Any comment and certainly any help for actually preparing the release is welcome. It's as good a plan as any other. However we missed the last planned release (2.2.0). I'm unaware of the reason(s), but I assume that release is dead. So I think the question we have to ask is not when but how. Until that is solved, the when is pretty meaningless. Nevertheless, having a plan at all is a good start. Vivian -- What Every C/C++ and Fortran developer Should Know! Read this article and learn how Intel has extended the reach of its next-generation tools to help Windows* and Linux* C/C++ and Fortran developers boost performance applications - including clusters. http://p.sf.net/sfu/intel-dev2devmay ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] heads up: FlightGear release plan
On Thu, 19 May 2011 17:47:43 +0100, Vivian wrote in message 6F98880E3CB048A183E86552C9E0CA5E@MAIN: Torsten wrote during this year's LinuxTag, Martin Spott, Mathias Fröhlich, Thorsten Brehm and myself developed a strategy and a concept about how to kick out new releases of FlightGear on a regular schedule. Please find our first draft here: http://wiki.flightgear.org/Release_Plan For the impatient reader, this is the abstract: We plan to have two releases per year, one in February, one in August. The first scheduled release following this concept will be 2.4.0 in August this year, 2.6.0 is scheduled for February 2012. If no major objections arise, we will set the version number on the current development stream to 2.3.0 and will call out a feature freeze on June 17th. Any comment and certainly any help for actually preparing the release is welcome. It's as good a plan as any other. However we missed the last planned release (2.2.0). I'm unaware of the reason(s), but I assume that release is dead. So I think the question we have to ask is not when but how. Until that is solved, the when is pretty meaningless. Nevertheless, having a plan at all is a good start. Vivian ..my opinion is the release guru should play around until he finds a bunch of git versions he likes and then release that combination as 2.2.0, might even become the preferred way. -- ..med vennlig hilsen = with Kind Regards from Arnt Karlsen ...with a number of polar bear hunters in his ancestry... Scenarios always come in sets of three: best case, worst case, and just in case. -- What Every C/C++ and Fortran developer Should Know! Read this article and learn how Intel has extended the reach of its next-generation tools to help Windows* and Linux* C/C++ and Fortran developers boost performance applications - including clusters. http://p.sf.net/sfu/intel-dev2devmay ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] heads up: FlightGear release plan
It's as good a plan as any other. There was another release plan? Wasn't aware of it ;-) However we missed the last planned release (2.2.0). I'm unaware of the reason(s), but I assume that release is dead. Yes, we simply declare it dead. To much has changed since the day we branched. So I think the question we have to ask is not when but how. Until that is solved, the when is pretty meaningless. You name it! That's why we spend an entire evening (with good pizza and good beer!) discussing the how which, in the end, automatically lead to the when. Torsten -- What Every C/C++ and Fortran developer Should Know! Read this article and learn how Intel has extended the reach of its next-generation tools to help Windows* and Linux* C/C++ and Fortran developers boost performance applications - including clusters. http://p.sf.net/sfu/intel-dev2devmay ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] heads up: FlightGear release plan
Am Donnerstag, den 19.05.2011, 17:47 +0100 schrieb Vivian Meazza: I think the question we have to ask is not when but how. Until that is solved, the when is pretty meaningless. And the last release got stalled more on a who than a how alone, when several people became too busy/blocked with RL commitments. You may not like that, but you can't blame anyone who has done a lot for FG and who has already invested a lot of free time into the project, that they suddenly need to shift their priorities or need a break for personal reasons. The new plan alone doesn't exclude the risk of this repeating - but there more people actively participate in the release, the less likely we're going to get stalled. So, it's up to all of us. And all of you can help: you can help by testing FlightGear right now and of course the upcoming release candidates and file bug reports. Of course we need as much help as possible for fixing issues. Things in the FG core will need to be fixed - but also issues concerning fgdata, such as working on aircraft or GUI. Everyone can look at the bug tracker, pick issues and submit patches. And even if you can't work on code or aircraft, you can still help by trying to narrow done what exactly causes a specific bug issue (such as testing which commit introduced a particular problem or what command-line/environment/... setting exactly triggers a certain problem). Or you can help with updating/improving manuals. Lots to do - any help is welcome! cheers, Thorsten -- What Every C/C++ and Fortran developer Should Know! Read this article and learn how Intel has extended the reach of its next-generation tools to help Windows* and Linux* C/C++ and Fortran developers boost performance applications - including clusters. http://p.sf.net/sfu/intel-dev2devmay ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel