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 [email protected] https://lists.sourceforge.net/lists/listinfo/flightgear-devel
