FYI: I installed the "new" bug tracker to ez1.php.net for easier
testing. Feel free to test it and comment to this thread. If the DNS has
not propagated yet, just add this to your hosts file:
128.39.198.38 bugs-beta.php.net
Keep in mind it's NOT totally new, it's simply been "cleaned up" and
some tiny featurettes have been added / merged from PEAR bug tracker:
-
Bug type (Bug, Feature/Change Request or Documentation problem)
- This allows more fine-grained categorization, per pacakge
-
Changelog and SVN commits separate from regular comments
-
Patches / file attachements
-
Categories in DB instead of file
- TODO: Online editor for categories (or s.c. pseudo packages)
-
Preview for reporting new bugs
-
Everything is UTF-8 now
-
Something I don't remember anymore.. :D
I wish this inspires more people to get involved and not waste time on
the current bugs.php.net anymore. :)
--Jani
FYI: I installed the "new" bug tracker to ez1.php.net for easier testing.
Feel free to test it and comment to this thread. If the DNS has not
propagated yet, just add this to your hosts file:128.39.198.38 bugs-beta.php.net
Keep in mind it's NOT totally new, it's simply been "cleaned up" and some
tiny featurettes have been added / merged from PEAR bug tracker:- Bug type (Bug, Feature/Change Request or Documentation problem)
* This allows more fine-grained categorization, per pacakge- Changelog and SVN commits separate from regular comments
- Patches / file attachements
- Categories in DB instead of file
* TODO: Online editor for categories (or s.c. pseudo packages)- Preview for reporting new bugs
- Everything is UTF-8 now
* f.e. http://bugs-beta.php.net/bug.php?id=51065&edit=1 vs.
http://bugs.php.net/bug.php?id=51065&edit=1- Something I don't remember anymore.. :D
I wish this inspires more people to get involved and not waste time on the
current bugs.php.net anymore. :)--Jani
--
A couple of low level things
1 - Can/should the PHP Versions include release candidates?
2 - Is "Package affected:" the right label?
3 - "A patch file created using cvs diff -u" ... cvs ?
Regards,
Richard.
--
Richard Quadling
"Standing on the shoulders of some very clever giants!"
EE : http://www.experts-exchange.com/M_248814.html
EE4Free : http://www.experts-exchange.com/becomeAnExpert.jsp
Zend Certified Engineer : http://zend.com/zce.php?c=ZEND002498&r=213474731
ZOPA : http://uk.zopa.com/member/RQuadling
22.2.2010 17:28, Richard Quadling wrote:
A couple of low level things
Nitpicking, are we? :D
1 - Can/should the PHP Versions include release candidates?
Yes, they're outdated. This is one part that should be automated/centralized,
it's enough PITA for the RMs already to remember all the places to update.
I'll added note to TODO about it.
2 - Is "Package affected:" the right label?
Yes, sort of. Remember this has origins in pear/pecl. And the ultimate goal has
been to have single tracker to allow moving reports easily around.
3 - "A patch file created using cvs diff -u" ... cvs ?
Fixed. :) And thanks for noticing. (not yet updated on the bugs-beta site, no
access from home :)
--Jani
22.2.2010 17:28, Richard Quadling wrote:
A couple of low level things
Nitpicking, are we? :D
It's what I'm good at ;-)
1 - Can/should the PHP Versions include release candidates?
Yes, they're outdated. This is one part that should be
automated/centralized, it's enough PITA for the RMs already to remember all
the places to update.I'll added note to TODO about it.
Maybe this is something that the new RMTools can handle automatically.
Poke Pierre.
--
Richard Quadling
"Standing on the shoulders of some very clever giants!"
EE : http://www.experts-exchange.com/M_248814.html
EE4Free : http://www.experts-exchange.com/becomeAnExpert.jsp
Zend Certified Engineer : http://zend.com/zce.php?c=ZEND002498&r=213474731
ZOPA : http://uk.zopa.com/member/RQuadling
Hi,
FYI: I installed the "new" bug tracker to ez1.php.net for easier
testing. Feel free to test it and comment to this thread. If the DNS has
Great!
- Patches / file attachements
I like the idea of calling it "patch" so users won't immediatly upload
large big applications. Is there a size limit?
- Something I don't remember anymore.. :D
The !Quick resolve" dropdown box seems to be missing. Is that
intentional?
Anybody working on a "target milestone" Feature?
johannes
22.2.2010 19:15, Johannes Schlüter wrote:
- Patches / file attachementsI like the idea of calling it "patch" so users won't immediatly upload
large big applications. Is there a size limit?
No limits apart from what is set in either httpd.conf or php.ini, also, they
need to be text format.
Again, this is simply copy of what PEAR bug tracker has had for ages. Or at
least one point had, dunno what they might be using right now.
The !Quick resolve" dropdown box seems to be missing. Is that
intentional?
For some reason it's not shown if you're not logged in.
Should it be? :)
Anybody working on a "target milestone" Feature?
There's nobody working on anything except me randomly when I have had time..
Feel free. I'd rather see people improving on this than wasting time on the
current horrid mess of php-bugs-web..
--Jani