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 <ac...@daffodil.uk.com> 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 <ac...@daffodil.uk.com
> > <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/<http://baron.flightgear.org/%7Ecurt/>
> > <http://baron.flightgear.org/%7Ecurt/>
> > ------------------------------------------------------------------------
> >
> >
> ------------------------------------------------------------------------------
> > 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 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
