Re: [Flightgear-devel] Release 2.10.0: final tags for 2.10.0
Am 15.02.2013 16:16, schrieb Torsten Dreyer: 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. Done. The tag version/2.10.0-final exists on fgdata, simgear and flightgear. Please start creating the tarballs, installers, binaries et.al. for the final FlightGear 2.10 release from that tag. FWIW, I have also merged the release/2.10.0 branch into the master branch on simgear and flightgear. Both had conflicts on a few files. I resolved these conflicts by checking out the files of the release branch (git checkout --theirs while sitting on master) and committing those versions. This has been documented in the merge commit. There is still one open item: To push the final pdf and html documentation to the mapserver site. I do not have write access, so may please somebody who knows how to do that and is able to do so take care of it? Torsten -- 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: final tags for 2.10.0
Hi Torsten, De : Torsten Dreyer tors...@t3r.de Envoyé le : Samedi 16 février 2013 10h48 There is still one open item: To push the final pdf and html documentation to the mapserver site. I do not have write access, so may please somebody who knows how to do that and is able to do so take care of it? To my knowledge, this is a fully automated task, which is croned at each update. So for the online stuff everything seems to be fine. The only thing I do not know is who is taking care to update the getstart.pdf files pushed into the installers and tarballs for the release. -- 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: final tags for 2.10.0
To my knowledge, this is a fully automated task, which is croned at each update. So for the online stuff everything seems to be fine. The only thing I do not know is who is taking care to update the getstart.pdf files pushed into the installers and tarballs for the release. Ah, good news. I just love automated tasks ;-) Stuart took care of the getstart.pdf for this release, so I assume we are all set w.r.t. documentation this time. Thanks Torsten -- 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
