Es/FlightGear Newsletter May 2011: Difference between revisions

Jump to navigation Jump to search

Es/FlightGear Newsletter May 2011 (view source)

Revision as of 19:20, 13 February 2012

142 bytes removed ,  13 February 2012
→‎New plan for a FlightGear release Nuevo plan para publicación de FlightGear
Line 8: Line 8:


=== New plan for a FlightGear release Nuevo plan para publicación de FlightGear ===
=== New plan for a FlightGear release Nuevo plan para publicación de FlightGear ===
Good news: finally, a new FlightGear release is planned again. We're aiming to release FlightGear '''2.4.0''' in mid August 2011.


Several people have now agreed to restart working on a new release and a new [[Release Plan|release plan]] for more regular releases has been prepared. We're now aiming to have two releases per year - one in mid February and one in mid August.
Several people have now agreed to restart working on a new release and a new [[Release Plan|release plan]] for more regular releases has been prepared. We're now aiming to have two releases per year - one in mid February and one in mid August.
Line 15: Line 14:
Buenas noticias: por fin, se planea una nueva versión de FlightGear. Tenemos el objetivo de publicar '''FlightGear 2.4.0'''a mediados de Agosto de 2011.
Buenas noticias: por fin, se planea una nueva versión de FlightGear. Tenemos el objetivo de publicar '''FlightGear 2.4.0'''a mediados de Agosto de 2011.


Varias personas han llegado a un acuerdo para reiniciar el trabajo en una nueva versión y una nueva [[Release Plan|release planplan de lanzamiento]], ha sido preparado para más lanzamientos regulares . Ahora tenemos el objetivo de sacar dos versiones por año, una a mediados de Febrero y una a mediados de Agosto.
Varias personas han llegado a un acuerdo para reiniciar el trabajo en una nueva versión y ha sido preparado un nuevo [[Release Plan|plan de lanzamiento]] para publicaciones más regulares. Ahora tenemos el objetivo de sacar dos versiones por año, una a mediados de Febrero y una a mediados de Agosto.


The current development branch will be used the base for a new release - which will be versioned as 2.4.0.
The current development branch will be used the base for a new release - which will be versioned as 2.4.0.
Original plans to release FlightGear 2.2.0 in February got stalled when a number of the developers involved became too busy/blocked with RL commitments. A 2.2.0 source branch had already been created, but has now been abandoned, since it hadn't been maintained for several months. FG2.2.0 will ''not'' be announced officially, and ''no'' installers/binaries/downloads will be prepared - though the last snapshot of 2.2.0 sources remains available in the source repository.
Original plans to release FlightGear 2.2.0 in February got stalled when a number of the developers involved became too busy/blocked with RL commitments. A 2.2.0 source branch had already been created, but has now been abandoned, since it hadn't been maintained for several months. FG2.2.0 will ''not'' be announced officially, and ''no'' installers/binaries/downloads will be prepared - though the last snapshot of 2.2.0 sources remains available in the source repository.


La rama de desarrollo actual se utilizará la base para una nueva versión - que será versionado como 2.4.0.
La rama de desarrollo actual se usará como base para la nueva publicación - que será versionada como 2.4.0.
Los planes originales para liberar FlightGear 2.2.0 en febrero quedó estancado cuando un número de los desarrolladores involucrados se convirtió en demasiado ocupado / bloqueado con los compromisos de RL. Una bifurcación de origen 2.2.0 ya se había creado, pero ahora se ha abandonado, ya que no se había mantenido durante varios meses. FG2.2.0 no'''' se anunció oficialmente, y'' no'' o instaladores binarios o descargas serán preparados -, aunque la última instantánea de las fuentes 2.2.0 sigue estando disponible en el repositorio de código fuente.
Los planes originales para liberar FlightGear 2.2.0 en Ffebrero quedó estancado cuando un número de los desarrolladores involucrados se convirtió en demasiado ocupado / bloqueado con los compromisos de RL. Una bifurcación de origen 2.2.0 ya se había creado, pero ahora se ha abandonado, ya que no se había mantenido durante varios meses. FG2.2.0 no'''' se anunció oficialmente, y'' no'' o instaladores binarios o descargas serán preparados -, aunque la última instantánea de las fuentes 2.2.0 sigue estando disponible en el repositorio de código fuente.


Preparations for the next release (FG 2.4.0) have already started. The release process will involve a phase of two months for beta testing, starting on June 17th. During this phase several release candidates (complete FlightGear installers) will be provided for testing. Our existing build automation (Hudson) has already been prepared to provide regular installers for Mac and Windows - as well as binaries for certain Linux distros. And of course - sources are available for any supported platform. Throughout this period, everyone is invited to test bug(-fixes) and report such things at [http://code.google.com/p/flightgear-bugs/ our bug tracker].
Preparations for the next release (FG 2.4.0) have already started. The release process will involve a phase of two months for beta testing, starting on June 17th. During this phase several release candidates (complete FlightGear installers) will be provided for testing. Our existing build automation (Hudson) has already been prepared to provide regular installers for Mac and Windows - as well as binaries for certain Linux distros. And of course - sources are available for any supported platform. Throughout this period, everyone is invited to test bug(-fixes) and report such things at [http://code.google.com/p/flightgear-bugs/ our bug tracker].
Aepcam
5,707

edits

Retrieved from "https://wiki.flightgear.org/Special:MobileDiff/41113"

Navigation menu