Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:44977
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain Sun.COM from 192.18.43.133 cause and error)
MIME-version: 1.0
Content-transfer-encoding: 7BIT
Content-type: text/plain; CHARSET=US-ASCII; format=flowed
Date: Wed, 15 Jul 2009 10:35:58 -0700
In-reply-to: <FBE08A97-79DF-4311-8DE4-2237DEAEFC59@roshambo.org>
Sender: Sriram.Natarajan@Sun.COM
To: Philip Olson <philip@roshambo.org>
Cc: PHP internals <internals@lists.php.net>
Message-ID: <4A5E137E.3010905@Sun.COM>
References: <FBE08A97-79DF-4311-8DE4-2237DEAEFC59@roshambo.org>
User-Agent: Thunderbird 2.0.0.22 (Macintosh/20090605)
Subject: Re: [PHP-DEV] bug tracker planning
From: Sriram.Natarajan@Sun.COM (Sriram Natarajan)

Hi
 bug tracking system also need the ability to mark a current bug as 
duplicate . Currently, all those bugs are marked as 'Bogus'. Also, it 
would be nice if we can have the ability to capture related bugs together.

- Sriram

Philip Olson wrote:
>
> The bug system today works fine but improvements are being made. I've 
> gone through the lists and details from past attempts and will list 
> ideas here. Please do not vote, but if a particular item appears like 
> a bad idea then please explain. Or, discuss additional (or modified) 
> ideas that will be useful to the PHP project.
>
> The new system[1] is based off the pear.php.net bug system (via Jani), 
> which long ago was a fork of our current (bugs.php.net). Because of 
> this, some of these items are already available via the pear geeks. 
> The plan is to have one bug tracker that includes 
> PEAR+PECL+Core+GTK+Etc. It's also planning to go live after Stage #1 
> is completed, and also Jani and 2009 GSoC student Felipe Ribeiro are 
> working on this project. Soonish a test system will be setup for all 
> to break. Yes, this really is happening.
>
> Most people like the current system because it's simple, and I don't 
> foresee this changing.
>
> First stage:
> - Cleanup code (in progress)
> - Attachments : For a diff, test, backtrace, screenshot, whatever. (done)
> - Package/Type separation : Packages (like extensions) and Bug Types 
> (like feature requests) are separate (done)
> - Defined/Documented permissions : For example, so we all know if a 
> random person can comment on a bogus bug
> - Preview button, instead of only submit (almost done)
> - Deal with bug id clashes from current PECL/PEAR/PHP bug trackers, 
> and associated links
> - Importing
> - Testing
>
> Second stage:
> - Additional history : When a bug was opened/closed etc. Currently we 
> don't log this except in emails
> - Reclassification : Discuss how we handle this, like should old/new 
> lists both receive emails?
> - Consider different captcha (like reCaptcha) for anonymous users
> - Voting : Do we use or care about this? Improve?
> - nofeedback improvements : People assume this means closed, when it 
> does not
>
> Third stage:
> - Subscriptions : Allow people to subscribe to RSS and/or receive 
> emails per bug/package
> - Tagging : Allow people to optionally attach tags to bugs
> - IRC integration : Allow bot integration to an IRC channel, like a 
> #php.bugs resurrection
> - Optional milestones (in pearweb today)
> - Integrate with VCS. Research this, KISS. Ex. A commit containing 
> "PHP Bug #42" automagically appends info to the bugs db
> - Befriend systems like http://bts-link.alioth.debian.org/
> - OpenID support, see also http://wiki.php.net/ideas/phpnetauth
> - Username finder for the 'assigned' boxes, see also 
> http://people.php.net/
>
> And as always, additional volunteers are welcome.
>
> Regards,
> Philip
>
> [1] http://cvs.php.net/viewvc.cgi/pear/Bugtracker/
>
>