[prev in list] [next in list] [prev in thread] [next in thread]
List: flightgear-devel
Subject: Re: [Flightgear-devel] heads up: FlightGear release plan
From: Peter Morgan <pete () freeflightsim ! org>
Date: 2011-05-31 22:42:00
Message-ID: BANLkTi=EMGVdqBhiVwTgsYXHb64zKUx5Mw () mail ! gmail ! com
[Download RAW message or body]
[Attachment #2 (multipart/alternative)]
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 <flightgear@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 i=
n
> > 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=F6hlich, Thorste=
n
> Brehm
> >> and myself developed a strategy and a concept about how to kick out ne=
w
> >> 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 Ju=
ne
> 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
>
[Attachment #5 (text/html)]
we need to sit on this as<div><a \
href="http://2.2.freeflightsim.org">2.2.freeflightsim.org</a>.. We need a marketing \
plam somwhat.. I hope we stick to release \
schedule..</div><div><br></div><div><br><div class="gmail_quote"> On Tue, May 31, \
2011 at 10:15 PM, HB-GRAL <span dir="ltr"><<a \
href="mailto:flightgear@sablonier.ch">flightgear@sablonier.ch</a>></span> \
wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px \
#ccc solid;padding-left:1ex;"> Am 22.05.11 14:37, schrieb ThorstenB:<br>
<div><div></div><div class="h5">> Hi,<br>
><br>
> since there were no major objections to the release plan, we're<br>
> proceeding as proposed.<br>
><br>
> Current status:<br>
><br>
> * We've "officially grounded" the releases/2.2.0 git branches \
yesterday.<br> > The flightgear/simgear "releases/2.2.0" branches were \
merged back to<br> > "master" (not "next"! "master" \
always contains the latest release).<br> > However, as proposed, we won't \
invest any more time into 2.2.0, so<br> > there'll be no binaries on the \
download page, no updated aircraft<br> > downloads, no announcements, etc.<br>
><br>
> * git/next is bumped to version 2.3.0 now. Actually we should have done<br>
> so when we branched releases/2.2.0 in January. Remember. it's odd minor<br>
> versions for the developer version now (git/next), even minor numbers<br>
> for releases.<br>
><br>
> * Hudson is prepared for providing release binaries and installers<br>
> (thanks James!). Once we create a new release branch, Hudson should<br>
> start building the binaries/installers (see Hudson's \
"Windows-release",<br> > "Mac-release", \
"Linux-release" projects). As usual, these will be<br> > updated hourly. \
We'll also provide complete Win/Mac installers<br> > (including fgdata base \
package) regularly, maybe about weekly, so these<br> > can be used for wider beta \
testing. We can't include the base package in<br> > the _hourly_ installers \
though, due to bandwidth/size limits (almost<br> > 400MB for the fgdata base \
package).<br> ><br>
> * We also started assessing tracker issues (thanks Gijs!). Some were<br>
> already fixed in the last days. And it doesn't look too bad, few issues<br>
> are highly critical. However, there are some areas where we're missing<br>
> people, for example for some (new) FDM, and a number of ATI-graphics<br>
> issues. Have a look at the tracker:<br>
> <a href="http://code.google.com/p/flightgear-bugs/issues/list" \
target="_blank">http://code.google.com/p/flightgear-bugs/issues/list</a><br> ><br>
><br>
> Finally, as a reminder now:<br>
> Only 4 more weeks to 2.4.0 feature freeze, remember June 17th, when<br>
> we'll close sg+fg "next" branch, and (!) fgdata "master" \
for 4 weeks.<br> > Only bug fixes should be committed after June 17th.<br>
> releases/2.4.0 will be branched on July 17th, when the main developer<br>
> branches will be bumped to 2.5.0 and reopen for new features. Beta<br>
> testing for 2.4.0 will continue for another month after that, till<br>
> August 17th. But all this was already described in the release plan<br>
> <a href="http://wiki.flightgear.org/Release_Plan" \
target="_blank">http://wiki.flightgear.org/Release_Plan</a><br> ><br>
> cheers,<br>
> Thorsten<br>
><br>
> On Do, 2011-05-19 at 14:29 +0200, Torsten Dreyer wrote:<br>
>> Hi everybody,<br>
>><br>
>> during this year's LinuxTag, Martin Spott, Mathias Fröhlich, Thorsten \
Brehm<br> >> and myself developed a strategy and a concept about how to kick \
out new<br> >> releases of FlightGear on a regular schedule.<br>
>><br>
>> Please find our first draft here: <a \
href="http://wiki.flightgear.org/Release_Plan" \
target="_blank">http://wiki.flightgear.org/Release_Plan</a><br> >><br>
>> For the impatient reader, this is the abstract:<br>
>> We plan to have two releases per year, one in February, one in August. \
The<br> >> first scheduled release following this concept will be 2.4.0 in \
August this<br> >> year, 2.6.0 is scheduled for February 2012.<br>
>><br>
>> If no major objections arise, we will set the version number on the \
current<br> >> development stream to 2.3.0 and will call out a "feature \
freeze" on June 17th.<br> >><br>
>> Any comment and certainly any help for actually preparing the release is<br>
>> welcome.<br>
>><br>
>> Thanks, Torsten<br>
><br>
<br>
</div></div>Can you please update <a href="http://wiki.flightgear.org/Release_Plan" \
target="_blank">http://wiki.flightgear.org/Release_Plan</a> with this<br> very \
important information ? Something like a short description of<br> current state ?<br>
<br>
Thanks a lot, Yves<br>
<br>
------------------------------------------------------------------------------<br>
Simplify data backup and recovery for your virtual environment with vRanger.<br>
Installation's a snap, and flexible recovery options mean your data is safe,<br>
secure and there when you need it. Data protection magic?<br>
Nope - It's vRanger. Get your free trial download today.<br>
<a href="http://p.sf.net/sfu/quest-sfdev2dev" \
target="_blank">http://p.sf.net/sfu/quest-sfdev2dev</a><br> <div><div></div><div \
class="h5">_______________________________________________<br> Flightgear-devel \
mailing list<br> <a href="mailto:Flightgear-devel@lists.sourceforge.net">Flightgear-devel@lists.sourceforge.net</a><br>
<a href="https://lists.sourceforge.net/lists/listinfo/flightgear-devel" \
target="_blank">https://lists.sourceforge.net/lists/listinfo/flightgear-devel</a><br> \
</div></div></blockquote></div><br></div>
------------------------------------------------------------------------------
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
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic