Re: [Flightgear-devel] [PATCH] 3D Clouds update

[Durk Talsma]

Hi Stuart,

Unless somebody else beats me to it, I'll try to commit this patch this 
weekend.

Thanks for this fine contribution,

Cheers,
Durk


On Wednesday 30 September 2009 11:15:21 pm Stuart Buchanan wrote:
> Hi All,
>
> I've been doing some work to improve the 3D clouds.
>
> As well as a variety of bug fixes, improvements include:-
> - A new XML format
> - Texture indexing based on the position of the sprite in the cloud-mass,
> allowing more control over the texture set. - Improved fog and shading
> - Better sprite distribution
> - A more natural distribution of clouds, so no more obvious grids.
>
> Most of the improvements can be seen in the Cu and Ac cloud types, but the
> stratus clouds have been improved as well.
>
> A patch is available here:
> http://www.nanjika.co.uk/flightgear/clouds.tar.gz
>
> Once it is applied, I'll update the appropriate README documentation
> myself.
>
> Comments are welcome as always.
>
> -Stuart
>
>
>
>
>
> ---
>--- Come build with us! The BlackBerry® Developer Conference in SF, CA
> is the only developer event you need to attend this year. Jumpstart your
> developing skills, take BlackBerry mobile applications to market and stay
> ahead of the curve. Join us from November 9-12, 2009. Register now!
> http://p.sf.net/sfu/devconf
> ___
> Flightgear-devel mailing list
> Flightgear-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/flightgear-devel


--
Come build with us! The BlackBerry® Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay 
ahead of the curve. Join us from November 9-12, 2009. Register now!
http://p.sf.net/sfu/devconf
___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel

Re: [Flightgear-devel] [Simgear-cvslogs] CVS: source/simgear/misc strutils.cxx, 1.4, 1.5 strutils.hxx, 1.4, 1.5

[James Turner]

On 30 Sep 2009, at 20:15, Simon Hollier wrote:

> I don't think there's an STL function, but there is
> boost::to_lower(str) or even something like:
>
> for (unsigned i=0; i < str.length(); ++i) {
>str[i] = tolower(str[i]);
>  }

I already chatted to Tim about this, I'm going to switch to the boost  
version.

tolower/toupper() worry me.



--
Come build with us! The BlackBerry® Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay 
ahead of the curve. Join us from November 9-12, 2009. Register now!
http://p.sf.net/sfu/devconf
___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel

Re: [Flightgear-devel] bug tracking

[Tim Moore]

On 10/01/2009 12:13 AM, Vivian Meazza wrote:
> Curt wrote
> 
>  
> 
> ‘git implementations under windows run fine’ Who claims that? Not here
> they don’t. I get constant glitches with cloned repos hanging – not only
> do they hang, but I can find no way out of the situation. I’m really
> p*ssed off with git right now. I’m in the anything but git camp today!
> 
Further investigation points to user error and maybe some tortoise git problems.
However, the local git expert has to go to sleep now...

Tim

--
Come build with us! The BlackBerry® Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay 
ahead of the curve. Join us from November 9-12, 2009. Register now!
http://p.sf.net/sfu/devconf
___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel

Re: [Flightgear-devel] bug tracking

[Vivian Meazza]

Curt wrote

 

'git implementations under windows run fine' Who claims that? Not here they
don't. I get constant glitches with cloned repos hanging - not only do they
hang, but I can find no way out of the situation. I'm really p*ssed off with
git right now. I'm in the anything but git camp today! 

 

Vivian

 

-Original Message-
From: Curtis Olson [mailto:curtol...@gmail.com] 
Sent: 30 September 2009 18:59
To: FlightGear developers discussions
Subject: Re: [Flightgear-devel] bug tracking

 

On Wed, Sep 30, 2009 at 12:47 PM, Gijs de Rooy  wrote:

Hi,



> Curtis Olson wrote:
>
> Why not use the bug tracker at code.google.com/p/flightgear?  
 

Is it just me or does that project not exist? The link gives an error page
and the project
does not show up when searching for FlightGear on Google Code. The simgear
one does 
exist...


Ok, well the one that will eventually exist there ... :-)

(except we cannot collectively agree on the best source code control system
to move towards.  Svn in better than cvs; cvs is better than svn, git
implementations are dodgy under windows, git implementations under windows
run fine, hg is a lean mean fighting machine, except google's implementation
or servers currently has some sort of issues with the linux hg client or
maybe visa versa; anything is better than cvs; don't transition to svn
because once the cvs 'crisis' is averted then there's no further motiviation
to go any further.  the project has a lot of git experience, the project has
a lot of svn experience, the project has a lot of cvs experienece, the
project doesn't have much hg experience; every one can register a project
name at their favorite hosting service, everyone can setup their own local
repostory clone using their favorite tool; but some developers have argued
this *very* passionately implying perhaps that there will be a huge
firestorm following up any bad or incorrect decisions for how to move
foward; we have set up a sequence of constraints that gives us no option to
do anything.)

Regards,

Curt. 

-- 
Curtis Olson: http://baron.flightgear.org/~curt/

--
Come build with us! The BlackBerry® Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay 
ahead of the curve. Join us from November 9-12, 2009. Register now!
http://p.sf.net/sfu/devconf___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel

Re: [Flightgear-devel] FlightGear September Newsletter now available

[Curtis Olson]

Hi Stuart,

Thanks for keeping on top of the news letter.  It is definitely
appreciated!  I like that you've kept it simple and concise.

Thanks!

Curt.


On Wed, Sep 30, 2009 at 4:09 PM, Stuart Buchanan <
stuart_d_bucha...@yahoo.co.uk> wrote:

> Hi All,
>
> The September edition of The FlightGear Newsletter is now available:
>
> http://wiki.flightgear.org/index.php/FlightGear_Newsletter_September_2009
>
> As always, we're looking for contributions to the next edition, so if
> you've done something interesting with FlightGear, please write up a couple
> of paragraphs for the next edition.
>
> Thanks,
>
> -Stuart
>
>
>
>
>
>
> --
> Come build with us! The BlackBerry® Developer Conference in SF, CA
> is the only developer event you need to attend this year. Jumpstart your
> developing skills, take BlackBerry mobile applications to market and stay
> ahead of the curve. Join us from November 9-12, 2009. Register now!
> http://p.sf.net/sfu/devconf
> ___
> Flightgear-devel mailing list
> Flightgear-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/flightgear-devel
>



-- 
Curtis Olson: http://baron.flightgear.org/~curt/
--
Come build with us! The BlackBerry® Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay 
ahead of the curve. Join us from November 9-12, 2009. Register now!
http://p.sf.net/sfu/devconf___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel

[Flightgear-devel] [PATCH] 3D Clouds update

[Stuart Buchanan]

Hi All,

I've been doing some work to improve the 3D clouds.

As well as a variety of bug fixes, improvements include:-
- A new XML format
- Texture indexing based on the position of the sprite in the cloud-mass, 
allowing more control over the texture set.
- Improved fog and shading
- Better sprite distribution
- A more natural distribution of clouds, so no more obvious grids.

Most of the improvements can be seen in the Cu and Ac cloud types, but the 
stratus clouds have been improved as well.

A patch is available here: http://www.nanjika.co.uk/flightgear/clouds.tar.gz

Once it is applied, I'll update the appropriate README documentation myself.

Comments are welcome as always.

-Stuart



  

--
Come build with us! The BlackBerry® Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay 
ahead of the curve. Join us from November 9-12, 2009. Register now!
http://p.sf.net/sfu/devconf
___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel

[Flightgear-devel] FlightGear September Newsletter now available

[Stuart Buchanan]

Hi All,

The September edition of The FlightGear Newsletter is now available:

http://wiki.flightgear.org/index.php/FlightGear_Newsletter_September_2009

As always, we're looking for contributions to the next edition, so if you've 
done something interesting with FlightGear, please write up a couple of 
paragraphs for the next edition.

Thanks,

-Stuart



  

--
Come build with us! The BlackBerry® Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay 
ahead of the curve. Join us from November 9-12, 2009. Register now!
http://p.sf.net/sfu/devconf
___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel

Re: [Flightgear-devel] [Simgear-cvslogs] CVS: source/simgear/misc strutils.cxx, 1.4, 1.5 strutils.hxx, 1.4, 1.5

[Simon Hollier]

Hello,

On Wed, Sep 30, 2009 at 2:47 PM, Curtis Olson  wrote:
> Ok, duh! I see that is a single character function, but there has to be a
>  class function or it can't be too hard to whip up a little function
> ourselves.

I don't think there's an STL function, but there is
boost::to_lower(str) or even something like:

for (unsigned i=0; i < str.length(); ++i) {
str[i] = tolower(str[i]);
  }



-- 
Simon Hollier

--
Come build with us! The BlackBerry® Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay 
ahead of the curve. Join us from November 9-12, 2009. Register now!
http://p.sf.net/sfu/devconf
___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel

Re: [Flightgear-devel] [Simgear-cvslogs] CVS: source/simgear/misc strutils.cxx, 1.4, 1.5 strutils.hxx, 1.4, 1.5

[Curtis Olson]

Ok, duh! I see that is a single character function, but there has to be a
 class function or it can't be too hard to whip up a little function
ourselves.

Thanks,

Curt.


On Wed, Sep 30, 2009 at 1:44 PM, Curtis Olson wrote:

> Hi Jim,
>
> I just noticed you added an OSG dependency to strutils.cxx/hxx  If possible
> it would be nice to avoid adding graphics system dependencies to these text
> manipulation libraries.  SimGear and SimGear code is used in a variety of
> places beyond FlightGear, even in embedded systems where compiling opengl
> and OSG is completely impossible.
>
> Would it work to use something like the following instead of an OSG
> function?:
>
>   #include 
>
>int toupper(int c);
>int tolower(int c);
>
> Right now this OSG dependency is breaking one of my other projects.
>
> Thanks,
>
> Curt.
>
>
>
>
> On Sat, Sep 26, 2009 at 6:44 AM, James Turner 
> wrote:
>
>> Update of /var/cvs/SimGear-0.3/source/simgear/misc
>> In directory baron.flightgear.org:/tmp/cvs-serv8677/simgear/misc
>>
>> Modified Files:
>>strutils.cxx strutils.hxx
>> Log Message:
>> Extend simgear::strutils with convertToLowerCase helper - currently a
>> proxy for osgDB helper of the same name.
>>
>>
>> Index: strutils.cxx
>> ===
>> RCS file: /var/cvs/SimGear-0.3/source/simgear/misc/strutils.cxx,v
>> retrieving revision 1.4
>> retrieving revision 1.5
>> diff -u -r1.4 -r1.5
>> --- strutils.cxx13 Apr 2008 21:11:44 -  1.4
>> +++ strutils.cxx26 Sep 2009 11:44:33 -  1.5
>> @@ -25,6 +25,11 @@
>>
>>  #include "strutils.hxx"
>>
>> +#include  // for convertToLowerCase
>> +
>> +using std::string;
>> +using std::vector;
>> +
>>  namespace simgear {
>> namespace strutils {
>>
>> @@ -180,5 +185,12 @@
>>return do_strip( s, BOTHSTRIP );
>>}
>>
>> +  string convertToLowerCase(const string& str)
>> +  {
>> +// proxy onto osgDB - easy to reimplement here, but let's avoid
>> +// code duplication for the moment.
>> +return osgDB::convertToLowerCase(str);
>> +  }
>> +
>> } // end namespace strutils
>>  } // end namespace simgear
>>
>> Index: strutils.hxx
>> ===
>> RCS file: /var/cvs/SimGear-0.3/source/simgear/misc/strutils.hxx,v
>> retrieving revision 1.4
>> retrieving revision 1.5
>> diff -u -r1.4 -r1.5
>> --- strutils.hxx28 Jul 2008 07:52:14 -  1.4
>> +++ strutils.hxx26 Sep 2009 11:44:34 -  1.5
>> @@ -30,16 +30,12 @@
>>  #include 
>>
>>  #include 
>> -
>>  #include 
>> -using std::vector;
>> -
>>  #include 
>>
>> -using std::string;
>>
>>  namespace simgear {
>> -namespace strutils {
>> +  namespace strutils {
>>
>>  // /**
>>  //  * atof() wrapper for "string" type
>> @@ -64,9 +60,9 @@
>> * @param s String to strip.
>> * @return The stripped string.
>> */
>> -   string lstrip( const string& s );
>> -   string rstrip( const string& s );
>> -   string strip( const string& s );
>> +   std::string lstrip( const std::string& s );
>> +   std::string rstrip( const std::string& s );
>> +   std::string strip( const std::string& s );
>>
>>/**
>> * Split a string into a words using 'sep' as the delimiter string.
>> @@ -79,12 +75,15 @@
>> * resulting in at most maxsplit+1 words.
>> * @return Array of words.
>> */
>> -   vector
>> -   split( const string& s,
>> +   std::vector
>> +   split( const std::string& s,
>>   const char* sep = 0,
>>   int maxsplit = 0 );
>>
>> -} // end namespace strutils
>> +
>> +  std::string convertToLowerCase(const std::string& str);
>> +
>> +  } // end namespace strutils
>>  } // end namespace simgear
>>
>>  #endif // STRUTILS_H
>>
>>
>>
>> --
>> Come build with us! The BlackBerry® Developer Conference in SF, CA
>> is the only developer event you need to attend this year. Jumpstart your
>> developing skills, take BlackBerry mobile applications to market and stay
>> ahead of the curve. Join us from November 9-12, 2009. Register
>> now!
>> http://p.sf.net/sfu/devconf
>> ___
>> Simgear-cvslogs mailing list
>> simgear-cvsl...@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/simgear-cvslogs
>>
>
>
>
> --
> Curtis Olson: 
> http://baron.flightgear.org/~curt/
>



-- 
Curtis Olson: http://baron.flightgear.org/~curt/
--
Come build with us! The BlackBerry® Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay 
ahead of the curve. Join us from November 9-12, 2009. Regi

Re: [Flightgear-devel] [Simgear-cvslogs] CVS: source/simgear/misc strutils.cxx, 1.4, 1.5 strutils.hxx, 1.4, 1.5

[Curtis Olson]

Hi Jim,

I just noticed you added an OSG dependency to strutils.cxx/hxx  If possible
it would be nice to avoid adding graphics system dependencies to these text
manipulation libraries.  SimGear and SimGear code is used in a variety of
places beyond FlightGear, even in embedded systems where compiling opengl
and OSG is completely impossible.

Would it work to use something like the following instead of an OSG
function?:

  #include 

   int toupper(int c);
   int tolower(int c);

Right now this OSG dependency is breaking one of my other projects.

Thanks,

Curt.



On Sat, Sep 26, 2009 at 6:44 AM, James Turner wrote:

> Update of /var/cvs/SimGear-0.3/source/simgear/misc
> In directory baron.flightgear.org:/tmp/cvs-serv8677/simgear/misc
>
> Modified Files:
>strutils.cxx strutils.hxx
> Log Message:
> Extend simgear::strutils with convertToLowerCase helper - currently a proxy
> for osgDB helper of the same name.
>
>
> Index: strutils.cxx
> ===
> RCS file: /var/cvs/SimGear-0.3/source/simgear/misc/strutils.cxx,v
> retrieving revision 1.4
> retrieving revision 1.5
> diff -u -r1.4 -r1.5
> --- strutils.cxx13 Apr 2008 21:11:44 -  1.4
> +++ strutils.cxx26 Sep 2009 11:44:33 -  1.5
> @@ -25,6 +25,11 @@
>
>  #include "strutils.hxx"
>
> +#include  // for convertToLowerCase
> +
> +using std::string;
> +using std::vector;
> +
>  namespace simgear {
> namespace strutils {
>
> @@ -180,5 +185,12 @@
>return do_strip( s, BOTHSTRIP );
>}
>
> +  string convertToLowerCase(const string& str)
> +  {
> +// proxy onto osgDB - easy to reimplement here, but let's avoid
> +// code duplication for the moment.
> +return osgDB::convertToLowerCase(str);
> +  }
> +
> } // end namespace strutils
>  } // end namespace simgear
>
> Index: strutils.hxx
> ===
> RCS file: /var/cvs/SimGear-0.3/source/simgear/misc/strutils.hxx,v
> retrieving revision 1.4
> retrieving revision 1.5
> diff -u -r1.4 -r1.5
> --- strutils.hxx28 Jul 2008 07:52:14 -  1.4
> +++ strutils.hxx26 Sep 2009 11:44:34 -  1.5
> @@ -30,16 +30,12 @@
>  #include 
>
>  #include 
> -
>  #include 
> -using std::vector;
> -
>  #include 
>
> -using std::string;
>
>  namespace simgear {
> -namespace strutils {
> +  namespace strutils {
>
>  // /**
>  //  * atof() wrapper for "string" type
> @@ -64,9 +60,9 @@
> * @param s String to strip.
> * @return The stripped string.
> */
> -   string lstrip( const string& s );
> -   string rstrip( const string& s );
> -   string strip( const string& s );
> +   std::string lstrip( const std::string& s );
> +   std::string rstrip( const std::string& s );
> +   std::string strip( const std::string& s );
>
>/**
> * Split a string into a words using 'sep' as the delimiter string.
> @@ -79,12 +75,15 @@
> * resulting in at most maxsplit+1 words.
> * @return Array of words.
> */
> -   vector
> -   split( const string& s,
> +   std::vector
> +   split( const std::string& s,
>   const char* sep = 0,
>   int maxsplit = 0 );
>
> -} // end namespace strutils
> +
> +  std::string convertToLowerCase(const std::string& str);
> +
> +  } // end namespace strutils
>  } // end namespace simgear
>
>  #endif // STRUTILS_H
>
>
>
> --
> Come build with us! The BlackBerry® Developer Conference in SF, CA
> is the only developer event you need to attend this year. Jumpstart your
> developing skills, take BlackBerry mobile applications to market and stay
> ahead of the curve. Join us from November 9-12, 2009. Register now!
> http://p.sf.net/sfu/devconf
> ___
> Simgear-cvslogs mailing list
> simgear-cvsl...@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/simgear-cvslogs
>



-- 
Curtis Olson: http://baron.flightgear.org/~curt/
--
Come build with us! The BlackBerry® Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay 
ahead of the curve. Join us from November 9-12, 2009. Register now!
http://p.sf.net/sfu/devconf___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel

Re: [Flightgear-devel] Source code control systems

[Pete Morgan]

So what would the "source  tree" look like to you as a developer and pilot
eg
hanger/boeing/**



Pablo Rogina wrote:
> Pete Morgan wrote:
>
> > I do like the way qt uses it with merge requests. a lot of them to do
> > with documentation corrections, as well as minor touches to code.
>
> I was following this thread since I'm interested about opinions and 
> thoughts about version control systems, from a software engineering 
> perspective.
>
> I don't know why it's really taking so long to make a decision about 
> the tool to use (name it: git, hg, svn, etc.). I do personally prefer 
> git and the DVCS proposed by it.
>
> And I would choose gitorious as the repository for that. Could Nokia 
> be so terribly wrong to trust one of its latest adquisitions, Qt 
> source code, to that repository without having thought it very carefully?
> And yes, they have set up a very good contribution scheme through the 
> merge requests.
>
> So at this point I cannot understand why FlightGear proyect could be 
> sooo different from Qt, which have several full time developers making 
> lots of changes, additions and so on, plus lots of contributions from 
> external resources. And everything is fine resting on git and gitorious.
>
> Regarding svn externals, that is a great thing from SVN and, even if I 
> didn't use it so far, it seems that svn externals can be mimic in git 
> by means of git's submodules
>
> http://panthersoftware.com/articles/view/3/svn-s-svn-externals-to-git-s-submodule-for-rails-plugins
>
> Just my 2 cents...
>
> Pablo
> 
>
> --
> Come build with us! The BlackBerry® Developer Conference in SF, CA
> is the only developer event you need to attend this year. Jumpstart your
> developing skills, take BlackBerry mobile applications to market and stay 
> ahead of the curve. Join us from November 9-12, 2009. Register now!
> http://p.sf.net/sfu/devconf
> 
>
> ___
> Flightgear-devel mailing list
> Flightgear-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/flightgear-devel
>   


--
Come build with us! The BlackBerry® Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay 
ahead of the curve. Join us from November 9-12, 2009. Register now!
http://p.sf.net/sfu/devconf
___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel

Re: [Flightgear-devel] bug tracking

[Pete Morgan]

Curtis..

Thou needs to rise up and command the people.

Please dictate where we can file bugs first..





--
Come build with us! The BlackBerry® Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay 
ahead of the curve. Join us from November 9-12, 2009. Register now!
http://p.sf.net/sfu/devconf
___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel

Re: [Flightgear-devel] bug tracking

[Curtis Olson]

On Wed, Sep 30, 2009 at 12:47 PM, Gijs de Rooy  wrote:

>  Hi,
>
> > Curtis Olson wrote:
> >
> > Why not use the bug tracker at code.google.com/p/flightgear?
>
> Is it just me or does that project not exist? The link gives an error page
> and the project
> does not show up when searching for FlightGear on Google Code. The simgear
> one does
> exist...
>

Ok, well the one that will eventually exist there ... :-)

(except we cannot collectively agree on the best source code control system
to move towards.  Svn in better than cvs; cvs is better than svn, git
implementations are dodgy under windows, git implementations under windows
run fine, hg is a lean mean fighting machine, except google's implementation
or servers currently has some sort of issues with the linux hg client or
maybe visa versa; anything is better than cvs; don't transition to svn
because once the cvs 'crisis' is averted then there's no further motiviation
to go any further.  the project has a lot of git experience, the project has
a lot of svn experience, the project has a lot of cvs experienece, the
project doesn't have much hg experience; every one can register a project
name at their favorite hosting service, everyone can setup their own local
repostory clone using their favorite tool; but some developers have argued
this *very* passionately implying perhaps that there will be a huge
firestorm following up any bad or incorrect decisions for how to move
foward; we have set up a sequence of constraints that gives us no option to
do anything.)

Regards,

Curt.
-- 
Curtis Olson: http://baron.flightgear.org/~curt/
--
Come build with us! The BlackBerry® Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay 
ahead of the curve. Join us from November 9-12, 2009. Register now!
http://p.sf.net/sfu/devconf___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel

Re: [Flightgear-devel] Source code control systems

[Pablo Rogina]

Pete Morgan wrote:

> I do like the way qt uses it with merge requests. a lot of them to do
> with documentation corrections, as well as minor touches to code.

I was following this thread since I'm interested about opinions and thoughts
about version control systems, from a software engineering perspective.

I don't know why it's really taking so long to make a decision about the
tool to use (name it: git, hg, svn, etc.). I do personally prefer git and
the DVCS proposed by it.

And I would choose gitorious as the repository for that. Could Nokia be so
terribly wrong to trust one of its latest adquisitions, Qt source code, to
that repository without having thought it very carefully?
And yes, they have set up a very good contribution scheme through the merge
requests.

So at this point I cannot understand why FlightGear proyect could be sooo
different from Qt, which have several full time developers making lots of
changes, additions and so on, plus lots of contributions from external
resources. And everything is fine resting on git and gitorious.

Regarding svn externals, that is a great thing from SVN and, even if I
didn't use it so far, it seems that svn externals can be mimic in git by
means of git's submodules

http://panthersoftware.com/articles/view/3/svn-s-svn-externals-to-git-s-submodule-for-rails-plugins

Just my 2 cents...

Pablo
--
Come build with us! The BlackBerry® Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay 
ahead of the curve. Join us from November 9-12, 2009. Register now!
http://p.sf.net/sfu/devconf___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel

Re: [Flightgear-devel] bug tracking

[Pete Morgan]

same here ?


Gijs de Rooy wrote:
> Hi,
>
> > Curtis Olson wrote:
> >
> > Why not use the bug tracker at code.google.com/p/flightgear 
> ? 
>  
> Is it just me or does that project not exist? The link gives an error 
> page and the project
> does not show up when searching for FlightGear on Google Code. The 
> simgear one does
> exist...
>
> Cheers,
> Gijs
>
> 
> Plan je party en pimp je uitnodigingen met Windows Live Events 
> 
>  
>
> 
>
> --
> Come build with us! The BlackBerry® Developer Conference in SF, CA
> is the only developer event you need to attend this year. Jumpstart your
> developing skills, take BlackBerry mobile applications to market and stay 
> ahead of the curve. Join us from November 9-12, 2009. Register now!
> http://p.sf.net/sfu/devconf
> 
>
> ___
> Flightgear-devel mailing list
> Flightgear-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/flightgear-devel
>   


--
Come build with us! The BlackBerry® Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay 
ahead of the curve. Join us from November 9-12, 2009. Register now!
http://p.sf.net/sfu/devconf
___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel

Re: [Flightgear-devel] bug tracking

[Pete Morgan]

code.google.com/p/flightgea r = 404 ???

I am interested in the bug tracking bit Will make life easier for all -)

Pete
Krash handler
FG.uk PLC



Curtis Olson wrote:
> I'm just not sure how productive it is to register yet another 
> separate google project simply to use the bug tracker.  Why not use 
> the bug tracker at code.google.com/p/flightgear 
> ?  I've been holding off pushing 
> any particular bug tracking system, because it really makes a lot of 
> sense to co-locate the bug tracking system with the code.
>
> Regards,
>
> Curt.
>
>
> On Wed, Sep 30, 2009 at 12:18 PM, Pete Morgan  > wrote:
>
>
> Precisley the problem is that me as  amuppet doth not know where the
> issue ie at, and where to report.
>
> So at least if we can point users to a particular point, then they can
> be filtered and sorted.
>
> therby dipatched to the concerned.
>
> At the moment its real crap.. so at least I want to use google
> issues as
> a common complaints dept, for delegation
>
> pete
>
> Curtis Olson wrote:
> >
> >
> > On Wed, Sep 30, 2009 at 11:58 AM, Pete Morgan
> mailto:ac...@daffodil.uk.com>
> > >>
> wrote:
> >
> > Curtis Olson wrote:
> > > I agree that a bug tracking system is a good thing.  My
> thoughts &
> > > hopes are that once we finalized what we were doing with our
> > eventual
> > > move away from CVS,  We would move our code to a system that
> > offers a
> > > number of developer features including an integrated bug
> tracker.
> > > Google does offer a nice system, but long term, it would
> be nice to
> > > just use the bug tracker associated with our project,
> rather than
> > > setup a completely new project and only use the bug
> tracker out
> > of it.
> > >
> > > Curt.
> > >
> > for me as an intermediate user, If there is a facility to report
> > bugs ie
> > PIEPR's then that would be cool.
> >
> > So at the moment This site is for identifying bugs only.. No
> less or
> > more. It will be seperate atmo from source..
> >
> > However recognising the bugs is THE issue.
> >
> > eg one of the  three paths
> > 1) dont set up a bug tracker and ignoire them
> > 2) Have a bug tracker and then ignore them
> > 3) Have an active bug tracer and identify problem area and
> resolve
> > issue..
> >
> > 4) Send a report to the developers that there is a bug u
> need to fix..
> >
> > Curtis .. please endorse and go for this bucktracker
> please.. At least
> > that way we can all complain until we sort it.. ;-)
> >
> > this way it will be a steady eddie ;-)
> > the SCM is another issue
> >
> >
> > I'd be more inclined to use the bug trackers at
> > http://code.google.com/p/simgear and
> > http://code.google.com/p/flightgear but those sites are
> currently tied
> > up with svn versus git versus hg discussions.
> >
> > Personally I think it could turn into a mess if we fill up this new
> > site with a bunch of bug reports and then have no way to move
> them to
> > the official site(s) later.  We also have bug trackers available at
> > our sourceforge registered projects.  I always felt the sourceforge
> > bug tracker was kind of slow and clunky.  The google bug tracker
> seems
> > much nicer, and it appears it is integrated with the repository
> so you
> > can reference specific patches or branches.  That would be harder to
> > do if the bug tracker lived at a completely separate project
> name.  We
> > lose much of the cool functionality that google offers.
> >
> > Regards,
> >
> > Curt.
> > --
> > Curtis Olson: http://baron.flightgear.org/~curt/
> 
> > 
> >
> 
> >
> >
> 
> --
> > Come build with us! The BlackBerry® Developer Conference in
> SF, CA
> > is the only developer event you need to attend this year.
> Jumpstart your
> > developing skills, take BlackBerry mobile applications to market
> and stay
> > ahead of the curve. Join us from November 9-12, 2009.
> Register now!
> > http://p.sf.net/sfu/devconf
> >
> 
> >
> > ___
> > Flightgear-devel mailing list
> > Flig

Re: [Flightgear-devel] bug tracking

[Gijs de Rooy]

Hi,

> Curtis Olson wrote:

>

> Why not use the bug tracker at code.google.com/p/flightgear?  

 

Is it just me or does that project not exist? The link gives an error page and 
the project
does not show up when searching for FlightGear on Google Code. The simgear one 
does 
exist...

Cheers,

Gijs
  
_
Krijg updates van je vrienden en blijf op de hoogte
http://home.live.com--
Come build with us! The BlackBerry® Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay 
ahead of the curve. Join us from November 9-12, 2009. Register now!
http://p.sf.net/sfu/devconf___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel

Re: [Flightgear-devel] bug tracking

[Curtis Olson]

I'm just not sure how productive it is to register yet another separate
google project simply to use the bug tracker.  Why not use the bug tracker
at code.google.com/p/flightgear?  I've been holding off pushing any
particular bug tracking system, because it really makes a lot of sense to
co-locate the bug tracking system with the code.

Regards,

Curt.


On Wed, Sep 30, 2009 at 12:18 PM, Pete Morgan  wrote:

>
> Precisley the problem is that me as  amuppet doth not know where the
> issue ie at, and where to report.
>
> So at least if we can point users to a particular point, then they can
> be filtered and sorted.
>
> therby dipatched to the concerned.
>
> At the moment its real crap.. so at least I want to use google issues as
> a common complaints dept, for delegation
>
> pete
>
> Curtis Olson wrote:
> >
> >
> > On Wed, Sep 30, 2009 at 11:58 AM, Pete Morgan  > > wrote:
> >
> > Curtis Olson wrote:
> > > I agree that a bug tracking system is a good thing.  My thoughts &
> > > hopes are that once we finalized what we were doing with our
> > eventual
> > > move away from CVS,  We would move our code to a system that
> > offers a
> > > number of developer features including an integrated bug tracker.
> > > Google does offer a nice system, but long term, it would be nice to
> > > just use the bug tracker associated with our project, rather than
> > > setup a completely new project and only use the bug tracker out
> > of it.
> > >
> > > Curt.
> > >
> > for me as an intermediate user, If there is a facility to report
> > bugs ie
> > PIEPR's then that would be cool.
> >
> > So at the moment This site is for identifying bugs only.. No less or
> > more. It will be seperate atmo from source..
> >
> > However recognising the bugs is THE issue.
> >
> > eg one of the  three paths
> > 1) dont set up a bug tracker and ignoire them
> > 2) Have a bug tracker and then ignore them
> > 3) Have an active bug tracer and identify problem area and resolve
> > issue..
> >
> > 4) Send a report to the developers that there is a bug u need to
> fix..
> >
> > Curtis .. please endorse and go for this bucktracker please.. At
> least
> > that way we can all complain until we sort it.. ;-)
> >
> > this way it will be a steady eddie ;-)
> > the SCM is another issue
> >
> >
> > I'd be more inclined to use the bug trackers at
> > http://code.google.com/p/simgear and
> > http://code.google.com/p/flightgear but those sites are currently tied
> > up with svn versus git versus hg discussions.
> >
> > Personally I think it could turn into a mess if we fill up this new
> > site with a bunch of bug reports and then have no way to move them to
> > the official site(s) later.  We also have bug trackers available at
> > our sourceforge registered projects.  I always felt the sourceforge
> > bug tracker was kind of slow and clunky.  The google bug tracker seems
> > much nicer, and it appears it is integrated with the repository so you
> > can reference specific patches or branches.  That would be harder to
> > do if the bug tracker lived at a completely separate project name.  We
> > lose much of the cool functionality that google offers.
> >
> > Regards,
> >
> > Curt.
> > --
> > Curtis Olson: 
> > http://baron.flightgear.org/~curt/
> > 
> > 
> >
> >
> --
> > Come build with us! The BlackBerry® Developer Conference in SF, CA
> > is the only developer event you need to attend this year. Jumpstart your
> > developing skills, take BlackBerry mobile applications to market and stay
> > ahead of the curve. Join us from November 9-12, 2009. Register
> now!
> > http://p.sf.net/sfu/devconf
> > 
> >
> > ___
> > Flightgear-devel mailing list
> > Flightgear-devel@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/flightgear-devel
> >
>
>
>
> --
> Come build with us! The BlackBerry® Developer Conference in SF, CA
> is the only developer event you need to attend this year. Jumpstart your
> developing skills, take BlackBerry mobile applications to market and stay
> ahead of the curve. Join us from November 9-12, 2009. Register now!
> http://p.sf.net/sfu/devconf
> ___
> Flightgear-devel mailing list
> Flightgear-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/flightgear-devel
>



-- 
Curtis Olson: http://baron.flightgear.org/~curt/
--
Come build wi

[Flightgear-devel] Bug Tracking != Source code

[Pete Morgan]

Source code != bug tracking..



--
Come build with us! The BlackBerry® Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay 
ahead of the curve. Join us from November 9-12, 2009. Register now!
http://p.sf.net/sfu/devconf
___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel

Re: [Flightgear-devel] bug tracking

[Pete Morgan]

Precisley the problem is that me as  amuppet doth not know where the 
issue ie at, and where to report.

So at least if we can point users to a particular point, then they can 
be filtered and sorted.

therby dipatched to the concerned.

At the moment its real crap.. so at least I want to use google issues as 
a common complaints dept, for delegation

pete

Curtis Olson wrote:
>
>
> On Wed, Sep 30, 2009 at 11:58 AM, Pete Morgan  > wrote:
>
> Curtis Olson wrote:
> > I agree that a bug tracking system is a good thing.  My thoughts &
> > hopes are that once we finalized what we were doing with our
> eventual
> > move away from CVS,  We would move our code to a system that
> offers a
> > number of developer features including an integrated bug tracker.
> > Google does offer a nice system, but long term, it would be nice to
> > just use the bug tracker associated with our project, rather than
> > setup a completely new project and only use the bug tracker out
> of it.
> >
> > Curt.
> >
> for me as an intermediate user, If there is a facility to report
> bugs ie
> PIEPR's then that would be cool.
>
> So at the moment This site is for identifying bugs only.. No less or
> more. It will be seperate atmo from source..
>
> However recognising the bugs is THE issue.
>
> eg one of the  three paths
> 1) dont set up a bug tracker and ignoire them
> 2) Have a bug tracker and then ignore them
> 3) Have an active bug tracer and identify problem area and resolve
> issue..
>
> 4) Send a report to the developers that there is a bug u need to fix..
>
> Curtis .. please endorse and go for this bucktracker please.. At least
> that way we can all complain until we sort it.. ;-)
>
> this way it will be a steady eddie ;-)
> the SCM is another issue
>
>
> I'd be more inclined to use the bug trackers at 
> http://code.google.com/p/simgear and 
> http://code.google.com/p/flightgear but those sites are currently tied 
> up with svn versus git versus hg discussions.
>
> Personally I think it could turn into a mess if we fill up this new 
> site with a bunch of bug reports and then have no way to move them to 
> the official site(s) later.  We also have bug trackers available at 
> our sourceforge registered projects.  I always felt the sourceforge 
> bug tracker was kind of slow and clunky.  The google bug tracker seems 
> much nicer, and it appears it is integrated with the repository so you 
> can reference specific patches or branches.  That would be harder to 
> do if the bug tracker lived at a completely separate project name.  We 
> lose much of the cool functionality that google offers.
>
> Regards,
>
> Curt.
> -- 
> Curtis Olson: http://baron.flightgear.org/~curt/ 
> 
> 
>
> --
> Come build with us! The BlackBerry® Developer Conference in SF, CA
> is the only developer event you need to attend this year. Jumpstart your
> developing skills, take BlackBerry mobile applications to market and stay 
> ahead of the curve. Join us from November 9-12, 2009. Register now!
> http://p.sf.net/sfu/devconf
> 
>
> ___
> Flightgear-devel mailing list
> Flightgear-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/flightgear-devel
>   


--
Come build with us! The BlackBerry® Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay 
ahead of the curve. Join us from November 9-12, 2009. Register now!
http://p.sf.net/sfu/devconf
___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel

Re: [Flightgear-devel] bug tracking

[Pete Morgan]

Gorilla thanks. U kinda exlained what's needed..

My vision it to "filter" the results and then have a direction of things 
to fix from user reports...

Users are our best friends.. who can complain to their hearts content..


The issue now is that we need to "register" and recongise all the 
failures, so they can be identified and fixed..

I love the idea of 2 weeks.. as that is a recognision of problem and 
solution...

Only thing is that whats REALYY important is the /data/ and this even in 
git yet anywhere. ??

The bug reports ie cusomter satisfaction and
FDS so not mix,
they are two seperate mixtures...

pete


George Patterson wrote:
> On Thu, Oct 1, 2009 at 2:25 AM, Curtis Olson  wrote:
>   
>> I agree that a bug tracking system is a good thing.  My thoughts & hopes are
>> that once we finalized what we were doing with our eventual move away from
>> CVS,  We would move our code to a system that offers a number of developer
>> features including an integrated bug tracker.  Google does offer a nice
>> system, but long term, it would be nice to just use the bug tracker
>> associated with our project, rather than setup a completely new project and
>> only use the bug tracker out of it.
>>
>> Curt.
>>
>>
>> 
>
> I totally agree that an issue tracking system is required.
>
> >From the short run that Pete Morgan and a couple of others have had a
> couple of things come to mind.
>
> - Proforma reports with at least the following information
> - Steps required to reproduce the bug
> - Operating System and version
> - Which version of FlightGear were you using?
>
> - The moderators need to be able to close tickets that are incomplete
> and the submitter is out of communication for an extended period of
> time. I'd say one fortnight, though that might be too long/short.
>
> - The idea where a user that submitted a bug report can also accept it
> as a bug is broken (unless the tickets are split into user issues and
> bugs.
>
> As an example a user reports an issue as "Flightgear stalls with lots
> of NaN messages being display on console at TBPB". The Bug could be
> "NaN messages are displayed on console due to bad input data". If you
> have other related issues, then you link the issue to the Bug ticket.
> This cuts down the redundant tickets that a developer needs to wade
> though.
>
>
> This is fast getting into ITIL land. I am familiar with Atlassian Jira
> for incident and problem management but it's an overkill for
> FlightGear base.
>
> What's the url for the ticketing system we have?
>
> Regards
>
>
> George
>
> --
> Come build with us! The BlackBerry® Developer Conference in SF, CA
> is the only developer event you need to attend this year. Jumpstart your
> developing skills, take BlackBerry mobile applications to market and stay 
> ahead of the curve. Join us from November 9-12, 2009. Register now!
> http://p.sf.net/sfu/devconf
> ___
> Flightgear-devel mailing list
> Flightgear-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/flightgear-devel
>   


--
Come build with us! The BlackBerry® Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay 
ahead of the curve. Join us from November 9-12, 2009. Register now!
http://p.sf.net/sfu/devconf
___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel

Re: [Flightgear-devel] bug tracking

[Curtis Olson]

On Wed, Sep 30, 2009 at 11:58 AM, Pete Morgan  wrote:

> Curtis Olson wrote:
> > I agree that a bug tracking system is a good thing.  My thoughts &
> > hopes are that once we finalized what we were doing with our eventual
> > move away from CVS,  We would move our code to a system that offers a
> > number of developer features including an integrated bug tracker.
> > Google does offer a nice system, but long term, it would be nice to
> > just use the bug tracker associated with our project, rather than
> > setup a completely new project and only use the bug tracker out of it.
> >
> > Curt.
> >
> for me as an intermediate user, If there is a facility to report bugs ie
> PIEPR's then that would be cool.
>
> So at the moment This site is for identifying bugs only.. No less or
> more. It will be seperate atmo from source..
>
> However recognising the bugs is THE issue.
>
> eg one of the  three paths
> 1) dont set up a bug tracker and ignoire them
> 2) Have a bug tracker and then ignore them
> 3) Have an active bug tracer and identify problem area and resolve issue..
>
> 4) Send a report to the developers that there is a bug u need to fix..
>
> Curtis .. please endorse and go for this bucktracker please.. At least
> that way we can all complain until we sort it.. ;-)
>
> this way it will be a steady eddie ;-)
> the SCM is another issue
>
>
I'd be more inclined to use the bug trackers at
http://code.google.com/p/simgear and http://code.google.com/p/flightgear but
those sites are currently tied up with svn versus git versus hg discussions.

Personally I think it could turn into a mess if we fill up this new site
with a bunch of bug reports and then have no way to move them to the
official site(s) later.  We also have bug trackers available at our
sourceforge registered projects.  I always felt the sourceforge bug tracker
was kind of slow and clunky.  The google bug tracker seems much nicer, and
it appears it is integrated with the repository so you can reference
specific patches or branches.  That would be harder to do if the bug tracker
lived at a completely separate project name.  We lose much of the cool
functionality that google offers.

Regards,

Curt.
-- 
Curtis Olson: http://baron.flightgear.org/~curt/
--
Come build with us! The BlackBerry® Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay 
ahead of the curve. Join us from November 9-12, 2009. Register now!
http://p.sf.net/sfu/devconf___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel

Re: [Flightgear-devel] bug tracking

[Pete Morgan]

Curtis Olson wrote:
> I agree that a bug tracking system is a good thing.  My thoughts & 
> hopes are that once we finalized what we were doing with our eventual 
> move away from CVS,  We would move our code to a system that offers a 
> number of developer features including an integrated bug tracker.  
> Google does offer a nice system, but long term, it would be nice to 
> just use the bug tracker associated with our project, rather than 
> setup a completely new project and only use the bug tracker out of it.
>
> Curt.
>
for me as an intermediate user, If there is a facility to report bugs ie 
PIEPR's then that would be cool.

So at the moment This site is for identifying bugs only.. No less or 
more. It will be seperate atmo from source..

However recognising the bugs is THE issue.

eg one of the  three paths
1) dont set up a bug tracker and ignoire them
2) Have a bug tracker and then ignore them
3) Have an active bug tracer and identify problem area and resolve issue..

4) Send a report to the developers that there is a bug u need to fix..

Curtis .. please endorse and go for this bucktracker please.. At least 
that way we can all complain until we sort it.. ;-)

this way it will be a steady eddie ;-)
the SCM is another issue

Pete

--
Come build with us! The BlackBerry® Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay 
ahead of the curve. Join us from November 9-12, 2009. Register now!
http://p.sf.net/sfu/devconf
___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel

Re: [Flightgear-devel] bug tracking

[George Patterson]

On Thu, Oct 1, 2009 at 2:25 AM, Curtis Olson  wrote:
> I agree that a bug tracking system is a good thing.  My thoughts & hopes are
> that once we finalized what we were doing with our eventual move away from
> CVS,  We would move our code to a system that offers a number of developer
> features including an integrated bug tracker.  Google does offer a nice
> system, but long term, it would be nice to just use the bug tracker
> associated with our project, rather than setup a completely new project and
> only use the bug tracker out of it.
>
> Curt.
>
>

I totally agree that an issue tracking system is required.

>From the short run that Pete Morgan and a couple of others have had a
couple of things come to mind.

- Proforma reports with at least the following information
- Steps required to reproduce the bug
- Operating System and version
- Which version of FlightGear were you using?

- The moderators need to be able to close tickets that are incomplete
and the submitter is out of communication for an extended period of
time. I'd say one fortnight, though that might be too long/short.

- The idea where a user that submitted a bug report can also accept it
as a bug is broken (unless the tickets are split into user issues and
bugs.

As an example a user reports an issue as "Flightgear stalls with lots
of NaN messages being display on console at TBPB". The Bug could be
"NaN messages are displayed on console due to bad input data". If you
have other related issues, then you link the issue to the Bug ticket.
This cuts down the redundant tickets that a developer needs to wade
though.


This is fast getting into ITIL land. I am familiar with Atlassian Jira
for incident and problem management but it's an overkill for
FlightGear base.

What's the url for the ticketing system we have?

Regards


George

--
Come build with us! The BlackBerry® Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay 
ahead of the curve. Join us from November 9-12, 2009. Register now!
http://p.sf.net/sfu/devconf
___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel

Re: [Flightgear-devel] bug tracking

[Curtis Olson]

I agree that a bug tracking system is a good thing.  My thoughts & hopes are
that once we finalized what we were doing with our eventual move away from
CVS,  We would move our code to a system that offers a number of developer
features including an integrated bug tracker.  Google does offer a nice
system, but long term, it would be nice to just use the bug tracker
associated with our project, rather than setup a completely new project and
only use the bug tracker out of it.

Curt.


On Wed, Sep 30, 2009 at 11:12 AM, Pete Morgan  wrote:

> Just the word bug and track are enough to scare pilots.
>
> So The concept is to set up a tracking system for bugs.
>
> So u must have at least one winge..
> http://code.google.com/p/flightgear-bugs/
>
> lets fix them ;-)
> pete
>
>
> --
> Come build with us! The BlackBerry® Developer Conference in SF, CA
> is the only developer event you need to attend this year. Jumpstart your
> developing skills, take BlackBerry mobile applications to market and stay
> ahead of the curve. Join us from November 9-12, 2009. Register now!
> http://p.sf.net/sfu/devconf
> ___
> Flightgear-devel mailing list
> Flightgear-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/flightgear-devel
>



-- 
Curtis Olson: http://baron.flightgear.org/~curt/
--
Come build with us! The BlackBerry® Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay 
ahead of the curve. Join us from November 9-12, 2009. Register now!
http://p.sf.net/sfu/devconf___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel

[Flightgear-devel] bug tracking

[Pete Morgan]

Just the word bug and track are enough to scare pilots.

So The concept is to set up a tracking system for bugs.

So u must have at least one winge..
http://code.google.com/p/flightgear-bugs/

lets fix them ;-)
pete

--
Come build with us! The BlackBerry® Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay 
ahead of the curve. Join us from November 9-12, 2009. Register now!
http://p.sf.net/sfu/devconf
___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel

[Flightgear-devel] simgear::strutils::convertToLowerCase link error.

[Scott Hamilton]

   I did a CVS update of SimGear and FG yesterday and I'm getting linker
errors, but I don't understand why?



../../src/Navaids/libNavaids.a(positioned.o): In function
`FGPositioned::typeFromName(std::basic_string, std::allocator > const&)':
/home/scotth/Downloads/FlightGear/CVS-1.0/source/src/Navaids/positioned.cxx:507:
 undefined reference to 
`simgear::strutils::convertToLowerCase(std::basic_string, std::allocator > const&)'
collect2: ld returned 1 exit status


Line 507 of positioned.cxx



  std::string lowerName(simgear::strutils::convertToLowerCase(aName));




and the matching strutils.cxx


   string
strip( const string& s )
{
return do_strip( s, BOTHSTRIP );
}

  string convertToLowerCase(const string& str)
  {
// proxy onto osgDB - easy to reimplement here, but let's avoid
// code duplication for the moment.
return osgDB::convertToLowerCase(str);
  }

} // end namespace strutils
} // end namespace simgear



and by implication the cvs log reveals

revision 1.5 
date: 2009/09/26 11:44:33;  author: jmt;  state: Exp;  lines: +13 -1
Extend simgear::strutils with convertToLowerCase helper - currently a
proxy for osgDB helper of the same name.

  
revision
1.4 
 
date: 2008/04/13 21:11:44;  author: timoore;  state: Exp;  lines: +5
-3   
Fixes for compiling with gcc
4.3 
 

Include standard header files and qualify with std:: where needed.

Add "const" to various char parameters and variables.





--
Come build with us! The BlackBerry® Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay 
ahead of the curve. Join us from November 9-12, 2009. Register now!
http://p.sf.net/sfu/devconf___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel