Mathias Fr??hlich wrote:
> I am currently reviewing our models and will provide a patch later this
> evening.
I'd be glad to 'maintain' a temporary PLIB package for FlightGear if
people welcome this effort but I don't want to cross anyone's plans,
Martin.
--
Unix _IS_ user friendly - it's jus
Martin,
If so, you might want to include some updated 3d models. For example the 737
is still flat shaded and the adf instrument is still ordered in in the wrong
direction in current cvs base package.
I am currently reviewing our models and will provide a patch later this
evening.
Greetin
Martin Spott wrote:
"Curtis L. Olson" wrote:
Update of /var/cvs/FlightGear-0.9/releases
In directory baron:/tmp/cvs-serv18174
Added Files:
FlightGear-0.9.6.tar.gz
Log Message:
Official source release for v0.9.6
I'm asking just to find out: Do we all agree that it makes much sense
to build
Selon Jon Stockill <[EMAIL PROTECTED]>:
> Martin Spott wrote:
> > Martin Spott wrote:
> >
> >
> >>I'm asking just to find out: Do we all agree that it makes much sense
> >>to build the upcoming binary releases with a "crease-patched" version
> >>of current PLIB CVS ?
> >
> >
> > Ahem, for this pur
Martin Spott wrote:
> I'm asking just to find out: Do we all agree that it makes much sense
> to build the upcoming binary releases with a "crease-patched" version
> of current PLIB CVS ?
Ahem, for this purpose I'll have put a patched version here within the
next couple of minutes that might serv
Martin Spott wrote:
Martin Spott wrote:
I'm asking just to find out: Do we all agree that it makes much sense
to build the upcoming binary releases with a "crease-patched" version
of current PLIB CVS ?
Ahem, for this purpose I'll have put a patched version here within the
next couple of minutes t
Martin Spott wrote:
"Curtis L. Olson" wrote:
Update of /var/cvs/FlightGear-0.9/releases
In directory baron:/tmp/cvs-serv18174
Added Files:
FlightGear-0.9.6.tar.gz
Log Message:
Official source release for v0.9.6
I'm asking just to find out: Do we all agree that it makes much sense
to build
Martin Spott wrote:
> "Curtis L. Olson" wrote:
> > Update of /var/cvs/FlightGear-0.9/releases
> > In directory baron:/tmp/cvs-serv18174
>
> > Added Files:
> > FlightGear-0.9.6.tar.gz
> > Log Message:
> > Official source release for v0.9.6
>
> I'm asking just to find out: Do we all agree th
"Curtis L. Olson" wrote:
> Update of /var/cvs/FlightGear-0.9/releases
> In directory baron:/tmp/cvs-serv18174
> Added Files:
> FlightGear-0.9.6.tar.gz
> Log Message:
> Official source release for v0.9.6
I'm asking just to find out: Do we all agree that it makes much sense
to build the up
David Megginson wrote:
> I agree with Curt. There are two basic strategies for releasing:
> 2. Release often, testing every release only lightly.
> I think that #2 works better for most cases
What he said.
One way of looking at it is this: The goal isn't to produce individual
releases with the g
Jim Wilson wrote:
David Megginson said:
I would support a 4-week code freeze before 1.0, however, and I do think
it's just about time for a 1.0.
We're close, maybe next release, but I think we need to get the
subsystem/initialization thing straightened out first. Fred's fix for the
tilemanager l
David Megginson said:
> Curtis L. Olson wrote:
>
> > The other thing to consider is everyone seems to have one more fix
> > they'd like to get in. If we waited for everyone to be happy, we
> > literally would never be able to have a release. At some point we have
> > to draw the line and shi
Curtis L. Olson wrote:
The other thing to consider is everyone seems to have one more fix
they'd like to get in. If we waited for everyone to be happy, we
literally would never be able to have a release. At some point we have
to draw the line and ship. The 0.9.4 release is simply the current
Martin Spott said:
> "Curtis L. Olson" wrote:
> > Update of /var/cvs/FlightGear-0.9/releases
> > In directory baron:/tmp/cvs-serv13253
>
> > Added Files:
> > FlightGear-0.9.4.tar.gz
> > Log Message:
> > Official 0.9.4 release.
>
> Oooops, I wonder if we ever get the chance to do real testin
Jon S Berndt wrote:
On Fri, 26 Mar 2004 17:28:12 -0600
"Curtis L. Olson" <[EMAIL PROTECTED]> wrote:
Martin Spott wrote:
Oooops, I wonder if we ever get the chance to do real testing before
a release. I'm very well aware that this is primarily Curt's project
I apologize if the schedule was a
On Fri, 26 Mar 2004 17:28:12 -0600
"Curtis L. Olson" <[EMAIL PROTECTED]> wrote:
Martin Spott wrote:
Oooops, I wonder if we ever get the chance to do real testing before
a release. I'm very well aware that this is primarily Curt's project
I apologize if the schedule was a bit compressed, but I
Martin Spott wrote:
Oooops, I wonder if we ever get the chance to do real testing before a
release. I'm very well aware that this is primarily Curt's project but
on the other hand these surprisingly short pre-release stages make it
very hard for peripheral efforts to keep up with the release proce
On Friday 26 March 2004 23:43, Erik Hofman wrote:
> Martin Spott wrote:
> > Oooops, I wonder if we ever get the chance to do real testing before a
> > release. I'm very well aware that this is primarily Curt's project but
> > on the other hand these surprisingly short pre-release stages make it
> >
On Friday 26 March 2004 23:35, Martin Spott wrote:
> "Curtis L. Olson" wrote:
> > Update of /var/cvs/FlightGear-0.9/releases
> > In directory baron:/tmp/cvs-serv13253
> >
> > Added Files:
> > FlightGear-0.9.4.tar.gz
> > Log Message:
> > Official 0.9.4 release.
>
> Oooops, I wonder if we ever ge
Martin Spott wrote:
Oooops, I wonder if we ever get the chance to do real testing before a
release. I'm very well aware that this is primarily Curt's project but
on the other hand these surprisingly short pre-release stages make it
very hard for peripheral efforts to keep up with the release proces
"Curtis L. Olson" wrote:
> Update of /var/cvs/FlightGear-0.9/releases
> In directory baron:/tmp/cvs-serv13253
> Added Files:
> FlightGear-0.9.4.tar.gz
> Log Message:
> Official 0.9.4 release.
Oooops, I wonder if we ever get the chance to do real testing before a
release. I'm very well awar
21 matches
Mail list logo
