Re: [Flightgear-devel] Release 2.10.0: Decision Altitude
Curt, I noticed the SG/FG packages got updated on the mirrors. So I checked them out again: still the same issue. How did you create the source tarballs? Having the version number 2.8 in it looks like they were created from an older, used git clone and not a fresh or cleaned up one. The tarballs should only contain files that are in git, nothing that gets created during configure/compile time. Chris Curtis Olson wrote: Certainly this is my fault, however, I must misunderstand something about cmake for this to happen. Can someone enlighten me and tell me what I need to do to fix this? Maybe there is something we can tweak in the future if the default behavior requires manual intervention to achieve the correct outcome? Thanks for checking this out Chris. Curt. -- The Go Parallel Website, sponsored by Intel - in partnership with Geeknet, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials, tech docs, whitepapers, evaluation guides, and opinion stories. Check out the most recent posts - join the conversation now. http://goparallel.sourceforge.net/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Release 2.10.0: Decision Altitude
Hi Christian, I completely blew away my build_flightgear and build_simgear directories so they should be totally clean for the latest version of the source code. Are our cmake rules doing something they shouldn't and writing files in the original source tree when you do out of source builds? I thought (I was 100% sure until now that you say there was a problem) that I looked at version.h in my build_simgear directory and it said 2.10.0 I really want to get this fixed as quickly as possible, but I'm confused as to where things could be going wrong or how to fix it. Back in the day I had the automake tools really figured out for myself at a deep level, but I unfortunately don't have that same level of groking for the cmake tools. Curt. On Mon, Feb 18, 2013 at 4:31 AM, Christian Schmitt ch...@ilovelinux.dewrote: Curt, I noticed the SG/FG packages got updated on the mirrors. So I checked them out again: still the same issue. How did you create the source tarballs? Having the version number 2.8 in it looks like they were created from an older, used git clone and not a fresh or cleaned up one. The tarballs should only contain files that are in git, nothing that gets created during configure/compile time. Chris Curtis Olson wrote: Certainly this is my fault, however, I must misunderstand something about cmake for this to happen. Can someone enlighten me and tell me what I need to do to fix this? Maybe there is something we can tweak in the future if the default behavior requires manual intervention to achieve the correct outcome? Thanks for checking this out Chris. Curt. -- The Go Parallel Website, sponsored by Intel - in partnership with Geeknet, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials, tech docs, whitepapers, evaluation guides, and opinion stories. Check out the most recent posts - join the conversation now. http://goparallel.sourceforge.net/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel -- Curtis Olson: http://www.atiak.com - http://aem.umn.edu/~uav/ http://www.flightgear.org - http://gallinazo.flightgear.org -- The Go Parallel Website, sponsored by Intel - in partnership with Geeknet, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials, tech docs, whitepapers, evaluation guides, and opinion stories. Check out the most recent posts - join the conversation now. http://goparallel.sourceforge.net/___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Release 2.10.0: Decision Altitude
Ok, I see now that in simgear-2.10.tar.bz2 the top level file version does report 2.10.0 but the simgear/version.h file is saying 2.8.0 So my question are: 1. for an out-of-source build, why is the build system writing files in the source tree? Can we fix that? 2. what is the proper cmake fix here so it doesn't happen in the future? Thanks, Curt. On Mon, Feb 18, 2013 at 8:26 AM, Curtis Olson curtol...@flightgear.orgwrote: Hi Christian, I completely blew away my build_flightgear and build_simgear directories so they should be totally clean for the latest version of the source code. Are our cmake rules doing something they shouldn't and writing files in the original source tree when you do out of source builds? I thought (I was 100% sure until now that you say there was a problem) that I looked at version.h in my build_simgear directory and it said 2.10.0 I really want to get this fixed as quickly as possible, but I'm confused as to where things could be going wrong or how to fix it. Back in the day I had the automake tools really figured out for myself at a deep level, but I unfortunately don't have that same level of groking for the cmake tools. Curt. On Mon, Feb 18, 2013 at 4:31 AM, Christian Schmitt ch...@ilovelinux.dewrote: Curt, I noticed the SG/FG packages got updated on the mirrors. So I checked them out again: still the same issue. How did you create the source tarballs? Having the version number 2.8 in it looks like they were created from an older, used git clone and not a fresh or cleaned up one. The tarballs should only contain files that are in git, nothing that gets created during configure/compile time. Chris Curtis Olson wrote: Certainly this is my fault, however, I must misunderstand something about cmake for this to happen. Can someone enlighten me and tell me what I need to do to fix this? Maybe there is something we can tweak in the future if the default behavior requires manual intervention to achieve the correct outcome? Thanks for checking this out Chris. Curt. -- The Go Parallel Website, sponsored by Intel - in partnership with Geeknet, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials, tech docs, whitepapers, evaluation guides, and opinion stories. Check out the most recent posts - join the conversation now. http://goparallel.sourceforge.net/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel -- Curtis Olson: http://www.atiak.com - http://aem.umn.edu/~uav/ http://www.flightgear.org - http://gallinazo.flightgear.org -- Curtis Olson: http://www.atiak.com - http://aem.umn.edu/~uav/ http://www.flightgear.org - http://gallinazo.flightgear.org -- The Go Parallel Website, sponsored by Intel - in partnership with Geeknet, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials, tech docs, whitepapers, evaluation guides, and opinion stories. Check out the most recent posts - join the conversation now. http://goparallel.sourceforge.net/___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Release 2.10.0: Decision Altitude
On 02/18/2013 03:36 PM, Curtis Olson wrote:
Ok, I see now that in simgear-2.10.tar.bz2 the top level file version
does report 2.10.0 but the simgear/version.h file is saying 2.8.0
So my question are:
1. for an out-of-source build, why is the build system writing files in
the source tree? Can we fix that?
2. what is the proper cmake fix here so it doesn't happen in the future?
I see that simgear/CMakeList.txt defines:
file(WRITE ${PROJECT_BINARY_DIR}/simgear/version.h #define
SIMGEAR_VERSION ${SIMGEAR_VERSION})
it would be better to create a version.h.in file and use
CONFIGURE_FILE(
${CMAKE_CURRENT_SOURCE_DIR}/simgear/version.h.in
containing:
#define SIMGEAR_VERSION @SIMGEAR_VERSION@
Erik
--
http://www.adalin.com
- Hardware accelerated AeonWave and OpenAL for Windows and Linux
--
The Go Parallel Website, sponsored by Intel - in partnership with Geeknet,
is your hub for all things parallel software development, from weekly thought
leadership blogs to news, videos, case studies, tutorials, tech docs,
whitepapers, evaluation guides, and opinion stories. Check out the most
recent posts - join the conversation now. http://goparallel.sourceforge.net/
___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Release 2.10.0: Decision Altitude
On 18 Feb 2013, at 14:57, Erik Hofman e...@ehofman.com wrote:
I see that simgear/CMakeList.txt defines:
file(WRITE ${PROJECT_BINARY_DIR}/simgear/version.h #define
SIMGEAR_VERSION ${SIMGEAR_VERSION})
it would be better to create a version.h.in file and use
CONFIGURE_FILE(
${CMAKE_CURRENT_SOURCE_DIR}/simgear/version.h.in
containing:
#define SIMGEAR_VERSION @SIMGEAR_VERSION@
Hmm, I don't think it matter *how* you write the file: PROJECT_BINARY_DIR seems
like the correct place based on my understand of cmake. I could be wrong of
course, but it makes more sense to me than CMAKE_CURRENT_SOURCE_DIR.
Since, we want to write version.h inside the build tree - the install hierarchy
is no use, and we certainly don't want to write to the source dir!
James
--
The Go Parallel Website, sponsored by Intel - in partnership with Geeknet,
is your hub for all things parallel software development, from weekly thought
leadership blogs to news, videos, case studies, tutorials, tech docs,
whitepapers, evaluation guides, and opinion stories. Check out the most
recent posts - join the conversation now. http://goparallel.sourceforge.net/
___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Release 2.10.0: Decision Altitude
Ok that got tangled up. Here's a diff.
Erik
--
http://www.adalin.com
- Hardware accelerated AeonWave and OpenAL for Windows and Linux
diff --git a/simgear/CMakeLists.txt b/simgear/CMakeLists.txt
index b4e299a..0725a78 100644
--- a/simgear/CMakeLists.txt
+++ b/simgear/CMakeLists.txt
@@ -1,5 +1,7 @@
-file(WRITE ${PROJECT_BINARY_DIR}/simgear/version.h #define SIMGEAR_VERSION ${SIMGEAR_VERSION})
+CONFIGURE_FILE(
+ ${CMAKE_CURRENT_SOURCE_DIR}/version.h.in
+ ${CMAKE_CURRENT_BINARY_DIR}/version.h)
foreach( mylibfolder
bucket
diff --git a/simgear/version.h.in b/simgear/version.h.in
index 635495e..a3def5d 100644
--- a/simgear/version.h.in
+++ b/simgear/version.h.in
@@ -26,7 +26,7 @@
#define _SIMGEAR_VERSION_H
-#define SIMGEAR_VERSION @VERSION@
+#define SIMGEAR_VERSION @SIMGEAR_VERSION@
#endif // _SIMGEAR_VERSION_H
--
The Go Parallel Website, sponsored by Intel - in partnership with Geeknet,
is your hub for all things parallel software development, from weekly thought
leadership blogs to news, videos, case studies, tutorials, tech docs,
whitepapers, evaluation guides, and opinion stories. Check out the most
recent posts - join the conversation now. http://goparallel.sourceforge.net/___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Release 2.10.0: Decision Altitude
On 02/18/2013 04:04 PM, James Turner wrote: Hmm, I don't think it matter *how* you write the file: PROJECT_BINARY_DIR seems like the correct place based on my understand of cmake. I could be wrong of course, but it makes more sense to me than CMAKE_CURRENT_SOURCE_DIR. You seem to be correct, when doing a make package_source I see simgear-2.11.0/build/simgear/version.h More investigation to do Erik -- http://www.adalin.com - Hardware accelerated AeonWave and OpenAL for Windows and Linux -- The Go Parallel Website, sponsored by Intel - in partnership with Geeknet, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials, tech docs, whitepapers, evaluation guides, and opinion stories. Check out the most recent posts - join the conversation now. http://goparallel.sourceforge.net/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Release 2.10.0: Decision Altitude
On 02/18/2013 04:08 PM, Erik Hofman wrote:
On 02/18/2013 04:04 PM, James Turner wrote:
Hmm, I don't think it matter *how* you write the file: PROJECT_BINARY_DIR
seems like the correct place based on my understand of cmake. I could be
wrong of course, but it makes more sense to me than CMAKE_CURRENT_SOURCE_DIR.
You seem to be correct, when doing a make package_source I see
simgear-2.11.0/build/simgear/version.h
More investigation to do
I suspect:
set(HEADERS compiler.h constants.h sg_inlines.h
${PROJECT_BINARY_DIR}/simgear/version.h)
is the culprit.
Erik
--
http://www.adalin.com
- Hardware accelerated AeonWave and OpenAL for Windows and Linux
--
The Go Parallel Website, sponsored by Intel - in partnership with Geeknet,
is your hub for all things parallel software development, from weekly thought
leadership blogs to news, videos, case studies, tutorials, tech docs,
whitepapers, evaluation guides, and opinion stories. Check out the most
recent posts - join the conversation now. http://goparallel.sourceforge.net/
___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Release 2.10.0: Decision Altitude
Sorry Curt, but nothing writes into the source dir if you use a sane, clean and proper checkout from git. Your tarballs make me think that you already ran cmake inside the source dir prior to packaging them. Could you run git clean -fdx inside the source dir and tar the result up again? This will eliminate any remains from prior cmake processings. Chris Curtis Olson wrote: Ok, I see now that in simgear-2.10.tar.bz2 the top level file version does report 2.10.0 but the simgear/version.h file is saying 2.8.0 So my question are: 1. for an out-of-source build, why is the build system writing files in the source tree? Can we fix that? 2. what is the proper cmake fix here so it doesn't happen in the future? -- The Go Parallel Website, sponsored by Intel - in partnership with Geeknet, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials, tech docs, whitepapers, evaluation guides, and opinion stories. Check out the most recent posts - join the conversation now. http://goparallel.sourceforge.net/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Release 2.10.0: Decision Altitude
On 18 Feb 2013, at 15:10, Erik Hofman e...@ehofman.com wrote: You seem to be correct, when doing a make package_source I see simgear-2.11.0/build/simgear/version.h The tar balls created by Jenkins (Linux-release) seem to be fine. They contain version.h.in, but no version.h They're created by the following script: https://gitorious.org/fg/fgmeta/blobs/master/hudson_build_release.sh And the results look 100% correct to me (download and check for yourselves: http://flightgear.simpits.org:8080/job/Linux-release/ ) James -- The Go Parallel Website, sponsored by Intel - in partnership with Geeknet, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials, tech docs, whitepapers, evaluation guides, and opinion stories. Check out the most recent posts - join the conversation now. http://goparallel.sourceforge.net/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Release 2.10.0: Decision Altitude
Maybe something has already been tweaked between v2.8 and v2.10. After I
manually removed the simgear/version.h file it did not come back again --
so maybe we will be in good shape for future releases.
I noticed that simgear/version.h (along with all the other build time
files) are explicitely listed in the .gitignore files throughout simgear.
Here is me wondering out loud: If we *strongly* recommend out of source
builds, maybe it would make sense to *not* list build files in the
.gitignore so they clearly show up as an anomoly. Previously when I did a
git status, it showed a pristine git tree on the 2.10 branch with no
changes or differences -- but the problem was hidden because of the
.gitignore file.
I found the git status --ignored command which shows ignored files, but
this is a lot of manual messing around to have to remember every 6 months
-- especially when 6 months is about the shelf life of remember specific
details on how or what I've done in the past if haven't repeated it since.
:-)
Anway, I have updated the source files on the ftp server and hopefully we
are ok for this release now.
Curt.
On Mon, Feb 18, 2013 at 9:10 AM, Erik Hofman e...@ehofman.com wrote:
On 02/18/2013 04:08 PM, Erik Hofman wrote:
On 02/18/2013 04:04 PM, James Turner wrote:
Hmm, I don't think it matter *how* you write the file:
PROJECT_BINARY_DIR seems like the correct place based on my understand of
cmake. I could be wrong of course, but it makes more sense to me than
CMAKE_CURRENT_SOURCE_DIR.
You seem to be correct, when doing a make package_source I see
simgear-2.11.0/build/simgear/version.h
More investigation to do
I suspect:
set(HEADERS compiler.h constants.h sg_inlines.h
${PROJECT_BINARY_DIR}/simgear/version.h)
is the culprit.
Erik
--
http://www.adalin.com
- Hardware accelerated AeonWave and OpenAL for Windows and Linux
--
The Go Parallel Website, sponsored by Intel - in partnership with Geeknet,
is your hub for all things parallel software development, from weekly
thought
leadership blogs to news, videos, case studies, tutorials, tech docs,
whitepapers, evaluation guides, and opinion stories. Check out the most
recent posts - join the conversation now.
http://goparallel.sourceforge.net/
___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel
--
Curtis Olson:
http://www.atiak.com - http://aem.umn.edu/~uav/
http://www.flightgear.org - http://gallinazo.flightgear.org
--
The Go Parallel Website, sponsored by Intel - in partnership with Geeknet,
is your hub for all things parallel software development, from weekly thought
leadership blogs to news, videos, case studies, tutorials, tech docs,
whitepapers, evaluation guides, and opinion stories. Check out the most
recent posts - join the conversation now. http://goparallel.sourceforge.net/___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Release 2.10.0: Decision Altitude
The 'make package_source' problem was related to this diff.
Erik
--
http://www.adalin.com
- Hardware accelerated AeonWave and OpenAL for Windows and Linux
diff --git a/CMakeLists.txt b/CMakeLists.txt
index f6dd5fe..615b82e 100644
--- a/CMakeLists.txt
+++ b/CMakeLists.txt
@@ -42,7 +42,7 @@ if (NOT EMBEDDED_SIMGEAR)
set(CPACK_SOURCE_GENERATOR TBZ2)
set(CPACK_SOURCE_PACKAGE_FILE_NAME simgear-${SIMGEAR_VERSION} CACHE INTERNAL tarball basename)
set(CPACK_SOURCE_IGNORE_FILES
- ^${PROJECT_SOURCE_DIR}/.git;.gitignore;Makefile.am;~$;${CPACK_SOURCE_IGNORE_FILES})
+ ^${PROJECT_SOURCE_DIR}/.git;.gitignore;Makefile.am;~$;${CMAKE_CURRENT_BINARY_DIR}/simgear/version.h;${CPACK_SOURCE_IGNORE_FILES})
message(STATUS ignoring: ${CPACK_SOURCE_IGNORE_FILES})
--
The Go Parallel Website, sponsored by Intel - in partnership with Geeknet,
is your hub for all things parallel software development, from weekly thought
leadership blogs to news, videos, case studies, tutorials, tech docs,
whitepapers, evaluation guides, and opinion stories. Check out the most
recent posts - join the conversation now. http://goparallel.sourceforge.net/___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Release 2.10.0: Decision Altitude
Hi, while this might be a minor issue, I still want to bring it up here: The SG and FG 2.10.0 release tarballs from the ibiblio mirror contain version.h files with version number 2.8.0. While this should be overwritten by cmake on configure time I just experienced a case where it wasn't with the result that fgfs didn't run because of fgdata/program mismatch. The version.h files should not be in the distributed tarball as they are runtime generated files. Just FYI Chris Curtis Olson wrote: Hi Everyone, I just wanted to send a quick update on the release process. Feb 17 arrives at different times at different places and it is still Feb 16 here for another hour. I have uploaded the source and the mac version of the release to ibiblio.org and the final windows version is being uploaded right now with about 2hr 45min left to go. So it will not finish before I head off to bed. When I get up I will hopefully find that everything transferred correctly. I'll update the kingmont mirror and hopefully the other mirrors will be getting in sync soon too. At that point I'll update the download links on the web site, try to find Stuart's release announcement in my email archives, etc. etc. I have a couple commitments tomorrow so I hope to have most of the release things taken care of by mid-afternoon (MN time) but we'll see. Please be patient if not everything is quite in place by Feb 17 00:00 UTC, we are getting better, but we aren't quite that good yet. :-) I appreciate all the hard work that so many people have put in on so many fronts to make this release happen smoothly! Thanks! Curt. -- The Go Parallel Website, sponsored by Intel - in partnership with Geeknet, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials, tech docs, whitepapers, evaluation guides, and opinion stories. Check out the most recent posts - join the conversation now. http://goparallel.sourceforge.net/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Release 2.10.0: Decision Altitude
Hi, upon further inspection the problem appears to be more serious: It occurs if SG/FG are built in a separate build dir, as recommended by the cmake process. We then have version 2.8 in the original sources and 2.10 in the build dir. Why 2.8 gets picked up is beyond my knowledge but I would consider this to be a serious issue and we should fix it before getting flamed post-release. Chris Christian Schmitt wrote: Hi, while this might be a minor issue, I still want to bring it up here: The SG and FG 2.10.0 release tarballs from the ibiblio mirror contain version.h files with version number 2.8.0. While this should be overwritten by cmake on configure time I just experienced a case where it wasn't with the result that fgfs didn't run because of fgdata/program mismatch. The version.h files should not be in the distributed tarball as they are runtime generated files. Just FYI Chris -- The Go Parallel Website, sponsored by Intel - in partnership with Geeknet, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials, tech docs, whitepapers, evaluation guides, and opinion stories. Check out the most recent posts - join the conversation now. http://goparallel.sourceforge.net/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Release 2.10.0: Decision Altitude
Certainly this is my fault, however, I must misunderstand something about cmake for this to happen. Can someone enlighten me and tell me what I need to do to fix this? Maybe there is something we can tweak in the future if the default behavior requires manual intervention to achieve the correct outcome? Thanks for checking this out Chris. Curt. On Sun, Feb 17, 2013 at 3:16 PM, Christian Schmitt ch...@ilovelinux.dewrote: Hi, upon further inspection the problem appears to be more serious: It occurs if SG/FG are built in a separate build dir, as recommended by the cmake process. We then have version 2.8 in the original sources and 2.10 in the build dir. Why 2.8 gets picked up is beyond my knowledge but I would consider this to be a serious issue and we should fix it before getting flamed post-release. Chris Christian Schmitt wrote: Hi, while this might be a minor issue, I still want to bring it up here: The SG and FG 2.10.0 release tarballs from the ibiblio mirror contain version.h files with version number 2.8.0. While this should be overwritten by cmake on configure time I just experienced a case where it wasn't with the result that fgfs didn't run because of fgdata/program mismatch. The version.h files should not be in the distributed tarball as they are runtime generated files. Just FYI Chris -- The Go Parallel Website, sponsored by Intel - in partnership with Geeknet, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials, tech docs, whitepapers, evaluation guides, and opinion stories. Check out the most recent posts - join the conversation now. http://goparallel.sourceforge.net/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel -- Curtis Olson: http://www.atiak.com - http://aem.umn.edu/~uav/ http://www.flightgear.org - http://gallinazo.flightgear.org -- The Go Parallel Website, sponsored by Intel - in partnership with Geeknet, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials, tech docs, whitepapers, evaluation guides, and opinion stories. Check out the most recent posts - join the conversation now. http://goparallel.sourceforge.net/___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Release 2.10.0: Decision Altitude
Hy Yves Sorry, I do not understand your question. Could you clarify, please? Torsten Am 16.02.2013 00:17, schrieb ys: Hi Torsten What does mean no public answer in this list for this decision ? -Yves Am 15.02.2013 um 16:16 schrieb Torsten Dreyer tors...@t3r.de: Hi all, at one point during every ILS approach you reach the decision altitude with two options: continue approach or go around. Being the copilot on our approach into the 2.10 release, I'd call out minimum, approach lights in sight, continue! If no one shouts out loudly _NOW_, I'm going to tag the release branches tomorrow (Saturday) morning (Central European Time) and give the package managers the GO to build and distribute the bundles. That should give us a ready-to-download release just in time on Sunday the 17th. Greetings, Torsten -- Free Next-Gen Firewall Hardware Offer Buy your Sophos next-gen firewall before the end March 2013 and get the hardware for free! Learn more. http://p.sf.net/sfu/sophos-d2d-feb ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel -- The Go Parallel Website, sponsored by Intel - in partnership with Geeknet, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials, tech docs, whitepapers, evaluation guides, and opinion stories. Check out the most recent posts - join the conversation now. http://goparallel.sourceforge.net/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel -- The Go Parallel Website, sponsored by Intel - in partnership with Geeknet, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials, tech docs, whitepapers, evaluation guides, and opinion stories. Check out the most recent posts - join the conversation now. http://goparallel.sourceforge.net/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Release 2.10.0: Decision Altitude
Hi Everyone, I just wanted to send a quick update on the release process. Feb 17 arrives at different times at different places and it is still Feb 16 here for another hour. I have uploaded the source and the mac version of the release to ibiblio.org and the final windows version is being uploaded right now with about 2hr 45min left to go. So it will not finish before I head off to bed. When I get up I will hopefully find that everything transferred correctly. I'll update the kingmont mirror and hopefully the other mirrors will be getting in sync soon too. At that point I'll update the download links on the web site, try to find Stuart's release announcement in my email archives, etc. etc. I have a couple commitments tomorrow so I hope to have most of the release things taken care of by mid-afternoon (MN time) but we'll see. Please be patient if not everything is quite in place by Feb 17 00:00 UTC, we are getting better, but we aren't quite that good yet. :-) I appreciate all the hard work that so many people have put in on so many fronts to make this release happen smoothly! Thanks! Curt. On Fri, Feb 15, 2013 at 9:16 AM, Torsten Dreyer wrote: Hi all, at one point during every ILS approach you reach the decision altitude with two options: continue approach or go around. Being the copilot on our approach into the 2.10 release, I'd call out minimum, approach lights in sight, continue! If no one shouts out loudly _NOW_, I'm going to tag the release branches tomorrow (Saturday) morning (Central European Time) and give the package managers the GO to build and distribute the bundles. That should give us a ready-to-download release just in time on Sunday the 17th. Greetings, Torsten -- Free Next-Gen Firewall Hardware Offer Buy your Sophos next-gen firewall before the end March 2013 and get the hardware for free! Learn more. http://p.sf.net/sfu/sophos-d2d-feb ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel -- Curtis Olson: http://www.atiak.com - http://aem.umn.edu/~uav/ http://www.flightgear.org - http://gallinazo.flightgear.org -- The Go Parallel Website, sponsored by Intel - in partnership with Geeknet, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials, tech docs, whitepapers, evaluation guides, and opinion stories. Check out the most recent posts - join the conversation now. http://goparallel.sourceforge.net/___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
[Flightgear-devel] Release 2.10.0: Decision Altitude
Hi all, at one point during every ILS approach you reach the decision altitude with two options: continue approach or go around. Being the copilot on our approach into the 2.10 release, I'd call out minimum, approach lights in sight, continue! If no one shouts out loudly _NOW_, I'm going to tag the release branches tomorrow (Saturday) morning (Central European Time) and give the package managers the GO to build and distribute the bundles. That should give us a ready-to-download release just in time on Sunday the 17th. Greetings, Torsten -- Free Next-Gen Firewall Hardware Offer Buy your Sophos next-gen firewall before the end March 2013 and get the hardware for free! Learn more. http://p.sf.net/sfu/sophos-d2d-feb ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Release 2.10.0: Decision Altitude
I would just add a quick last minute request to the developers (or anyone else). We haven't organized an effort to collect screen shots for the v2.10 release yet and I'd like to do that now. If anyone is interested/willing to submit v2.10 screen shots (based on the release candidates or other pre-release builds) I would be happy to take them. You can send them directly to me and I will assemble a screen shot page on the web site. It would be wonderful to have a dozen or two high quality images in time for the release, but we can always add more images to the page later. +1 to shots that highlight something new or interesting in FlightGear and +1 to any shot that is just a nice, well composed FlightGear scene. And as usual, I'd like to steer clear of images that show private unreleased work, or content that would be difficult for an average user to chase down and see themselves. I think most people are visual and if we don't change up any imagery on the web site (some of the images are from the 2.6 release or maybe earlier) there could be a perception that not much has gone on in the last 6 months. Thanks! Curt. On Fri, Feb 15, 2013 at 9:16 AM, Torsten Dreyer tors...@t3r.de wrote: Hi all, at one point during every ILS approach you reach the decision altitude with two options: continue approach or go around. Being the copilot on our approach into the 2.10 release, I'd call out minimum, approach lights in sight, continue! If no one shouts out loudly _NOW_, I'm going to tag the release branches tomorrow (Saturday) morning (Central European Time) and give the package managers the GO to build and distribute the bundles. That should give us a ready-to-download release just in time on Sunday the 17th. Greetings, Torsten -- Free Next-Gen Firewall Hardware Offer Buy your Sophos next-gen firewall before the end March 2013 and get the hardware for free! Learn more. http://p.sf.net/sfu/sophos-d2d-feb ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel -- Curtis Olson: http://www.atiak.com - http://aem.umn.edu/~uav/ http://www.flightgear.org - http://gallinazo.flightgear.org -- Free Next-Gen Firewall Hardware Offer Buy your Sophos next-gen firewall before the end March 2013 and get the hardware for free! Learn more. http://p.sf.net/sfu/sophos-d2d-feb___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Release 2.10.0: Decision Altitude
Hi Torsten What does mean no public answer in this list for this decision ? -Yves Am 15.02.2013 um 16:16 schrieb Torsten Dreyer tors...@t3r.de: Hi all, at one point during every ILS approach you reach the decision altitude with two options: continue approach or go around. Being the copilot on our approach into the 2.10 release, I'd call out minimum, approach lights in sight, continue! If no one shouts out loudly _NOW_, I'm going to tag the release branches tomorrow (Saturday) morning (Central European Time) and give the package managers the GO to build and distribute the bundles. That should give us a ready-to-download release just in time on Sunday the 17th. Greetings, Torsten -- Free Next-Gen Firewall Hardware Offer Buy your Sophos next-gen firewall before the end March 2013 and get the hardware for free! Learn more. http://p.sf.net/sfu/sophos-d2d-feb ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel -- The Go Parallel Website, sponsored by Intel - in partnership with Geeknet, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials, tech docs, whitepapers, evaluation guides, and opinion stories. Check out the most recent posts - join the conversation now. http://goparallel.sourceforge.net/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
