RE: cvs: php-bugs-web / bugtypes.inc /include functions.inc
| From: | Rasmus Lerdorf | Date: | Sat, 28 Jun 2003 16:50:29 +0000 |
| Subject: | RE: cvs: php-bugs-web / bugtypes.inc /include functions.inc | ||
| References: | 1 | Groups: | php.mirrors |
| Request: | Send a blank email to php-mirrors+get-19017@lists.php.net to get a copy of this message | ||
On Sat, 28 Jun 2003, Jacques Marneweck wrote:
> I think that the bugs.php.net site needs a huge bit of work to support
> multiple projects of the php group. atm it support PHP. To add more
> projects it need to track things like which project it belongs to e.g.
> PEAR, PHP, PECL, PHPGTK, Smarty, etc. also things like version need
> tracking, etc. etc.
I don't think the work to add a project field and per-project versioning
is huge at all. I'd rather see us spend the time enhancing the existing
system to handle multiple projects than trying to maintain a bunch of
instances. If we decide to change something in the main bugs.php.net
code, especially if it involves any sort of database schema change,
chances are we mess up all the instances.
Also, as we get more php-related projects popping up on php.net, the
interaction between them is much easier to handle in a single bug
database. For example, the curl library recently moved to our cvs server.
It would be nice if the current ext/curl category belonged to both the php
and the curl projects and thus visible on both bugs.php.net and
bugs.curl.org (or whatever their url might be). It would also mean that
if someone files a bug against ext/curl in the php bug database and we
look at it and determine it is actually a low-level library problem, we
can reclassify it directly into the curl system.
-Rasmus