Re: [PHP-DEV] bug tracker planning

2009-07-16 Thread Pierre Joye
On Thu, Jul 16, 2009 at 5:54 AM, Philip Olson wrote: > As for 'capturing related bugs', I imagine the [optional] tagging would help > with that... or do you have something specific in mind? Related bugs are more a list of bugs # related to a given one, or being a dependency, a coma separated list

Re: [PHP-DEV] bug tracker planning

2009-07-15 Thread Philip Olson
On Jul 15, 2009, at 11:47 AM, Jani Taskinen wrote: Sriram Natarajan wrote: Hi bug tracking system also need the ability to mark a current bug as duplicate . Currently, all those bugs are marked as 'Bogus'. Also, it would be nice if we can have the ability to capture related bugs together

Re: [PHP-DEV] bug tracker planning

2009-07-15 Thread Jani Taskinen
Sriram Natarajan wrote: Jani Taskinen wrote: Please don't top post! And what you ask for is already there. --Jani Sriram Natarajan kirjoitti: Hi I very much miss the ability to add my email address to the bugs that I am interested in. This used to allow to me to track its progress. I wa

Re: [PHP-DEV] bug tracker planning

2009-07-15 Thread Jani Taskinen
Sriram Natarajan wrote: Hi bug tracking system also need the ability to mark a current bug as duplicate . Currently, all those bugs are marked as 'Bogus'. Also, it would be nice if we can have the ability to capture related bugs together. - Sriram Again: DO NOT TOP POST!! And we're not add

Re: [PHP-DEV] bug tracker planning

2009-07-15 Thread Sriram Natarajan
Hi bug tracking system also need the ability to mark a current bug as duplicate . Currently, all those bugs are marked as 'Bogus'. Also, it would be nice if we can have the ability to capture related bugs together. - Sriram Philip Olson wrote: The bug system today works fine but improvement

Re: [PHP-DEV] bug tracker planning

2009-07-15 Thread Sriram Natarajan
Jani Taskinen wrote: Please don't top post! And what you ask for is already there. --Jani Sriram Natarajan kirjoitti: Hi I very much miss the ability to add my email address to the bugs that I am interested in. This used to allow to me to track its progress. I wasn't not sure, if that is

Re: [PHP-DEV] bug tracker planning

2009-07-11 Thread Brett Bieber
On Tue, Jul 7, 2009 at 12:54 PM, Philip Olson wrote: > And as always, additional volunteers are welcome. Sounds great. How does one join the team? Is there an appropriate place to submit patches to, a bugtracker for the bugtracker? > [1] http://cvs.php.net/viewvc.cgi/pear/Bugtracker/ now http://

Re: [PHP-DEV] bug tracker planning

2009-07-11 Thread Jani Taskinen
Please don't top post! And what you ask for is already there. --Jani Sriram Natarajan kirjoitti: Hi I very much miss the ability to add my email address to the bugs that I am interested in. This used to allow to me to track its progress. I wasn't not sure, if that is what you meant within S

Re: [PHP-DEV] bug tracker planning

2009-07-09 Thread Sriram Natarajan
Hi I very much miss the ability to add my email address to the bugs that I am interested in. This used to allow to me to track its progress. I wasn't not sure, if that is what you meant within Subscriptions.. - sriram Philip Olson wrote: The bug system today works fine but improvements are

Re: [PHP-DEV] bug tracker planning

2009-07-09 Thread Greg Beaver
Hannes Magnusson wrote: > On Thu, Jul 9, 2009 at 04:50, Greg Beaver wrote: > >> The disadvantages are obvious: everyone has to have an account and give >> their email address to report a bug. The advantages are also obvious: >> > > I *hate* when I am required to signup and do all sorts of

Re: [PHP-DEV] bug tracker planning

2009-07-09 Thread Hannes Magnusson
On Thu, Jul 9, 2009 at 04:50, Greg Beaver wrote: >  The disadvantages are obvious: everyone has to have an account and give > their email address to report a bug.  The advantages are also obvious: I *hate* when I am required to signup and do all sorts of weird validation crap before I can file bug

Re: [PHP-DEV] bug tracker planning

2009-07-08 Thread Greg Beaver
Richard Lynch wrote: > On Tue, July 7, 2009 12:54 pm, Philip Olson wrote: >> - Reclassification : Discuss how we handle this, like should old/new >> lists both receive emails? > > Both lists should receive reclassifaction notification, and nothing > more, imho. > >> - Consider different captcha (

Re: [PHP-DEV] bug tracker planning

2009-07-08 Thread Richard Lynch
On Tue, July 7, 2009 12:54 pm, Philip Olson wrote: > - Reclassification : Discuss how we handle this, like should old/new > lists both receive emails? Both lists should receive reclassifaction notification, and nothing more, imho. > - Consider different captcha (like reCaptcha) for anonymous user

Re: [PHP-DEV] bug tracker planning

2009-07-08 Thread Jani Taskinen
Hannes Magnusson wrote: On Wed, Jul 8, 2009 at 14:00, Jani Taskinen wrote: Philip Olson wrote: - Importing Of what..? Existing bugs from php/pecl/php/gtk Ah yes, that's 3rd stage stuff, when (if?) there's single installation handling all bugs for all our projects.. - Tagging : Allow pe

Re: [PHP-DEV] bug tracker planning

2009-07-08 Thread Hannes Magnusson
On Wed, Jul 8, 2009 at 14:00, Jani Taskinen wrote: > Philip Olson wrote: >> - Importing > > Of what..? Existing bugs from php/pecl/php/gtk >> - Tagging : Allow people to optionally attach tags to bugs > > What tags..? I assume web2.0 tagging (as in gmail labels for example, or blog entry tags..

Re: [PHP-DEV] bug tracker planning

2009-07-08 Thread Jani Taskinen
Philip Olson wrote: The new system[1] is based off the pear.php.net bug system (via Jani), which long ago was a fork of our current (bugs.php.net). Because of Pear folks forked it for http://pear.php.net/bugs/ and pecl folks took the same at some point..(?). this, some of these items are al