Re: extremely inactive packages
| From: | Arnaud Limbourg | Date: | Mon, 19 Feb 2007 14:06:41 +0000 |
| Subject: | Re: extremely inactive packages | ||
| References: | 1 2 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-45679@lists.php.net to get a copy of this message | ||
Sebastian Ebling wrote:
Am Sonntag, den 18.02.2007, 15:06 -0600 schrieb Gregory Beaver:That does sound good. One major issue though is that without unit tests it is almost impossible to guarantee BC. Arnaud.Hi all, I would like to propose a change to the way we do things here. There are too many packages whose open bugs are just hanging out waiting to be fixed. If you find a package with a few open bugs that are simple fixes, I propose we do this: First, check these possibilities: 1) When was the last commit? Recent? 2) When was the last comment on a bug? Recent? 3) Has the developer been active on any of their packages recently? If the answer is "no" to all 3, I suggest that the package be marked as unmaintained, and if it is marked as unmaintained, any pear developer with commit access may fix bugs and then QA can make a release.I really like this idea because this makes it a lot more easy to apply a fix to a more or less unmaintained package without having to become a maintainer of this package.