Bugtracker - Status update
| From: | Felipe Ribeiro | Date: | Tue, 21 Jul 2009 02:18:03 +0000 |
| Subject: | Bugtracker - Status update | ||
| Groups: | php.gsoc | ||
| Request: | Send a blank email to php-gsoc+get-117@lists.php.net to get a copy of this message | ||
Hi all,
The bugtracker improvements are divided in milestones, that are listed below.
This week I implemented the RSS feeds per bug and I'm working on the
SVN integration.
First stage:
- Cleanup code (*done*)
- 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
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
- 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 (*done*)
- 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 (*almost
done*)
- Username finder for the 'assigned' boxes, see also http://people.php.net/
Regards
--
Felipe Ribeiro
Zend PHP5 Certified Engineer
felipernb@gmail.com
http://feliperibeiro.com
+55 83 9979-3161