Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:30019
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain powertrip.co.za designates 72.21.46.202 as permitted sender)
In-Reply-To: <465DEF93.1080006@sci.fi>
References: <465DA8F9.2020001@chiaraquartet.net> <465DEF93.1080006@sci.fi>
Mime-Version: 1.0 (Apple Message framework v752.3)
Content-Type: text/plain; charset=ISO-8859-1; delsp=yes; format=flowed
Message-ID: <6406496A-48F4-4CB7-9E45-FB7F6F2124CA@powertrip.co.za>
Cc: internals Mailing List <internals@lists.php.net>,
 Gregory Beaver <greg@chiaraquartet.net>
Content-Transfer-Encoding: quoted-printable
Date: Fri, 1 Jun 2007 00:51:48 +0200
To: jani.taskinen@iki.fi
Subject: Re: [PHP-DEV] bug tracker merging
From: jacques@powertrip.co.za (Jacques Marneweck)

Are you using PHPUnit for the unit tests?

Also there was some alert stuff that Jim Winstead if I remember =20
correctly
was wanting to hook into the mix (it's all commented out from my last =20=

look at
the bugsweb code), which would be great to allow devs to subscribe to =20=

bugs
(package / project / etc.) that interests them.

Regards
--jm

On 30 May 2007, at 11:41 PM, Jani Taskinen wrote:

> I read this email *AFTER* discussing with Gregory in IRC about =20
> current situation  of having 3 separate bug trackers in *.php.net. =20
> So now I'm hijacking this coincidentally related thread for =20
> informing what happened during/after the discussion. :D
>
> Gregory Beaver kirjoitti:
>> I'm a bit concerned by the headlong rush to refactor phpbugsweb to
>> include PEAR and PECL bugs.  The concept is fine by me, but starting
>> with phpbugsweb as the starting point is a big mistake if you plan to
>> include PEAR bugs.  The PEAR bug tracker has several killer features
>> that you will have to pry from my cold dead fingers before I would
>> accept a merge with the phpbugsweb
>
> I agreed with Gregory that the PEAR version of the original PHP bug =20=

> tracker code is the best starting point for unified codebase. So =20
> now there is pear/Bugtracker
> in CVS which Gregory created from the current PEAR bug tracker code.
>
> This will be the base for the =FCbertracker.
>
>> The main problem with the codebase of pearweb/bugs is that it =20
>> depends on
>> the core of pearweb (bad) and so needs to be independentized, but =20
>> we are
>> doing this ASAP.  roadmap for the website is at
>> http://pear.php.net/bugs/roadmap.php?package=3Dpearweb
>
> I'm dividing the task in hand first into 2 phases required to =20
> kickstart this:
>
> Phase I (one):
>
> - Unified codebase that works for PEAR/PECL/PHP bug trackers using =20
> their own databases. (*)
>
> * Basically all changes/additions are needed only for current PHP =20
> bug db,
> PEAR/PECL both share the "package/type" concept already. This is my =20=

> first TODO.
>
> Phase II (two):
>
> - Add "project" concept into the tracker and merge each database =20
> into one,
> http://bugs.php.net/ will be the only bugtracker for *.php.net, =20
> [pear|pecl].php.net/bugs/ can just be redirected there..not to =20
> forget php-gtk, etc. When projects are in DB, adding one more will =20
> not be hard. :)
>
> ..more phases will propably come up later, these 2 are the main =20
> targets now.
>
>> Of course, it's also in the process of being refactored along with =20=

>> the
>> rest of pearweb (unit tests *gasp*) so please don't discount a =20
>> look at
>> this codebase, no matter how bigoted against PEAR you might be ;)
>
> I will ignore any unit tests for now. :)
>
> --Jani
>
> p.s. Any volunteers: You're not needed right now..and most likely =20
> not later either. (this is friendly hint to everyone: keep your =20
> hands off! :)
>
> p.p.s I refuse to discuss things like coding style, using pear/not =20
> using pear stuff..etc. Focus!
>
> --=20
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php
>