I read this email *AFTER* discussing with Gregory in IRC about current situation
of having 3 separate bug trackers in *.php.net. So now I'm hijacking this
coincidentally related thread for 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 tracker code
is the best starting point for unified codebase. So now there is pear/Bugtracker
in CVS which Gregory created from the current PEAR bug tracker code.
This will be the base for the übertracker.
The main problem with the codebase of pearweb/bugs is that it depends on
the core of pearweb (bad) and so needs to be independentized, but we are
doing this ASAP. roadmap for the website is at
http://pear.php.net/bugs/roadmap.php?package=pearweb
I'm dividing the task in hand first into 2 phases required to kickstart this:
Phase I (one):
- Unified codebase that works for PEAR/PECL/PHP bug trackers using their own
databases. (*)
* Basically all changes/additions are needed only for current PHP bug db,
PEAR/PECL both share the "package/type" concept already. This is my first TODO.
Phase II (two):
- Add "project" concept into the tracker and merge each database into one,
http://bugs.php.net/ will be the only bugtracker for *.php.net,
[pear|pecl].php.net/bugs/ can just be redirected there..not to forget php-gtk,
etc. When projects are in DB, adding one more will not be hard. :)
..more phases will propably come up later, these 2 are the main targets now.
Of course, it's also in the process of being refactored along with the
rest of pearweb (unit tests *gasp*) so please don't discount a 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 not later
either. (this is friendly hint to everyone: keep your hands off! :)
p.p.s I refuse to discuss things like coding style, using pear/not using pear
stuff..etc. Focus!
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
