Es/FlightGear Newsletter July 2011: Difference between revisions

Jump to navigation Jump to search
Line 16: Line 16:
=== Versiones Snapshot ===
=== Versiones Snapshot ===
Some of you might know that James and Gene have spent a lot of time assembling a [[FlightGear Build Server|nightly build server]] for the FlightGear project. This monitors the [[git]] repository for any source code changes and then spawns builds for Windows, Linux, and Mac.
Some of you might know that James and Gene have spent a lot of time assembling a [[FlightGear Build Server|nightly build server]] for the FlightGear project. This monitors the [[git]] repository for any source code changes and then spawns builds for Windows, Linux, and Mac.
Algunos de ustedes podrían saber que James y Gene han pasado mucho tiempo de montaje de un [[FlightGear Build Server | servidor de compilación nocturna]] para el proyecto FlightGear. Esto controla el [[git]] repositorio para cualquier cambio de código fuente y, a continuación genera versiones para Windows, Linux y Mac.


You can find the build server at http://flightgear.simpits.org:8080/
You can find the build server at http://flightgear.simpits.org:8080/


This is really great work and a huge contribution to the FlightGear project. Unfortunately, to run a nightly build from the build server, you still have to pull the latest data tree from the git repository. That's not all that hard, once you work through the details, but it's a bit "fiddly" for some folks.
This is really great work and a huge contribution to the FlightGear project. Unfortunately, to run a nightly build from the build server, you still have to pull the latest data tree from the git repository. That's not all that hard, once you work through the details, but it's a bit "fiddly" for some folks.
Usted puede encontrar el servidor de construir en http://flightgear.simpits.org:8080/
Esto es realmente un gran trabajo y una enorme contribución al proyecto FlightGear. Por desgracia, para ejecutar un programa nocturno de construir a partir de la construcción de servidor, usted todavía tiene que tirar de la última árbol de datos desde el repositorio git. Eso no es todo tan difícil, una vez que usted trabaja a través de los detalles, pero es un poco "incómoda" para algunas personas.


So Curt has been playing around with creating a developer's snapshot release which would be similar to our official release. It is one big setup.exe that includes all the programs and the data. We are hopeful that this will eventually make the current development version of FlightGear more accessible for "joe average" users which would then in term hopefully give us more feedback and bug reports ahead of our official release.
So Curt has been playing around with creating a developer's snapshot release which would be similar to our official release. It is one big setup.exe that includes all the programs and the data. We are hopeful that this will eventually make the current development version of FlightGear more accessible for "joe average" users which would then in term hopefully give us more feedback and bug reports ahead of our official release.
Así que Curt ha estado jugando con la creación de la liberación de un desarrollador de instantáneas, que sería similar a nuestro lanzamiento oficial. Se trata de un archivo setup.exe grande que incluye todos los programas y los datos. Tenemos la esperanza de que esto eventualmente hará que la versión de desarrollo actual de FlightGear más accesible de "Joe" promedio de los usuarios que luego en el término ojalá nos den más informes de retroalimentación y corrección de errores antes de nuestro lanzamiento oficial.


None of this would be possible without the "Jenkins" (formerly Hudson) build server that Gene and James set up.
None of this would be possible without the "Jenkins" (formerly Hudson) build server that Gene and James set up.
Nada de esto sería posible sin la "Jenkins" (antes de Hudson) crear servidor en el que Gene y Santiago de configurar.


There are a couple things that are done with this snapshot package:
There are a couple things that are done with this snapshot package:
* An unique app name of the form <tt>FlightGear YYYYMMDD</tt> is assigned so you can have multiple versions installed concurrently and they don't step on each other and don't step on the official release. If people maintain multiple snapshots installed on their systems, that might help narrow down when a bug was introduced.
* An unique app name of the form <tt>FlightGear YYYYMMDD</tt> is assigned so you can have multiple versions installed concurrently and they don't step on each other and don't step on the official release. If people maintain multiple snapshots installed on their systems, that might help narrow down when a bug was introduced.
* The openal installer "oalinst.exe" is included and vcredist_x86.exe ... neither of these may be required in the long term if we can just ship the needed dll's, but that probably needs further testing.
* The openal installer "oalinst.exe" is included and vcredist_x86.exe ... neither of these may be required in the long term if we can just ship the needed dll's, but that probably needs further testing.
Hay un par de cosas que se hacen con este paquete de instantáneas:
* El nombre de la aplicación única de la forma <tt> FlightGear YYYYMMDD </ tt> se asigna así que usted puede tener varias versiones instaladas al mismo tiempo y no se entorpezcan unos a otros y no pisar el lanzamiento oficial. Si las personas a mantener varias instantáneas instalado en sus sistemas, que pueden ayudar a reducir, cuando un error se introdujo.
* El instalador de OpenAL "oalinst.exe" está incluido y vcredist_x86.exe ... ninguno de ellos puede ser necesaria en el largo plazo si podemos enviar el archivo DLL es necesario, pero que probablemente necesite más pruebas.


Does it basically work? Are there any major packaging blunders? Please note, FlightGear bugs and feature request should still be handled through normal channels. But I am interested in packaging issues right now.
Does it basically work? Are there any major packaging blunders? Please note, FlightGear bugs and feature request should still be handled through normal channels. But I am interested in packaging issues right now.
Line 34: Line 48:


For downloads please see: [http://mirrors.ibiblio.org/pub/mirrors/flightgear/ftp/Win32/Setup%20FlightGear%20v20110629.exe this location]
For downloads please see: [http://mirrors.ibiblio.org/pub/mirrors/flightgear/ftp/Win32/Setup%20FlightGear%20v20110629.exe this location]
¿Tiene básicamente funciona? ¿Hay errores de envasado más importantes? Tenga en cuenta que los errores de FlightGear y la solicitud función todavía deben ser manejados a través de canales normales. Pero estoy interesado en los problemas de embalaje en estos momentos.
Para enviar sus comentarios por favor, utilice [http://flightgear.org/forums/viewtopic.php?f=28&t=10488 este hilo del foro].
Para descargas por favor visite: [20FlightGear http://mirrors.ibiblio.org/pub/mirrors/flightgear/ftp/Win32/Setup% 20v20110629.exe% este lugar]


== Nuevos proyectos y herramientas de software ==
== Nuevos proyectos y herramientas de software ==
5,810

edits

Navigation menu