PHP :: Request #55963 :: send bug summary to pear-qa

Request #55963	send bug summary to pear-qa
Submitted:	2004-01-13 05:33 UTC	Modified:	2004-12-22 09:32 UTC
From:	smith at backendmedia dot com	Assigned:	dufuz (profile)
Status:	Closed	Package:	PECL bug system (PECL)
PHP Version:	Irrelevant	OS:	Irrelevant
Private report:	No	CVE-ID:	None

View Developer Edit

Welcome! If you don't have a Git account, you can't do anything here.
If you reported this bug, you can edit this bug over here.

php.net Username: php.net Password:

	Block user comment
Status:		Assign to:
Package:
Bug Type:
Summary:
From:	smith at backendmedia dot com
New email:
PHP Version:		OS:

New/Additional Comment:

[2004-01-13 05:33 UTC] smith at backendmedia dot com

Description:
------------
Would it be possible to send a summary of all open bugs to pear-qa? What would be even nicer is to also add all bug reports that have changed.

The time interval should probably be weekly.

Patches

Pull Requests

History

AllCommentsChangesGit/SVN commitsRelated reports

[2004-02-20 09:40 UTC] lsmith@php.net

alternatively I guess a dedicated bug list would also do, if the summary is too much effort to implement. QA really needs to know what is going on. Who closes bugs, how many open etc.

[2004-02-20 10:14 UTC] toby@php.net

I guess just routing all bug mails to pear-qa would last, shouldn't it? The header and subject additions of the bug-system should enable everyone to filter them out. Otherwise I'd prefer a normal new mailinglist instead of a summary, since each bug is a single topic and and bug-actions should be viewable grouped by bug (threads).

[2004-02-20 11:00 UTC] neufeind@php.net

Well, I don't see why such a summary would be helpful. You can easily browse the bugs (by relevance, by package, ...) via the bug-system from time to time. And what would "who closed the bugs" be needed for? There might be several people involved in the solution - so imho it doesn't really matter who actually closed the bug.

[2004-02-20 11:16 UTC] toby@php.net

I personally prefer mailinglists. :) Getting the latest issues  directly aggregated inside one application is quite cool! :) Maybe a seperated mailinglist pear-bugs is the best solution.

[2004-02-20 11:29 UTC] neufeind@php.net

Already yeah. After a clarifying discussion I've agreed with Lukas that a mailinglist would be best. However neither pear-dev nor pear-qa should be flooded with messages, since others might suffer from that "noise". So we propose to open a pear-bug-list (similar to pear-cvs) which everbody interested is invited to join. We expect >40 mails per week ..

[2004-02-20 12:31 UTC] mj@php.net

So to sum it up:

* Weekly summaries will be send to pear-qa
* A copy of all bug reports and the appendant comments will be send to pear-bugs.

If that is the way to go, I'll take care of getting the stuff set up. (I'm also working towards having a announcement list, but did not get a response from the people in charge yet.)

[2004-04-26 23:38 UTC] helgi at trance dot is

I assigend my self to this one since I'm making a bug reminder/summary script... Should be added sooner the later ;)
Martin what's the status on pear-bugs and pear-announce ? :)

[2004-12-22 09:32 UTC] helgi at trance dot is

This has now been implanted.

	php.net \| support \| documentation \| report a bug \| advanced search \| search howto \| statistics \| random bug \| login
go to bug id or search bugs for


Copyright © 2001-2024 The PHP Group All rights reserved.	Last updated: Sat Dec 21 11:01:30 2024 UTC